Quote:
Originally Posted by Arios
The funny thing is that Sigil insert the codes <u></u>, the less funny thing is, as Doitsu and eschwartz said, epubcheck as well as FlightCrew do not like those codes... And specs are specs  |
True. But the button is there because there was a wysiwyg cry for such a thing. And making the button underline text in a spec-compliant AND sane method would be nothing but trouble: do we create inline styles; do we create a new class in the css file for each occurrance (do we create/link a css file if one doesn't already exist)? Do we parse existing css (both inline and external) to see if a suitable class to be used already exists? What if inheritance from a pre-existing class clobbers Sigil's efforts to create the underline? It's a nightmare any way you look at it.
My personal preference would be to give U tags a free pass in Sigil's well-formed check, if at all possible. Let the epub validators do all the barking about them. Short of that, I guess I'd like to see it (the button) made unavailable in documents where Sigil/gumbo deems them un-spec-worthy.
Good stuff!
