Quote:
Originally Posted by Sella174
Linked files need not be defined in the OPF under <manifest>, e.g. external stylesheets or images (other than the cover). KindleGen either finds them by itself or throws a warning. (Warnings do not stop compilation of the mobi, just like with a “real” compiler.)
|
Using unmanifested files with KindleGen
might work, but you're not following best practices; it'll also ensure that an epub book assembled from these files will be invalid.
Quote:
Originally Posted by Sella174
How the <guide> section in the OPF is interpreted.
|
Even though most epub2 apps will ignore the guide section, adding the guide items recommended by Amazon won't invalidate an epub book, because they're a part of the
epub2 specs. BTW, Sigil has a dedicated menu option for adding guide items (Add Semantics...).
Quote:
Originally Posted by Sella174
Depreciated method (in terms of HTML5) for declaring UTF-8 as the character encoding.
|
Epub2 books are supposed to contain utf-8 or utf-16 encoded (X)HTML files and, AFAIK, KindleGen does not require deprecated character encoding declarations.
In fact, according to section 2.2.1 of the Kindle Publishing Guidelines, Amazon recommends using
valid epub books.