Quote:
Originally Posted by AlexBell
@Doitsu: So far as I can tell the process of using Kindlegen to make a mobi file is quite different from the process used to make an ePub file - so far as I know the HTML has to be one big HTML file for Kindlegen, but it is best practice to have one HTML file per chapter for ePub. The ebook I'm working on has around forty chapters or sections. It is this doing things differently that I want to avoid. I'd much rather do the ePub as usual then zap it with something to produce the azw3 level mobi.
|
Kindlegen can process unmodified epubs, and epubs that pass epubcheck will usually compile without errors. I.e. you don't have to change the structure of your epub at all, unless you've defined dropcaps, which need to be slighly adjusted for Kindle books.
However, if you use Kindlegen, you'll also need to define the beginning of the book (AKA SRL=Start Reading Location), the HTML TOC and the cover image or the title page with
guide items. In Sigil, you'll need to manually define these items with
Add Semantics > Text/Table Of Contents/Cover or
Cover Image. (Calibre does this automatically.)
BTW, as you probably know, KindleGen will automatically generate hybrid .mobi files that contains both old and new formats. You
can define fallbacks for the older format using media queries. You can for example replace dropcaps with large bold letters. For more information about this, see the
Kindle Publishing Guidelines. However, these fallbacks are not required because Kindlegen will ignore unsupported elements by default.