Created attachment 190953 [details] ODF file containing a ∞ char MathML is meant to be valid XML. In certain conditions LibreOffice Math exports the infinity char (∞) as the Infinity html entity ∞ which is not valid XML rendering the prodiced MML file useless. Consider the attached formula.odf file. When LibreOffice exports it to MML : * line 9 of content.xml : <mi mathvariant="normal">∞</mi> * is exported as <mi mathvariant="normal">∞</mi> The produced file is not valid XML and will not load in a browser.
This is not a bug. MathML is not only a "valid XML"; it also references the MathML specification. Namely: MathML spec. chapter 7 section 7.3 "Entity Declarations" [1] tells: > The MathML DTD references the combined HTML MathML entity set defined in [Entities] The "combined HTML MathML entity set" [2] references, among others, "xhtml1-symbol" set. The latter is defined in "Entities" [3] as [4]. And there, the 'infin' entity is defined. It is incorrect to expect parsing of MathML without the respective DTD. [1] https://www.w3.org/TR/MathML3/chapter7.html#chars.entities [2] http://www.w3.org/2003/entities/2007/htmlmathml.ent [3] https://www.w3.org/TR/xml-entity-names/ [4] https://www.w3.org/TR/xml-entity-names/xhtml1-symbol.html
OTOH: > every fragment using entity references must use a DOCTYPE declaration which > specifies the MathML DTD, or a DTD that at least declares any entity reference > used in the MathML instance NEW.
Regression after https://gerrit.libreoffice.org/c/core/+/108354.
Why then does the internal MathML in content.xml not use them ? Why produce an MML file that no browser can parse ? The produced MML cannot be displayed by mozilla or chromium browsers. This problem is not present on LibreOffice 6.4.7.2
Dear sam.monsarrat, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug