Closed Bug 1338401 Opened 8 years ago Closed 8 years ago

XML Parsing Error: undefined entity

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
51 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 22942

People

(Reporter: erchbox, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20170125094131 Steps to reproduce: Simply point Firefox to http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.xml Actual results: XML Parsing Error: undefined entity Location: http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.xml Line Number 25461, Column 12: (2008&ndash;2012).</para> -----------^ Expected results: Firefox supports the HTML entity &ndash; and properly displays the following code: <!DOCTYPE html> <html> <style> body { font-size: 20px; } </style> <body> <p>I will display &ndash;</p> </body> </html> But its XML parser does not recognize it
XML has rather fewer entities than HTML. See https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references#Predefined_entities_in_XML for more details.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
I would suggest that you check the following URLs: https://www.w3.org/TR/xml-entity-names/xhtml1-special.html https://www.w3.org/2003/entities/2007/xhtml1-specialmap.xsl This is about Firefox not fully supporting standard XLST. FYI Google Chrome & Opera do handle properly the page: http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.xml Would you please re-open the case? Thanks
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
(In reply to Eduardo Reyes from comment #2) > I would suggest that you check the following URLs: > > https://www.w3.org/TR/xml-entity-names/xhtml1-special.html > > https://www.w3.org/2003/entities/2007/xhtml1-specialmap.xsl those are about XHTML, and http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.xml is not XHTML.
In the Abstract of the document at https://www.w3.org/TR/xml-entity-names you can read: This document defines several sets of names, so that to each name is assigned a Unicode character or sequence of characters. Each of these sets is expressed as a file of XML entity declarations. To my understanding, W3C inherited "Legacy Entity Sets" from previous specs and made them part of the XML spec. Of course, I could be deadly wrong in my appreciation.
From the very Wikipedia page (https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references#Predefined_entities_in_XML) I was suggested to read: XML Entity Sets: The W3C MathML Working Group took over maintenance of the ISO public entity sets, combined with the MathML and documents them in XML Entity Definitions for Characters. This set can support the requirements of XHTML, MathML and as an input to future versions of HTML.
you need to use htmlmathml or htmlmathml-f like this https://www.w3.org/TR/xml-entity-names/#setsdiv
I refuse to go on with this. Have you realized that someone is taking part of his precious time to try to help your company to improve its flagship product Firefox? Instead of trying to prove that you are right, you should give yourself the benefit of the doubt and READ: XML Entity Sets: The W3C MathML Working Group took over maintenance of the ISO public entity sets, combined with the MathML and documents them in XML Entity Definitions for Characters. This means: XML Entity Definitions = MathML + Legacy Entity Sets If you still have doubts please contact W3C
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
The XML file at http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.xml points on line 10 to: http://docs.oasis-open.org/ubl/os-UBL-2.1/db/spec-0.6/docbook/docbookx.dtd That file points on line 120 to: http://docs.oasis-open.org/ubl/os-UBL-2.1/db/spec-0.6/docbook/dbcentx.mod That file points on line 158 to: http://docs.oasis-open.org/ubl/os-UBL-2.1/db/spec-0.6/docbook/ent/isopub.ent That file has the ndash entity defined on line 99. If the XML processor in Mozilla properly identified the use of the DocBook DTD and processed all of its fragments, it would have found the &ndash; entity without complaint. Certainly the other browsers do so.
We can make this bug a duplicate of not loading external DTDs then.
Status: VERIFIED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: INVALID → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.