In the thread about Sigil's error messages, I said I was surprised that a single mismatched quote in a class identifier caused the EpubCheck plugin to record numerous errors related to "unidentified fragments" in the HTML Contents and the NCX files. Errors which vanished once the original mismatched quote was corrected. BeckyEbook explained this in a reply:
https://www.mobileread.com/forums/sh...9&postcount=19.
I recently saw another example where an accidentally erased '<' at the end of an early paragraph in one of the files caused EpubCheck to produce 26 error statements for that file, none of which was the actual error.
If the plugin identifies an error in a chapter, the user has to rerun the plugin after correcting the error so the validation process is always likely to involve several iterations of the use of epubcheck.
To avoid the listing of numerous non-errors, would it be possible for the plugin to log the first error and then exit that file and progress to the next file?
Just a thought from a comparatively non-techie user.