Bug 107409 - FILESAVE DOC: Formula's seem to be (badly) rendered EMF+ images
Summary: FILESAVE DOC: Formula's seem to be (badly) rendered EMF+ images
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium minor
Assignee: Not Assigned
Keywords: bibisected, bisected, filter:doc, regression
Depends on:
Blocks: DOC-Formula
  Show dependency treegraph
Reported: 2017-04-25 07:46 UTC by Telesto
Modified: 2023-11-01 11:36 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Example file (27.48 KB, application/odt)
2017-04-25 07:46 UTC, Telesto
Comparison (41.48 KB, application/pdf)
2017-04-25 12:48 UTC, Telesto
Comparison2 (18.03 KB, application/pdf)
2017-05-05 09:22 UTC, Telesto

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2017-04-25 07:46:25 UTC
The formula's look quite ugly when saving to doc and reopening them in Word or LibreOffice. Opening the math editor (by double clicking the formula) will fix the rendering issue on Word as LibO. 

Re-saving the file after 'proper' rendering will be permanent in Word (also working for LibO), but not visa versa. 

Steps to Reproduce:
1. Open attached file
2. Save as a new .DOC file
3. Open then new file in Libreoffice

Actual Results:  
Ugly improper rendering of formula's 

Expected Results:
Should look the save as a file saved with Word

Reproducible: Always

User Profile Reset: No

Additional Info:
Found in
Build ID: 4354f0e9ef4a5538729a2a6f2d1745e247f6c5cd
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-04-21_06:05:57
Locale: nl-NL (nl_NL); Calc: CL

and in
Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d
Locale: nl_NL

User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Comment 1 Telesto 2017-04-25 07:46:50 UTC
Created attachment 132820 [details]
Example file
Comment 2 Bartosz 2017-04-25 11:10:02 UTC
Please attach example screenshot from LO and from Office.
Comment 3 Bartosz 2017-04-25 11:10:58 UTC
For me formulas are properly rendered. 
The only issue is with table cells, which are not properly divided
Comment 4 Telesto 2017-04-25 12:48:27 UTC
Created attachment 132829 [details]
Comment 5 Buovjaga 2017-04-29 06:49:24 UTC
Yep, they turn fuzzy after saving to .doc and reloading. Double click and exit fixes the issue.

Interestingly no problem in 3.6.

Arch Linux 64-bit, KDE Plasma 5
Build ID: 9348b322a5c230dfcc2231661b73e480b130fcd9
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on April 28th 2016

Arch Linux 64-bit
Version (Build ID: e183d5b)
Comment 6 Bartosz 2017-05-04 23:53:23 UTC
Please check if setting the Environment variable EMF_PLUS_DISALE to 1, resolve that issue.
Comment 7 Bartosz 2017-05-04 23:54:15 UTC
Just enter in terminal
and run LibreOffice from that terminal
Comment 8 Buovjaga 2017-05-05 04:47:53 UTC
(In reply to Bartosz from comment #7)
> Just enter in terminal
> export EMF_PLUS_DISABLE=1 
> and run LibreOffice from that terminal

or even simply
EMF_PLUS_DISABLE=1 libreoffice

Yep, confirm it resolves the issue.
Comment 9 Telesto 2017-05-05 09:22:07 UTC
Created attachment 133086 [details]

I also can confirm that it looks a lot better with EMF_PLUS_DISABLE. 

However, I want to note that there is still noticeable difference between re-rendering a formula (by entering/exiting the formula editor) and EMF_PLUS_DISABLE. The formula symbols are smaller and bit super-scripted. The font rendering is also different (less spacing, especially the equals sign)
Comment 10 QA Administrators 2018-05-06 02:30:02 UTC Comment hidden (obsolete)
Comment 11 Buovjaga 2019-05-19 18:48:26 UTC
Bibisected on Linux with 50max to https://gerrit.libreoffice.org/plugins/gitiles/core/+/d53103dd83bf20ac63485e229069f145e35b3009%5E!/
fdo#74124 bilinear scaling with blending for some formats

Adding Cc: to Tomaž Vajngerl
Comment 12 QA Administrators 2023-07-18 03:15:18 UTC
Dear Telesto,

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