Quote:
Originally Posted by Hitch
My last direct experience with this was quite simply that using direct styling in the form of "u" did not pass ePUBcheck; I vaguely recall a discussion in-house about the inconsistency with b and i and u; and I'm fairly certain that the latest ePUBcheck will puke on underlining styling that's done directly.
|
EpubCheck 4.0.1 will flag <u>...</u> in an ePub2 book as an error:
Code:
Error while parsing file 'element "u" not allowed anywhere; expected the element end-tag, text or element "a", "abbr", "acronym", "applet", "b", "bdo", "big", "br", "cite", "code", "del", "dfn", "em", "i", "iframe", "img", "ins", "kbd", "map", "noscript", "ns:svg", "object", "q", "samp", "script", "small", "span", "strong", "sub", "sup", "tt" or "var" (with xmlns:ns="http://www.w3.org/2000/svg")'.
but is OK with <u>...</u> in ePub3 books.