In theory, only operators like those mentioned in http://www.w3.org/TR/MathML3/appendixc.html#oper-dict.entries-table should be exported as <mo> elements. Symbols like emptyset, aleph, setN that are more like variables should use <mi> elements instead.
NEW right away :). Kind regards, Joren
I've submitted a patch for review: https://gerrit.libreoffice.org/#/c/4595/
Marking these bugs assigned since I've already taken them.
Frederic Wang committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=43cf39adff66d20862956869d11fbcc184eb5702 fdo#66088 Export some math symbols as <mi> elements. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Reopening this bug as it seems that I overlooked the NSPECIAL and NGLYPH_SPECIAL cases. NGLYPHSPECIAL correspond to the commands uoper, boper, oper to define operators and so should still be exported as <mo> elements. NSPECIAL correspond to the %xxxx commands. Most of them are greek letters like %alpha so should be exported as <mi> elements. Other correspond to binary operators (without syntax verification) like %and so should be exported as <mo> elements. I think users can define their own %xxxx commands so a generic way to detect whether a character is an operator is needed (bug 66279)
Frederic Wang committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=9bb74686b1f857e791235381db632d1b5ac58296 fdo#66088 - follow-up: handle NGLYPHSPECIAL and NSPECIAL too. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
This is not completely fixed and depends on bug 66279. %xxx are now exported as <mi>'s rather than <mo>'s which is OK since most of them are Greek letters. But a few commands like %noelement should be <mo>. Users can also define their own commands with the Catalog menu. See comment 5.
OK, I overlooked that.
Setting Assignee back to default. Please assign it back to yourself if you're still working on this issue
Dear Dante, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assign it back to yourself if you're still working on this.
(In reply to Xisco Faulí from comment #10) > Dear Dante, > This bug has been in ASSIGNED status for more than 3 months without any > activity. Resetting it to NEW. > Please assign it back to yourself if you're still working on this. Solving mathml bugs require big structural changes. I'm still working on them. But don't spect anything before 7.3 I need to build the basements before the building.
Dear Frédéric Wang, 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