Created attachment 145481 [details] Sample DOCX Looking at Bug 87379 there is a possible regression with Microsoft Equation 3.0 while opening attached sample DOCX. Some "Omega rSup" signs were correct in LO 4.4.7 and wrong from 5.0 up to 6.2+ as shown in attachment 132807 [details].
Created attachment 145574 [details] comparison MSO 2010 and LibreOffice 6.2
Regression introduced by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=791d8b4f1f656a8553c25fe9034ca8a350efaaae author Miklos Vajna <vmiklos@collabora.co.uk> 2015-04-15 15:41:11 +0200 committer Miklos Vajna <vmiklos@collabora.co.uk> 2015-04-15 17:16:56 +0200 commit 791d8b4f1f656a8553c25fe9034ca8a350efaaae (patch) tree b4931b8dfc2258e2ce1f30117e3f81b4f565be07 parent bf33f22ff29b6e4f6ea204e7d438cf28a1079392 (diff) DOCX import: convert MathType to Math if MathTypeToMath is enabled With this, math equations created by Word <= 2003 and embedded to docx files can be edited finally. Previously the result was read-only and opened in an unexpected new window. Bisected with: bibisect-50max Adding Cc: to Miklos Vajna
Sorry, I think this is rather an implementation error than a regression. The MathType <-> Math filter always had this problem, and it was a real bug that this conversion did not happen when the conversion was enabled in the UI. You can work this around by going to tools -> options -> load/save -> microsoft office -> and untick the load column for math. (But sure, it's a bug, it would be nice to fix it.)
Dear Timur, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No change in 7.2+.
Dear Timur, 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