#Kindle previewer 3.5 text to speech code#
yjhtmlcleanerapp, which cleans up code that goes in the way.mobicontentdumper, which dumps the mobi files generated by KindleGen as json files.EpubToKFXConverter-1.0.jar, the KDF converter.There is a lot of interesting stuff to be found in KP3’s package: That could be an intermediate format like AZK-only this time they didn’t bother or have time to implement a bridge inside apps which support KFX. Kindle Previewer 3 (beta) outputs KDF files, which is basically KFX data in an sqlite3 database instead of a KFX container. The addition of Bookerly seems to be a hint, though. KFX is usually not mentioned in the release notes of Kindle updates. Indeed, it looks like it would be pretty useless to convert KFX to ePub (more about that later). While this is pure speculation, another goal may have been the creation of a stronger walled garden. the renderer computes an WCAG2-compliant contrast ratio: color for text on background.Īs the previous renderer (for KF8) performed very poorly with kerning and ligatures, it could explain why they decided to build a new one and manage a lot of stuff when processing files so that the new renderer doesn’t have to.the renderer supports gaiji images ( inline images).the renderer takes user settings into account and will adapt drop caps, H&J and float images dynamically once a critical font size is reached.What they don’t advertise though, are clever features that will enhance the user experience: KFX brings support for drop caps, hyphenation & justification (H&J), kerning, ligatures, etc. The hyphenation engine is not written in JavaScript.Hyphens are turned on/off using -webkit-hyphens.It seems specific versions are prepared and delivered depending on device (e.g.Color images are delivered in JPEG (at least in iOS).Grayscale images are using an high compression format called JPEG-XR (transparency is not supported at the moment).Contents are divided into small JSON files (like AZK and KCR, you can go check online for the latter).Contents (excepted images) are encrypted/ofbuscated (AES-256) for both DRM-protected and -free files.Like KF8, KFX is using a webkit-based rendering engine.But it was intended for magazines at first.
It looks like KFX has been around since 2013. EpubToKFXConverter-1.0.jar is bundled with KindlePreviewer (like azkcreator for AZK) so you can probably make use of your command-prompt-fu to access it (see this post in MobileRead forums). And there is no publicly distributed converter for those two formats. Strictly speaking, KindleGen is no longer involved at this AZK/KFX conversion level. That is still unclear though, so correct me if I’m wrong. JavaScript built on top of jQuery and making use of webviews. In other words, it is somehow likely the new Kindle renderer is sharing common traits with Kindle Cloud Reader, i.e. So, to sum things up, like AZK (and KCR), KFX is a binary version of JSON (JavaScript Object Notation). Kindle Cloud Reader for iOS has been partly documented and implies a lot of HTML + CSS sanitization. More technical details about AZK here and there.Īs a reminder, AZK is not the file Kindle for iOS uses, it is indeed converted to KCR (Kindle Cloud Reader) when you sideload it on your iDevice. It seems KFX is a follow-on AZK, the Kindle format for iOS you’ll get when using Kindle Previewer 2.94. Thanks to jhowell, and all the others folks in the MobileRead thread, whose research proved so valuable when inquiring into dat shit. I’ll quote from and refer to that thread’s posts since it would be disrespectful to steal and paraphrase. Please note some folks have been retro-engineering already. Inquiring further into Kindle Previewer 3 (beta), we may get a hint of the conversion process to KFX.Īt first sight, the process is epic.
0 kommentar(er)
