Donec cursus, metus et aliquam pulvinar, mauris quam dignissim dolor, ullamcorper tristique leo elit quis augue. Aliquam sagittis ex at dolor tincidunt, eu ultrices nisl iaculis. Suspendisse blandit accumsan risus a consequat. Curabitur ornare ac lorem ac ullamcorper. Foreword Lorem ipsum dolor sit amet, consectetur adipiscing elit. Produce files on any platform, what is impossible with Kindle Previewer.Control resulting file, what is impossible with closed-source tools.After that, we could possibly work on adding KF10 support, though it might be harder because KF10 was not reverse-engineered/documented yet (or I just didn't find that info yet). When it's done, asciidoctor-epub3 will be to produce KF8 files without any Kindlegen. I had little spare time last year to finish KF8 part, that will hopefully happen early this year. It already can do MOBI6 and almost can do KF8. It is also closed-source, so cannot be fixed directlyĪs I already said above, I've started writing a library that aims to be EPUB3 -> MOBI6 + KF8 converter.It cannot produce KF10, that's why Kindle Previewer complains about lack of Enhanced Typesetting.It is closed-source, so when it has bugs, they have to be hacked around in EPUB3 that is fed into Kindlegen (that's why asciidoctor-epub3 produces a bit different -kf8.epub file).It doesn't exist for modern MacOS, neither 圆4 nor ARM.It no longer has legal distribution way.Kindle Previewer doesn't have KF8 -> KF10 converter. Now, what does "this file doesn't support Enhanced Typesetting" mean? It means that file is not a KF10 and not a EPUB3, so Kindle Previewer cannot convert it to KF10. Kindle Previewer also can do EPUB3 -> KF10 (supposedly, combined with MOBI6/KF8, I didn't check). Kindlegen is a EPUB3 -> MOBI6+KF8 converter. UPD: Google says that KPF is only an intermediate format that is never uploaded to ebook. I don't have a prooflink currently, but it is very likely that a single file can contain all three MOBI6 + KF8 + KF10. This is what Amazon calls "Enhanced Typesetting" thing. One file can contain KF8 and MOBI6 at the same time and this is what kindlegen produces. To make things confusing, KF8 files can be named. On this level of abstraction, file doesn't have any relation to ebooks at all. Think of it as something like an archive that can hold multiple (this is important) entries inside. azw files are actually PalmDB containers. still epub, just with tweaks for Kindle)? Can anyone confirm? If this is indeed the case, would it be possible to add an option to asciidoctor-epub3 to produce just that file and not try to run kindlegen on it? That is currently the missing piece for me to still be able to produce an output format for kindle through CI builds.Īll this terminology is kinda confusing, let's make it clear:
I'm wondering if the most appropriate format for distribution to Kindle is now the *-kf8.epub (i.e. This would suggest that epub is now the format that should be used even for Kindle. This MOBI file should only be used for testing on older devices that do not support Enhanced Typesetting. NOTE: Please use your original source file (EPUB or DOCX) for publishing. Selecting the latter, it pops up a dialog with the following note:
More interesting though, if you then try to export the result, you can choose *.kfp format (which seems to be specifically for reloading back into Kindle Previewer) or *.mobi format which it labels as "to side-load on older Kindle Devices". Furthermore, if you import a *-kf8.epub file into Kindle Previewer, it does so successfully and even enables Enhanced Typesetting. mobi files (when there is a kindlegen available). However, it does load the *-kf8.epub file that asciidoctor-epub3 generates on its way to producing the.
mobi files (it did previously for the same file(s)). I was just experimenting with Kindle Previewer 3.49 (latest available release) and it no longer loads the previously generated. I'm wondering if we actually need to convert from the epub format to mobi any more.
0 kommentar(er)
