Quote:
Originally Posted by BeckyEbook
The connection is simple.
Parsing encounters erroneous incompatible quotes, which results in the inability to check the rest of the text where the footnote text is located, hence the message about the unidentified fragments.
Incompatible quotes are dangerous and I don't understand where they would come from in Sigil, which takes great care to ensure that the code is well-formed. You simply have to be careful when editing your code to avoid such situations.[/CODE]
|
OK, thanks Becky, that's an explanation.
Of course these errors come from editing and my concern is with author friends learning to use Sigil. I wouldn't advise them to use Mend and Prettify to correct for an accidentally erased quote. They wouldn't understand the result.
Further checking of my quotes and missing angle brackets cases found that all resulting fragment errors were down to nav links in that xhtml file and their correspondents in the HTML Contents and NCX files. Since my test document was a non-fiction epub with h1, h2, h3 levels of contents, that explained the number of fragment problems.
Your comment about the parsing encountering an error and being unable to check the rest of the file explains all. Perhaps it would be better to ignore the rest of the file or just the links, once an error has been encountered rather than listing 'errors' that do not or may not exist.
In any case, we have to rerun the plugin after fixing the real error and if there are really unidentified fragments they could be listed in a subsequent run.