We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Discovered with the help of https://github.com/belingueres/xml-conformance
MXParser fails on parts of the W3C XML Conformance Test Suite.
In this issue, it is failing ibm66n01.xml, ibm66n03.xml, ibm66n05.xml, ibm66n07.xml, ibm66n09.xml, ibm66n11.xml from "IBM XML Conformance Test Suite - Production 66" (see https://github.com/belingueres/xml-conformance/blob/main/src/test/resources/xmlconf/ibm/ibm_oasis_not-wf.xml) regarding the parsing of invalid character references.
The text was updated successfully, but these errors were encountered:
Fix MXParser fails to recognize illegal character references (codehau…
0386992
…s-plexus#132)
b5a006b
Most probably causes #238
Sorry, something went wrong.
No branches or pull requests
Discovered with the help of https://github.com/belingueres/xml-conformance
MXParser fails on parts of the W3C XML Conformance Test Suite.
In this issue, it is failing ibm66n01.xml, ibm66n03.xml, ibm66n05.xml, ibm66n07.xml, ibm66n09.xml, ibm66n11.xml from "IBM XML Conformance Test Suite - Production 66" (see https://github.com/belingueres/xml-conformance/blob/main/src/test/resources/xmlconf/ibm/ibm_oasis_not-wf.xml) regarding the parsing of invalid character references.
The text was updated successfully, but these errors were encountered: