Fix unresolved exception ZMQ entity references - #5776
Conversation
|
What entities is docbook-cs not detecting? DTD entity references, or the targets of XPointers, or other cases? It's important to note that changing DTD entity references around will change the final XML structure, so XPointers need to be also changed, and that is ok. But changing DTD entities around to fix unresolved entities appear to be a form of loading order mismatch. So to be sure:
This is the "macro order" or "tree building algorithm" of HTML, that I think that xmllib does, while assembling the manual. But the more general question is why docbook-cs is hitting undefined entities that libxml does not. |
|
So the exact errors for this PR are: The real reason libxml doesn't catch these errors is because these files are never loaded by the manual. They were absent in The XPointer changes are a side effect of the files being loaded. Docbook-cs doesn't check. configure.php does. As a side note, I am planning to load |
Ah, you found out files not included in XML assembly. That was unexpected.
Please, do. doc-base 321 is now merged. I will wait for the manual to build and publish before erasing the PR branch, but I expect the change will build ok. After this settles, then all loading of DTD files can be replaced by the loading of doc-base/temp/doctype.dtd. |
A few more follow-up MRs to come. The main goal is to bring docbook-cs to a state where it reports no unresolved entities.
These errors are caused by incorrect or outdated references.
I have not verified whether the synopsis is correct; that is out of scope.