Quote:
Originally Posted by KevinH
For speed reasons, Sigil will simply look for no errors when loading a document. Sigil's importer is not a full validator nor does it have the interface to be one. If any errors are detected, the user is warned that errors exist.
You do not need to worry about loading an epub that is well formed in Sigil. There is no need to pass epubcheck before being loaded in Sigil.
Sigil will warn only when it finds something it does not consider spec and will offer to automatically fix it for you.
I think you see that message about the possibility of data loss, and it gives you pause. Any fears here are very overblown. Actual data loss is very very rare and only happens due to the xhtml text not being at all parseable (ie so broken so that gumbo's parser can not read it).
Simple things like missing doctype, missing html tag, etc, will always be happily and safely be fixed by Sigil's gumbo parser during Mend.
…
|
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.