Bug 59181 - docx formulas with messed parentheses hierarchy don't show correctly in LibO
Summary: docx formulas with messed parentheses hierarchy don't show correctly in LibO
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Keywords: filter:docx
: 81840 82108 (view as bug list)
Depends on:
Blocks: DOCX-Formula
  Show dependency treegraph
Reported: 2013-01-09 21:38 UTC by Ruslan Kabatsayev
Modified: 2022-12-24 03:25 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Test file (15.09 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2013-01-09 21:38 UTC, Ruslan Kabatsayev
How it's look like in Word for Mac 2011 (=Microsoft office word) (98.14 KB, image/png)
2013-01-10 15:29 UTC, Jorendc
pdf created with Word for Mac 2011 (767.71 KB, application/pdf)
2013-01-10 15:30 UTC, Jorendc

Note You need to log in before you can comment on or make changes to this bug.
Description Ruslan Kabatsayev 2013-01-09 21:38:29 UTC
Created attachment 72754 [details]
Test file

See test file. It has "(E" being subscripted by "g", and thus the closing parenthesis doesn't match anything, which results in lots of red question marks in formula rendering.
I'm not sure how this should be fixed, perhaps when such messed formula appears as result of parsing, parser should escape/quote nonmatching parentheses or something.
Comment 1 Jorendc 2013-01-10 15:29:57 UTC
Created attachment 72783 [details]
How it's look like in Word for Mac 2011 (=Microsoft office word)
Comment 2 Jorendc 2013-01-10 15:30:23 UTC
Created attachment 72784 [details]
pdf created with Word for Mac 2011
Comment 3 Joel Madero 2013-01-10 15:31:36 UTC
I see this problem in as well so I'm changing version
@reporter - version represents oldest version that the bug is confirmed on. It looks different on vs. on 4.1 master but both show the red question marks which seem to be incorrect :)

Marking as:
New (confirmed)
Normal - can prevent high quality work for those inserting formulas in writer and using docx format
Medium - default priority for normal bugs, no need to change this for this bug

Thanks for reporting.
Comment 4 Jorendc 2014-04-26 17:01:37 UTC
Still reproducible using Windows 8.1 with LibreOffice Version:
Build ID: f4a6837025a293312cbc43b9c527851362f11030
TinderBox: Win-x86@47-TDF, Branch:MASTER, Time: 2014-04-26_09:21:18

Kind regards,
Comment 5 Matthew Francis 2015-01-18 06:48:09 UTC
*** Bug 81840 has been marked as a duplicate of this bug. ***
Comment 6 Matthew Francis 2015-01-18 06:54:18 UTC
This looks to be more of an import filter issue than a Writer issue. There is some confusion between straight and curly brackets.

Changing the first formula in attachment 72754 [details] from

  {E} rsub {g} = {{E} rsub {g}} rsub {GaN} + {{(E} rsub {g}} rsub {AlN} {{-E} rsub {g}} rsub {GaN} )x-cx(1-x)

  {E} rsub {g} = {{E} rsub {g}} rsub {GaN} + {{{E} rsub {g}} rsub {AlN} {{-E} rsub {g}} rsub {GaN} }x-cx(1-x)

(replacing some straight brackets with curly brackets) makes it render more like the sample image


Version -> (3.3 doesn't render the formulae at all, so not inherited from OOo or a regression as such)
Component -> filters and storage
Whiteboard -> filter:docx
Comment 7 Matthew Francis 2015-01-19 05:20:35 UTC
*** Bug 82108 has been marked as a duplicate of this bug. ***
Comment 8 Robinson Tryon (qubit) 2015-12-09 18:44:53 UTC Comment hidden (obsolete)
Comment 9 Telesto 2016-12-21 16:09:24 UTC
Still reproducible with:
Build ID: 9cfb2f2f03b5ec086487fd483298466db0b09010
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2016-12-20_23:58:02
Locale: nl-NL (nl_NL); Calc: CL
Comment 10 QA Administrators 2017-12-22 03:35:12 UTC Comment hidden (obsolete)
Comment 11 Ruslan Kabatsayev 2017-12-22 06:04:33 UTC
Still happens on LibO
Comment 12 QA Administrators 2018-12-23 03:49:07 UTC Comment hidden (obsolete)
Comment 13 Ruslan Kabatsayev 2018-12-23 07:59:45 UTC
Still present in
Comment 14 QA Administrators 2020-12-23 03:45:08 UTC Comment hidden (obsolete)
Comment 15 QA Administrators 2022-12-24 03:25:31 UTC
Dear Ruslan Kabatsayev,

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