View Single Post
Old 02-24-2014, 03:37 AM   #11
Jellby
frumious Bandersnatch
Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.
 
Jellby's Avatar
 
Posts: 7,556
Karma: 19500001
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
Quote:
Originally Posted by roger64 View Post
- wrong, because formally, EPUB 2.0.1 which is the latest iteration of the official norm before EPUB 3, still relies on xhtml 1.1 specs, for which the DOCTYPE is an absolute requirement. Point.
I don't see that. Where is it stated that ePub documents must be valid XHTML 1.1? As I said above, they must be vaild XML, with XHTML.

Quote:
Originally Posted by roger64 View Post
I just spoke about UTF-16 because I had read (where?) that calibre editor used hexadecimal unicode characters. I knew no more about this. It would have been better to write only: Unicode characters.
You are mixing several things:

Named entity: é (needs DOCTYPE)
Decimal entity: é
Hexadecimal entity: é ("x" means it's hexadecimal, where "e" means fourteen, so "e9" = 15*16^1+9*16^0 = 233)
Unicode character: é

The Unicode character may be actually stored as utf-8 or utf-16, but that's mostly invisible to the user:
In utf-8 it will be saved as: C3 A9 (two bytes)
In utf-16 it will be saved as: 00 E9 (two bytes)

Last edited by Jellby; 02-24-2014 at 03:44 AM.
Jellby is offline   Reply With Quote