Quote:
Originally Posted by Doitsu
@eggheadbooks1: You can ignore all confusing Amazon statements about Unicode support for the following reasons:
1. As far as Kindle books are concerned, only KindleGen Unicode support matters, and KindleGen and its precursor MobiGen have supported Unicode for a long time.
2. The epub2 specs require all books to be encoded as either utf-8 or utf-16. (utf-16 was presumably only added because it can theoretically reduce the size of CJK HTML files by 20-30%.)
3. KindleGen explicitly supports valid epub2 and epub3 books as input files. (KindleGen doesn't support all epub3/CSS3 features, though.)
Code:
Usage : kindlegen [filename.opf/.htm/.html/.epub/.zip or directory] [-c0 or -c1 or c2] [-verbose] [-western] [-o <file name>]
For all these reasons, utf-8 is the best format for both epubs and Amazon KDP books.
|
Exactly. I've been doing the Sigil-convert-to-mobi-in-Kindlegen for my ebooks for the last several years, and this has always created the best results. So I find Amazon's Guideline's strange. And as far as fonts are concerned, the guide mentions Monospace font as a secondary option that does not need to be embedded; why not also mention Unicode? It's a mystery. But then that's Amazon.
Which is why I come here for help, and not KDP's alleged technical help department, which is manned by people for whom English is a foreign language and who often don't understand complex questions. I gave up on them a long time ago. When Amazon/Adobe first developed the InDesign Kindle plugin, there was a feedback button that sent one's email directly to the Kindle programming team; THEN you got proper answers. But now that feedback button links (or is forwarded) to the KDP help department, which as stated is of no help at all.
