Quote:
Originally Posted by tomsem
Yes, I can appreciate that Amazon would want to avoid inserting (many) characters into the content stream. So they compute offsets into that stream (representing positions where hyphens can be) and store those in a separate stream, and they can merge these very efficiently as the content stream is read into memory and page layout is applied.
The computation is done in the cloud (once for each title, and re computing whenever they update the hyphenation behavior), obviating the need for (at least several) hyphenation dictionaries on the device, eliminating CPU usage to do hyphenation lookups, and also lets them refine the hyphenation behavior without any device updates.
|
While this is a plausible possible implementation, it does not match my understanding of how hyphenation is accomplished in KFX.
Do you have any evidence to support this?
----
I have converted several very short test books to KFX using Kindle Previewer 3 and the KFX Output plugin for calibre. I was able to account for every data structure present in the converted books and found nothing related to hyphenation. Despite that, these books are properly hyphenated when read.
In addition, I
have found hyphenation dictionaries present in all of the KFX rendering software that I have examined. For example in the latest Kindle for PC, the file "res.dat" contains hyphenation dictionaries in multiple languages.