I'm just posting this to see how long it takes to get this fixed.
The clock is ticking...
I'm just posting this to see how long it takes to get this fixed. The clock is ticking...
Are you saying that they weren't the first publishers? [;)]
[:P]
Jannie -
That was quick! When does it get updated on our side? Just curious.
When does it get updated on our side?
Soon. [:)]
UPDATE: Restart Logos to get the corrected version.
When does it get updated on our side? Soon. UPDATE: Restart Logos to get the corrected version.
Soon.
Wow! Too bad all typos don't get fixed that quick!! [;)] [:p]
Jannie, thanks for the quick fix. your hard work and quick action are appreciated! [:)]
When does it get updated on our side? Soon. UPDATE: Restart Logos to get the corrected version. Wow! Too bad all typos don't get fixed that quick!!
Wow! Too bad all typos don't get fixed that quick!!
Wow, wow, wow indeed! And yes I wish all typos were fixed that quick. Jannie can I hire you as my personal typo fixer? [:)]
Wow, wow, wow indeed
To be fare, I'm just the messenger. Three other people did the work, so all thanks to them!
Wow, wow, wow indeed To be fare, I'm just the messenger. Three other people did the work, so all thanks to them!
OK, then can I hire you ask my personal typo messenger to get three people to do the work?
Seriously, though, it really takes three people to change PUBLISHERS to PUBLISHED and check in the fix (plus one messenger to communicate the need for the fix and the fact that it's been fixed)? No wonder there's such a backlog of typos waiting to be fixed.
I remember our discussion at BibleTech 2011 Rosie
I think the three people come in more with republishing the book, not necessarily fixing the typo.
One to hold the keyboard. One to type the change. One to watch the screen. [;)]
Seriously, though, it really takes three people to change PUBLISHERS to PUBLISHED and check in the fix (plus one messenger to communicate the need for the fix and the fact that it's been fixed)? No wonder there's such a backlog of typos waiting to be fixed. One to hold the keyboard. One to type the change. One to watch the screen.
One to hold the keyboard. One to type the change. One to watch the screen.
I've got some lightbulbs that need changing... [;)]
I remember our discussion at BibleTech 2011 Rosie I think the three people come in more with republishing the book, not necessarily fixing the typo.
OK, I was just taking Jannie's comment "three people did the work" literally. Maybe there was other work being done to republish the book at the same time, and that's why he happened to be able to get them to sneak in a typo fix while they were at it.
Seriously, though, it really takes three people to change PUBLISHERS to PUBLISHED and check in the fix (plus one messenger to communicate the need for the fix and the fact that it's been fixed)? No wonder there's such a backlog of typos waiting to be fixed. One to hold the keyboard. One to type the change. One to watch the screen. I've got some lightbulbs that need changing...
I've got some lightbulbs that need changing...
That requires 5 persons: 2 to hold and turn the ladder, one to change the bulb, 1 to unpack the new bulb and 1 to throw away the packaging. [:D]
Wow, wow, wow indeed! And yes I wish all typos were fixed that quick. Jannie can I hire you as my personal typo fixer?
To be "fare" ? [:O] Rosie, Are you sure you want to pay a fair fare for fair spell-checking? It is a fair game when the spelling is fairly "infairior.". [;)] Now who is snarky? Hi Jannie, Good to meet you.
Glad to see the quick response on this. Of course, this seems to be an exception to the rule. I hope that there will be a BIG MOVE on typos at some point in the not too distant future. And dead links. I thought that this typo might get attention because it was a title page, and it seems to have produced enough "squeak" to get the grease. But, practically speaking, a title page isn't exactly a "high need" fix.
Thanks again for the response. Hope it is a portent of more to come. [Y]
Wow, wow, wow indeed! And yes I wish all typos were fixed that quick.
Glad to see the quick response on this. Of course, this seems to be an exception to the rule.
While I applaud Logos for being a good sport and raising to the challenge, I do not applaud David for issuing it, and I do not want all typos to be fixed this quick.
Unless this resource just happened to be scheduled for an update anyway, your little prank, David, cost me nearly two hours with an essentially dead computer, desperately struggling with the indexing. I did not appreciate that at all. And I don't think those with monthly caps appreciated it either. Yes, I want links and typos fixed as much as the rest of you, but I want them fixed one resource at a time, not one typo at a time. I'd love it if Logos could reach a stage where Bibles were updated twice a year and other books once, but I do not want to redownload and reindex the same resources week after week, just because someone found a new typo.
While I applaud Logos for being a good sport and raising to the challenge, I do not applaud David for issuing it, and I do not want all typos to be fixed this quick. Unless this resource just happened to be scheduled for an update anyway, your little prank, David, cost me nearly two hours with an essentially dead computer, desperately struggling with the indexing. I did not appreciate that at all. And I don't think those with monthly caps appreciated it either. Yes, I want links and typos fixed as much as the rest of you, but I want them fixed one resource at a time, not one typo at a time. I'd love it if Logos could reach a stage where Bibles were updated twice a year and other books once, but I do not want to redownload and reindex the same resources week after week, just because someone found a new typo.
I can understand your pique with this, but, not having a monthly cap, I can't say that I personally was very concerned about it. I would agree, however, that fixes should be on a per book basis (or series in a multivolume set). I nevertheless would go further by saying that a schedule of once or twice per year for resources might be a bit overwhelming considering the number of resources Logos now publishes. I would rather think that typo fixes should be performed when a certain quantity has been accumulated for that resource or on a schedule to be determined should there not be sufficient to reach that threshhold (so that they don't become too old).
And I don't think those with monthly caps appreciated it either.
Modified resources are not downloaded whole anymore. Only the changed portion is downloaded.
not having a monthly cap, I can't say that I personally was very concerned about it
Nor do I. I'm personally more concerned about the indexing.
a schedule of once or twice per year for resources might be a bit overwhelming considering the number of resources Logos now publishes.
If they ever reach a stage when they manage that, it will be because almost all typos have already been weeded out. [:)]
I know, but if all typos were fixed immediately, like those folks above wanted, it would still mean an awful lot of MBs to download (and index) each week.
Not really. They've now switched to a model where they download "patches" instead of entire resources. So if a single typo were fixed in a largish resource, we'd only have to download a small patch which would get merged into the resource on our end. If dozens of typos were fixed across dozens of resources, it would still only amount to a relatively small amount of downloading, compared to the new resources we download every time a pre-pub ships. Let's say they do that once a month. I don't think it would mess with most people's Internet usage caps.
Unless this resource just happened to be scheduled for an update anyway
It was. By a happy coincidence, we were already fixing other typos and adding new markup for text justification. (I hope I'm not spoiling Jannie's fun at getting to supply such rapid results.[:)])
The advantage of having resources in data base files rather then in text files. [Thanks for the information]
