Quote:
Originally Posted by Sella174
Quote:
Originally Posted by Doitsu
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.
|
It does work and is documented in the “official” examples [...] |
What "official" examples are you referring to?
Quote:
Originally Posted by Sella174
[...] but wasn’t that the point: me giving an example of something valid for KindleGen that produces an invalid ePub?
|
Not really, if you manifested all unmanifested files, KindleGen would continue to work and you'd end up with a valid epub.
You also claimed that it isn't possible to create valid epubs with Amazon guide items with Sigil, which simply isn't true.
Quote:
Originally Posted by Sella174
Character encoding in HTML5 is done with <meta charset="UTF-8">, but KindleGen still requires the depreciated HTML 4.01 method of <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">, even though the file is read as HTML5 if defined as such.
|
The current KindleGen version does
not require these declarations.
Quote:
Originally Posted by Sella174
Quote:
Originally Posted by Doitsu
In fact, according to section 2.2.1 of the Kindle Publishing Guidelines, Amazon recommends using valid epub books.
|
Not in version 2017.4 of that document. |
Quote:
|
Originally Posted by Kinde Publishing Guidelines version 2017.4
2.2.1 KindleGen
Publishers can create Kindle files in-house by using a free software program called KindleGen. [...]
To create Kindle files using KindleGen, you need:
|