Quote:
Originally Posted by eschwartz
@ 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?
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.
 This is exactly why in real life <u> works for ebooks. |
You are correct that <u> is not in any way related to xml. In XML you can define the meaning of any tag to be anything you wish, so long at the structure rules are maintain and you have a definition table available to interpret the meaning. XML is a very generalized specification of which xhtml is one specific implementation and is the one chosen by ePub.
Dale