View Single Post
Old 02-14-2017, 08:20 AM   #16
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,762
Karma: 206758686
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JSWolf View Post
I cannot say. I do know that ADE forces UTF-8. But I'm not up on all ePub readers. I know Kindles do not and if you convert such an ePub, you will get incorrect encoded characters.
The meta tag attribute isn't necessary. EPUB only supports UTF-8/16. So if a valid epub goes into kindlegen, no character-encoding issues will arise. Besides ... 'encoding="utf-8" ' is usually already included in the xml declaration of most epub xhtml files.

Kindlegen supports other character encodings on other type of kindlebook sources, but that wouldn't apply to valid epub sources being converted (which MUST be UTF-8/16).

There is no "forcing" of UTF-8. Any epub rendering system that doesn't assume UTF-8/16 is a broken epub rendering system. And any epub that isn't UTF-8/16 encoded (regardless of whether your meta tag attribute is present) is a broken epub archive.

Last edited by DiapDealer; 02-14-2017 at 08:30 AM.
DiapDealer is online now   Reply With Quote