To make things confusing, KF8 files can be named. On this level of abstraction, file doesn't have any relation to ebooks at all.
#Kindle previewer for docx files archive
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)
