@
skreutzer calibre is actually quite good about xml, it will only convert books into strictly xhtml-compliant code. So since the problem with the <u> tag has nothing to do with conformance to xml, but s rather an html and by extension an html-as-it-relates-to-xhtml problem, can we stop dragging xml workflow into it? Even though it is a cause you care about?
Quote:
Originally Posted by DaleDe
Go read the xhtml 1.1 specification and you will see. You can also look at the list of supported tags in our wiki for ePub. I was just commenting on the fact that someone claimed that ePub wasn't XML compliant but it is.
Dale |
I never claimed <u> is a valid part of the epub spec. I simply said it has nothing to do with the xml aspect of it.
Quote:
Originally Posted by DiapDealer
Oh what a tangled web we weave...
There really is no epub "standard" when all is said and done. There's just one organization's published "specifications" that the rest of the world cherrypicks and deviates from as they see fit. It's a glorified wishlist... and it'll never really be anything but.
|
This is exactly why in real life <u> works for ebooks.