Bug 76541 - FILEOPEN: Incorrect formula view when it contains 2 equal signs, DOC, DOCX
Summary: FILEOPEN: Incorrect formula view when it contains 2 equal signs, DOC, DOCX
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.5.0 release
Hardware: All All
: medium minor
Assignee: Not Assigned
Whiteboard: BSA
Keywords: filter:docx, implementationError
Depends on:
Blocks: DOCX-Formula
  Show dependency treegraph
Reported: 2014-03-24 08:03 UTC by Sergey Pashinin
Modified: 2024-03-17 03:14 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

test document (14.52 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-03-24 08:03 UTC, Sergey Pashinin
doc, 2 equal signs, new line (22.00 KB, application/msword)
2014-03-24 08:06 UTC, Sergey Pashinin
Test compared MSO LO (159.35 KB, image/png)
2020-03-16 10:42 UTC, Timur

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Pashinin 2014-03-24 08:03:55 UTC
Created attachment 96271 [details]
test document

Problem description: 
A formula may contain 2 equal signs in a row: "=="
Or in the end of 1 line and in the beginning of another "=\n="
This is incorrectly displayed if such (doc, docx) document is imported.

"==" is displayed in LO as "=¿"

Apparently because it expects something between 2 "=" signs.
But it is not correct when importing from .doc

If to make one symbol in qoutes - then they are slightly different in sizes.
I suggest to put "{}" between them.

Steps to reproduce:
1. Open a document
2. Maybe dbl click a formula

Current behavior:

Expected behavior:
Operating System: Ubuntu
Version: release
Comment 1 Sergey Pashinin 2014-03-24 08:06:42 UTC
Created attachment 96272 [details]
doc, 2 equal signs, new line
Comment 2 Thomas van der Meulen [retired] 2014-03-24 09:35:07 UTC
Thank you for your bug report, I can reproduce this bug running 
Build ID: 1a67b7cc3d5dc3dcd0de0e247f638c33d57dea1b
TinderBox: MacOSX-x86@49-TDF, Branch:master, Time: 2014-03-23_05:59:09
OS: Mac osx 10.9.2
Comment 3 Joel Madero 2015-05-02 15:42:58 UTC Comment hidden (obsolete)
Comment 4 Buovjaga 2015-06-21 10:30:46 UTC

Win 7 Pro 64-bit Version:
Build ID: 3ecef8cedb215e49237a11607197edc91639bfcd
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-06-19_23:16:58
Locale: fi-FI (fi_FI)
Comment 5 QA Administrators 2016-09-20 10:09:58 UTC Comment hidden (obsolete)
Comment 6 Xisco Faulí 2017-03-15 10:17:17 UTC
Still reproducible in

Build ID: d3b5bd4a07a619db6bee1c39c32280ac3c620532
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group


Version (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Comment 7 QA Administrators 2018-03-16 03:36:22 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2020-03-16 02:36:20 UTC Comment hidden (obsolete)
Comment 9 Timur 2020-03-16 10:42:01 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2022-03-17 03:36:02 UTC Comment hidden (obsolete)
Comment 11 Timur 2022-03-17 08:47:53 UTC
Repro 7.4+ as seen in screenshot attachment 158719 [details] from 7.0.
Comment 12 QA Administrators 2024-03-17 03:14:18 UTC
Dear Sergey Pashinin,

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