View Single Post
Old 04-25-2017, 03:22 PM   #5
tomsem
Grand Sorcerer
tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.
 
Posts: 6,955
Karma: 27060153
Join Date: Apr 2009
Location: USA
Device: iPhone 15PM, Kindle Scribe, iPad mini 6, PocketBook InkPad Color 3
Quote:
Originally Posted by jhowell View Post
I disagree with whoever wrote that in the wiki. That was early speculation, since disproved.

The original post also mentioned koreader. As far as I know that doesn't support KFX. I don't know whether or not it supports hyphenation some other way.
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.

Last edited by tomsem; 04-25-2017 at 03:25 PM.
tomsem is offline   Reply With Quote