- Joined
- Feb 13, 2011
- Messages
- 161
- Reaction score
- 2
Hi guys,
I was thinking about ebook back-compatibility and future-proofing, and was wondering if anyone knew of the perfect setup for handling for this?
I'm guessing that the areas of concern where are doctypes (XHTML, HTML), charsets, and entity usage (named, numerical, or direct character injection into something like UTF-8?). What's the best combo of these things?
Some things I've started to realize (and please correct me if I'm wrong, as I'm a newbie):
Any help would be great
Todsplace
I was thinking about ebook back-compatibility and future-proofing, and was wondering if anyone knew of the perfect setup for handling for this?
I'm guessing that the areas of concern where are doctypes (XHTML, HTML), charsets, and entity usage (named, numerical, or direct character injection into something like UTF-8?). What's the best combo of these things?
Some things I've started to realize (and please correct me if I'm wrong, as I'm a newbie):
- Numerical entities are supposed to give old kindles some trouble.
- UTF-8, in general on the www, does not need entities, and can support direct injection of the character[SUP][1][/SUP][SUP][2][/SUP], but most people who use UTF-8 in ebooks seem to also put the named entities as well.
- I believe earlier Kindles had initially more support for ISO-8859-1 than UTF-8, making me wonder if UTF-8 HTML docs will be okay on ye olde Kindles.
- I've read that at one stage, Kindle DTP required people to use named entities over numerical ones--atleast the accounts form people at the DTP forum seem to suggest this[SUP][3][/SUP]. However, the current guide on their site does not mention named entities at all[SUP][4][/SUP].
- The release notes inside the zip file for the latest version of KindleGen states that Kindlegen has "changed default encoding of the generated books to utf-8."[SUP][Link to download page of latest version.][/SUP]
Any help would be great
Todsplace
Last edited: