View Single Post
Old 04-18-2014, 04:51 PM   #31
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by skreutzer View Post
Just think about this issue as follows: EPUB gets processed with XML tools. XML tools use XML schema validation. The validation fails for an invalid EPUB input file. What are web services supposed to do in such a case? The initial post about <u> invalidity didn't mention if this issue was raised by a web service or processing tool or if the user just did a validation voluntarily, but at least he posted the issue and asked for a solution. Can he solve it in Calibre? Manually or automatically?
And the <u> tag will pass xml validation.

Granted, it may fail xhtml validation....

Yes, it can be solved in calibre. regex it out. Or convert it with calibre and create beautifully conformant xhtml.

Regardless, it is more important to sell a working book than to comform to the standards. Change must start with the distributors who enforce noncompliant ebooks.

Last edited by eschwartz; 04-18-2014 at 04:56 PM.
eschwartz is offline