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.
In earlier versions of Sigil before Sigil 1.0, Sigil just quietly fixed these errors for you while moving all files to their Sigil standard locations.
From Sigil-1.0 to Sigil-1.3, once moving to "standard locations" stopped, errors due to missing doctypes started to happen but not be fixed or detected until another Sigil tool was run that needed gumbo.
From Sigil 1.4 onwards, we now properly detect the missing doctype and warn the user on load so that they run Mend (after load) or we do it for the them depending on user Preferences.
If you truly do not want to auto run Mend on open, set it to that in your Preferences. If you want to see what is broken that mend fixes, then checkpoint it after load and then run mend, and then compare it against the checkpoint.
Quote:
Originally Posted by democrite
Nice.
If it is ok to request something that I hope you will consider and may include, either with the upcoming version, or later, I have found the new error message upon EPUB open with possible errors a bit confusing.
There are times when I edit an epub outside of Sigil and may introduce syntax errors that may possibly lead to data loss as mentioned by Sigil. Then there are more frequent times when I open a commercial EPUB in Sigil and the possible fixes are perhaps only metadata such as DOCTYPE, missing head elements, etc. Generally if I am making an EPUB myself, I I don't mind running epubcheck before the next opening with Sigil in case I messed up something. In the case of editing commercial epubs, it'd be nice to not to have run epubcheck each time before first open with Sigil to verify it is ok. More detail of the errors would be nice and I think help avoid potential data loss and save effort of verifying the EPUB when it is unneeded.
|