Sigil uses Google's gumbo parser which follows the rules of html5 parsing standard according to the whatwg browser standard. In other words, it does exactly the same thing that Chrome, Edge, Safari, and Firefox, does when faced with that same broken code.
As for more details, once loaded Preview will show you exactly where and what well-formed errors exist on a file by file basis if desired.
Just turn off Mend on open. Load the epub "as-is". Hit checkpoint (one mouse click). Run Mend. Compare against the fixed code to see everything that gumbo fixed or changed.
Or instead of Mend, just run a basic well-formed check (see Sigil's menus), which is a basic validator that will show you just serious well-formed errors.
You have options. Loading an epub is not going to give you a complete list of errors like a validator will for speed and missing interface reasons but can load them "as-is" for you to validate, or hand fix, or can auto fix them for you.
Quote:
Originally Posted by democrite
What I am uneasy about is I'm not sure what Sigil does in the cases when there are errors to fix, e.g., I may miss a close tag, or change some paragraph to header but make a typo such as <h2>…</p>. Of various errors, I am not sure if the automatic fix is what I'd prefer.
If it were possible to distinguish between such malformed errors and others such as merely fixing doctype or other metadata, that would save a lot of time rather than having to as you suggest checkpoint and compare. Often I am editing outside of Sigil as another editor I find quicker to load up an EPUB, and perform regular edits. I understand Sigil does not fully validate the EPUB; it would just be nice to have more clarity in the message.
|