(Think of it as "not only was the code they use scrambled", but they took the effort to scramble it differently each time ixtab made some advances.) mobi - Amazon reacted highly agressively and confrontational, changing the obfuscation of the code repeatedly, in short term intervals. When ixtab (the author of JBPatch) worked on making tweaks possible to the viewer engine for. kfx is so closed down - lets call it "in a class of its own". azw3 is the best possible (objectively) format for another one mobi is the best possible (objectively, looking at the featureset) format for one. kfx) entirely separate eBook Viewers (render engines) on Kindles. On every other firmware version you go with azw3 - because you can add hyphenation (soft-hyphens) to it using a Calibre Plugin called "hyphenate this".Īs for the "why?" that almost lies embedded in this two answers -Īmazon uses three (? new one for. mobi - because of JBpatch's hyphenation (best in class for a Kindle) and page formating options. On a Kindle where JBPatch still works (we are talking firmwares from around 2013) you go with.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |