Quote:
Originally Posted by isarl
I may be wrong but these particular errors look to me like the file is already encoded as UTF-8. The problem is not how it is encoded, it is how it is being decoded.
|
Which Amazon does if the UTF8 statement is missing in an epub.
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
If the charset is not defined Amazon assume it's CP1252. Some sort of throw-back to early days of Mobi on Kindle. Amazon bought Mobipocket, the biggest seller of ebooks on Windows CE, Symbian and Palm OS the year Sony brought out eink (2005) and first Kindle was 2007.
Historical stupidity.
Use Modify Epub tool or edit existing <meta http-equiv="Content-Type" content="text/html> (or whatever) to <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> at the top of every HTML file.