MobileRead Forums - View Single Post

taming · 09-13-2012, 02:44 PM

What I don't know, Mrs_Often, is if Matt is expecting that people who installed the 2.1.1 build manually might have problems when the new build is officially released.

I am not a techie, but I do know that one of the reasons this release is taking awhile has to do with localizations of earlier releases and the odd way they can fail on updates. I think I was the first person to speculate that our Oz and Kiwi friends were having failures that people in No America were not experiencing waaaay back in the early release days of 2.0.0.

I believe that the build we are all waiting for is supposed to take care of that for folks using official builds, regardless of what their initial version was.

In the land of pure speculation---When Kobo started out and had various International partners, each of them had different websites and folks were more or less locked into these partners. They did not buy books from Kobobooks.com. Then that model went away (remember Borders). Devices locked into Borders had to be transitioned into Kobo. It was a difficult project to manage, but it appears to have gone fairly smoothly.

From what I can tell, none of the locked in devices received special firmware changes, so these very localized firmware versions are still lurking about. Some are problematic, some are not.

It seems to me (speculation mode still on), that Kobo recognizes that some location-based things are still necessary, for example, default fonts for Japanese customers and Canadian customer are not likely to be the same. And given that space is limited, the loaded dictionaries could also be different, from one part of the world to another. That being said, it looks like there is something afoot to get a whole whack of code the same regardless of what Kobo eINK device people use, or where they are located when they activate the device.

Now (yes, still more speculation), Kobo actually knows what builds/firmware is out there. And they can figure out how to clean up this issue as long as they can pretty much count on all of the builds sitting on devices being official ones that were laid down on top of them. Add in variations never meant to go on top of the builds on their list, and potentially weird things could happen when the official build is released.

Stick a fork in me; I'm done.

09-13-2012, 02:44 PM	#40
taming Trying for calm & polite Posts: 4,012 Karma: 9455193 Join Date: May 2010 Location: Mostly in Canada Device: kobo original, WiFI, Touch, Glo, and Aura	What I don't know, Mrs_Often, is if Matt is expecting that people who installed the 2.1.1 build manually might have problems when the new build is officially released. I am not a techie, but I do know that one of the reasons this release is taking awhile has to do with localizations of earlier releases and the odd way they can fail on updates. I think I was the first person to speculate that our Oz and Kiwi friends were having failures that people in No America were not experiencing waaaay back in the early release days of 2.0.0. I believe that the build we are all waiting for is supposed to take care of that for folks using official builds, regardless of what their initial version was. In the land of pure speculation---When Kobo started out and had various International partners, each of them had different websites and folks were more or less locked into these partners. They did not buy books from Kobobooks.com. Then that model went away (remember Borders). Devices locked into Borders had to be transitioned into Kobo. It was a difficult project to manage, but it appears to have gone fairly smoothly. From what I can tell, none of the locked in devices received special firmware changes, so these very localized firmware versions are still lurking about. Some are problematic, some are not. It seems to me (speculation mode still on), that Kobo recognizes that some location-based things are still necessary, for example, default fonts for Japanese customers and Canadian customer are not likely to be the same. And given that space is limited, the loaded dictionaries could also be different, from one part of the world to another. That being said, it looks like there is something afoot to get a whole whack of code the same regardless of what Kobo eINK device people use, or where they are located when they activate the device. Now (yes, still more speculation), Kobo actually knows what builds/firmware is out there. And they can figure out how to clean up this issue as long as they can pretty much count on all of the builds sitting on devices being official ones that were laid down on top of them. Add in variations never meant to go on top of the builds on their list, and potentially weird things could happen when the official build is released. Stick a fork in me; I'm done. Last edited by taming; 09-13-2012 at 02:46 PM.