Quote:
Originally Posted by kovidgoyal
Automatic correction of invalid html is not going to change. It is the foundation of many robust features in Tweak Book. I find the entire idea of software that refuses to render html because it is not valid XML, ridiculous, it is simply too easy to generate non well formed XML. Fortunately, the larger web development community agrees with me, see HTML5. If ebooks had developed just a few years later, epub would have been based on HTML 5 instead of XHTML and everyone's life would have been a lot better. Remember that Tweak Book is not a epub 2 specific tool, unlike Sigil. Therefore, its fundamental design choices are not going to be limited by epub 2.
|
Kovid:
I know you said you were through discussing this, but my sole comment, if I may, is that having Tweak "auto-fix" HTML, as it does, gives the creator no audit trail. Using the example provided,
without proofing the entire book, you wouldn't find that the closing italics tag had been moved to the wrong place. From my own standpoint solely (understanding quite clearly that my needs are very different from most here), this would never work for us.
Is there any possibility that at least an audit trail of the auto-fixes could be somehow visible? e.g., a "fixed this" report of some kind?
For anyone making other people's books, using pretty cruddy manuscripts, this could be sort of death-defying. I understand your philosophy: Calibre helps those who cannot help themselves. And, Calibre is not really designed for "my ilk." But as this is intended to be a successor to Sigil, it would be great if at least the changes made were not silent, somehow.
Is there a way that
that could be done? Which would replace the need for the "stop rendering" methodology that Sigil currently uses?
(Just asking.)
Hitch