public marks

LINK

What I’d change about ePub : Threepress Consulting blog

by karlcow, 2 comments

Support any valid form of XHTML

XHTML 1.1 was obviously a mistake, as it’s used (as far as I know) nowhere else, and is a dead-end as far as web technologies go. Few automated HTML tools generate it, and the changes from XHTML 1.0 are simply annoying rather than useful.

I’d prefer that ePub support XHTML 1.0, which is simply HTML 4.01 with an XML vocabulary. HTML 4 is the dominant form of HTML on the web (and will remain so for some time) and common automated tools like Tidy can clean up “street” HTML 4 into XHTML 1.0 quite well. Tidy won’t, however, produce XHTML 1.1.

I also don’t want to put an upper bound on the XHTML supported: XHTML 5 should also be okay, and the rules for a reading system which don’t support later tags should be the same “ignore and move on” that has worked well on the web.

Comments

Sauf qu'HTML 5 ne fonctionne pas en mode "ignore and move on" (en particulier pour les balises "date" et "time").

night.kame said at 15:46 the 10/01/2010

Je retiendrai de cette page le commentaire suivant : "2. Add styling (or add CSS extensions) so that we can mimic word processing programs style inheritance. (CSS cascade idea is just a bad hack from authoring perspective as well and IMHO should be avoided. I cannot image an intuitive WYSIWYG program that would expose CSS cascade to the user)"

night.kame said at 15:52 the 10/01/2010


PUBLIC TAGS
on this link

epub   html5   xhtml  

BY

karlcow
the 10/01/2010 at 14:54