Hide Forgot
Created attachment 568059 [details] testcase Description of problem: See attached large XML file (complete Czech study translation of Bible in OSIS XML language). Version-Release number of selected component (if applicable): libxml2-2.7.6-4.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.run xmllint --noout --schema http://www.bibletechnologies.net/osisCore.2.1.1.xsd bible.xml 2. 3. Actual results: bible.xml:65535: element q: Schemas validity error : Element '{http://www.bibletechnologies.net/2003/OSIS/namespace}q': This element is not expected. Expected is one of ( {http://www.bibletechnologies.net/2003/OSIS/namespace}a, {http://www.bibletechnologies.net/2003/OSIS/namespace}abbr, {http://www.bibletechnologies.net/2003/OSIS/namespace}date, {http://www.bibletechnologies.net/2003/OSIS/namespace}divineName, {http://www.bibletechnologies.net/2003/OSIS/namespace}foreign, {http://www.bibletechnologies.net/2003/OSIS/namespace}hi, {http://www.bibletechnologies.net/2003/OSIS/namespace}index, {http://www.bibletechnologies.net/2003/OSIS/namespace}lb, {http://www.bibletechnologies.net/2003/OSIS/namespace}milestone, {http://www.bibletechnologies.net/2003/OSIS/namespace}milestoneEnd ). Expected results: correct line number ... there is no <q> element on line 65535 Additional info:
Sorry the internal tree model has room to keep lines only on a 16 bits integer and I can't change that without breaking the API. The validation error is right I would guess, except for the line number. Getting that line number would be hard, even in the streaming case xmllint --stream --schema http://www.bibletechnologies.net/osisCore.2.1.1.xsd bible.xml this was raised upstream and I dropped the request due to the ABI stability issue. I could try to be inventive and attempt a solution in the case of streaming, but that's not a simple problem. My first take is WONTFIX as this is the upstream status-quo, but if you can come with convincing arguments on reopen of the bug, I may try to spend some time on it :-) Daniel