View Single Post
Old 05-19-2011, 07:00 AM   #2
pdurrant
The Grand Mouse 高貴的老鼠
pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.pdurrant ought to be getting tired of karma fortunes by now.
 
pdurrant's Avatar
 
Posts: 74,002
Karma: 315160596
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Oasis
Quote:
Originally Posted by Stodder View Post
Hi guys,

I promise not to ask another question here for the next few days, but I just had to get an opinion on this :

What's the best doctype and charset to use for creating Kindle-compliant mobi files? I'm thinking of using XHTML Strict and ISO 8859-1.

Will this be compliant, and will it be able to handle named character entities (— et al)? My validation has come up clean, but I'm never sure what to make of charsets and the associated dtd stuff.

Any help would be great :-D

Stodder
I'd recommend XHTML 1.1 Transitional, but be sure to limit use to XHTML that's valid in the ePub 2.0.1 spec.

And then you'll probably want to limit even more to things that convert to Mobipocket well using kindlegen.

You should definitely use utf-8 as the character encoding, as that's a requirement of the ePub spec (well, or UTF-16, but that would just be silly.), and is also handled well by kindlegen.
pdurrant is offline   Reply With Quote