Quote:
Originally Posted by tomsem
On Kindle, it is computed from ‘locations’, which is the arbitrary, algorithmic method they came up with to sync reading position between the different devices supported on Kindle platform since the very first Kindle. It tries to reflect the ‘amount of reading’ you have done
|
That makes it sound much smarter than it is. The design is clearly aimed at sheer implementation simplicity over everything else. A single location value is 128 bytes long, with a new location starting at every offset through the book's text divisible by 128 bytes (not Unicode codepoints, not characters-not-counting-spaces, bytes): in MOBI and AZW this counts the (invisible) markup, in KFX it seemingly does not (so you can get different location counts and total lengths by switching from a AZW to a KFX version of the same book. As an aside, I wonder if this suggests that in KFX the markup is out-of-band somehow and points into the text from "outside", and both location implementations are just counting bytes in a byte stream).