Quote:
Originally Posted by kovidgoyal
Umm come up with an automated way to take arbitrarily bad HTML ad produce standards compliant XHTML from it while still preserving its meaning to human readers and I will be happy to implement it.
|
Hmm... If it can be displayed by a (X)HTML viewer, it can be converted to valid XHTML, can't it? I mean, if there are unclosed or invalid tags, the viewer already has to do something about them, so it can be done. There is the problem that different viewers might do different things, but that's the problem of non-compliant sources
In practice, I guess you could add a flag to "force ePUB compliance" or issue a warning if the generated ePUB is non-compliant.
I'm still an idealist, and think that we should press Adobe to make their reader standards-compliant and hope that other companies, groups or individuals develop independent standards-compliant ePUB readers. Then, when it comes to convincing someone to fix a bug in their readers, it's probably better to say "it does not work with this standards-compliant files" than "it does not work with this file that happens to work in ADE".
