Quote:
Originally Posted by KevinH
My guess (complete wag) is they map a reflowable epub into a size fixed to a specific device (or family of devices), handling automatic hyphenation (since the boundaries are now known), and then use webkit to effectively "print" it to a pdf-like format, and deliver that to your device. Kerning, ligatures, font metrics (known fonts!), hyphenation positions, Dropcaps, etc can all be worked out in advance in a fixed layout and converted into a form suitable for viewing. Then sell the whole pile as "Enhanced formatting" which is similar to what can be achieved in a finished format like pdf
|
I don't think it's quite that bad. They are still using a reflowable document model, it's just not html.
A lot of what got added in that intermediate html file shown by baf doesn't appear in the kdf output. It looks to me that they are determining the final styling result of css for each html element and then translating that to their own simplified binary document model.
I don't see any sign that they are pre-rendering to specific devices. That would be difficult given all of the possible font-face/size combinations and screen sizes for all iOS/Android devices. Also, I have been able to move non-device locked kfx files between devices of different resolutions and they rendered just fine.
Drop caps appear to be handled by using their own non-standard style properties created just for that purpose.
The document text doesn't appear to be altered at all. I think that kfx hyphenation is handled by the renderer on the user's device using a dictionary.