Testcase: Attachment 81816 [details] from Bug 66463. Screenshot shownig incorrect rasulting formula: Attachment 80819. Please note the third image showing incorrect curly brace and red question marks. The internal structure of the imported formula is this: size 12 { alignl { stack { left lbrace {{c}} sup {'} rSub {size 8{1}} left (x right )+ {{c}} sup {'} rSub {size 8{2}} left (x right ) cdot e rSup {size 8{- x}} =0 {} # right none left lbrace - {{c}} sup {'} rSub {size 8{2}} left (x right )e rSup {size 8{- x}} = {{1} over {e rSup {size 8{x}} +1} } {} # right no } } lbrace } {} Note: * lbraces positioned incorrectly (inside stack; in each line of the stack; second "left lbrace" is matched by bad-syntax "right no"; extra lbrace in the end without match); * extra "#" in the end of the second stack line. Here is the corrected formula: size 12 { left lbrace alignl { stack { {{c}} sup {'} rSub {size 8{1}} left (x right )+ {{c}} sup {'} rSub {size 8{2}} left (x right ) cdot e rSup {size 8{- x}} =0 {} # - {{c}} sup {'} rSub {size 8{2}} left (x right )e rSup {size 8{- x}} = {alignc {1} over {e rSup {size 8{x}} +1} } {} } } right none } {} Note that I intentionally left unnecesary elements (like empty and redundant braces) to keep resemblance. I had to add alignc to the division in the lower line to restore its correct representation. I suppose that the possible cause of the problem is that there is only one brace in the formula. A somewhat related is Bug 62178, that discusses the opposite direction problem. Affected both LO 3.6.3.2 and AOO, so must be an inherited problem. Still present in 4.0.3 and 4.1.0.1.
Excuse me, the screenshot is Attachment 81819 [details].
Hi Mike, Thank you for this quite clear report. I already met those problems with imported documents with formulas. I reproduce with LO 4.2.0.0.alpha0+ Build ID: ce0383d2950d3b0da2c457c8a406c1229de53571 & Windows 7 Home Premium I set status to NEW and Importance to MEDIUM HIGH. Regards, Jacques
Created attachment 83929 [details] More formulas to test These formulas are also displayed incorrectly for me. I think this .doc can also be a testcase for bug https://bugs.freedesktop.org/show_bug.cgi?id=66463
Created attachment 95109 [details] Formulas to test
Still reproduced with LO 4.4.0.0.alpha0+ Build ID: 488f31200094d7237d45545ab227014831a1f8e6 TinderBox: Win-x86@39, Branch:master, Time: 2014-06-15_05:02:39 & Windows 7 Home Premium Jacques
This is TWO issues in one, actually. One is sizing on msword mathtype objects import (#45284), another is incorrect processing of bracing brace (no pun intended). Actually, there is the THIRD issue involved -- the automatic re-rendering of all formulas images should be done after importing.
(In reply to Yury from comment #6) > This is TWO issues in one, actually No, actually here is only ONE issue reported, and its fix awaited: incorrect structure of imported formula (possibly caused by unmatched brace). Other problems that you have mentioned are irrelevant for this specific bug report, though affect the formula. Please don't add irrelevant comments, that may distract developer or make the issue hard to manage. I saw your issue when submitted this one, that's why I haven't create a dupe. As to "automatic re-rendering of all formulas images should be done after importing", it's questionable. In bug 66463, there's a case when the opposite is preferrable.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still reproducible with Version: 5.2.2.1 (x64) Build ID: 3c2231d4aa4c68281f28ad35a100c092cff84f5d
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
still repro in Version: 6.3.0.0.alpha0+ Build ID: 2b9739b9b009de93efa4f24995469c3bb9d82261 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-12-18_23:09:56 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Created attachment 158577 [details] doc saved in MSO 2016 as docx doc saved in MSO 2016 as docx load docx more errors in formulas in LO 6.4.1.2 x64 win10-64
Created attachment 158578 [details] doc saved as odt in LO 6.4.1.2 doc saved as odt in LO 6.4.1.2 formulas not ok in design in relation to mso 2016
Created attachment 158579 [details] docx saved as odt in LO 6.4.1.2 docx saved as odt in LO 6.4.1.2 more errors in formula
same in LO7.0.0beta2x64 on win10 x64
Looks like bug 62178 in the mirror direction. But the import of Docx is also buggy. So there a more than one bug or limitation in this example. There are improvements in 7.2.0 in ms office importers. Perhaps there is here progress.
no positive change for this problem in Version: 7.2.0.2 (x64) / LibreOffice Community Build ID: 614be4f5c67816389257027dc5e56c801a547089 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL
No formula improvement for doc and DOCX in 7.3.4.2. Version: 7.3.4.2 (x64) / LibreOffice Community Build ID: 728fec16bd5f605073805c3c9e7c4212a0120dc5 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL
Dear Mike Kaganski, 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