Hi,
FYI, KF8's internally are almost a one for one mapping to the AZK format, with the same skeleton, and fragment sections. The only real differences are that azks are just encoded by a special dictionary based word compression scheme and encoded into json.
To test this I converted the same epub into kf8 andazk using kindlegen and studied the differences which were quite minimal. Both are set up to allow "fragments" of up to 8000 chars or so to be loaded upon demand inside a page "skeleton". KindleUnpack simply builds up the original pages from the fragments and skeleton info provided in the KF8 (and then does a lot of link fixups, css link fixups, and etc) to create an epub-like structure.
This is perfect format for limited memory phones and tablets with their own webkits and web-based technologies.
I could never fully figure out the encoding/encryption used for the dictionary based word compression scheme of the azk otherwise I would have modified KindleUnpack to unpack them as well since much of the code would be re-usable from the kf8 code.
Given how much morewe know based on this thread, I may decide to revisit it.
Hope this helps,
KevinH
Quote:
Originally Posted by DaleDe
At one time the Apple viewer was KF7 but when AZK was released it became like the Amazon tablets, a dual reader except instead of KF7 fallback from KF8 the Apple Kindle reader is AZK with a KF7 fallback. It does not read KF8 at all. It is not clear why Amazon developed two formats but perhaps they are testing an intend to adopt only one of them in the future.
Dale
|