Bug 135999 - Formula resolution is too low
Summary: Formula resolution is too low
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, bisected, regression
: 142970 (view as bug list)
Depends on:
Reported: 2020-08-21 20:48 UTC by Army_bloodcore
Modified: 2023-08-01 03:16 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Low resolution of a formula object (16.91 KB, image/png)
2020-08-21 20:49 UTC, Army_bloodcore
Test document, see end of page 4 and beginning of a page 5 to broken formulas. (74.50 KB, application/msword)
2020-08-21 20:52 UTC, Army_bloodcore
Test DOC 1 page (69.00 KB, application/msword)
2020-11-13 10:19 UTC, Timur

Note You need to log in before you can comment on or make changes to this bug.
Description Army_bloodcore 2020-08-21 20:48:40 UTC
When I am open a *.doc format, formula definition is too low, I can't see the small symbols, indexes and overbars/underbars.

Steps to Reproduce:
1. Turn off in settings export to the MathType MS office format.
2. Create a new document or import any document with formulas.
3. Create any formula in this document.
4. Save this document in *.doc format.
5*. If you will export/print this document in *.pdf format, this bugs will be save.

Actual Results:
Formula definition is too low, I can't see nothing, I see just a pixels on the screen.

Expected Results:
Formula definition is normal, like in

Reproducible: Always

User Profile Reset: No

Additional Info:
I've been turned off formula load/saving from MS office.
And I cannot find how to enable OpenGL in settings.
Version: (x86)
Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e
Потоков ЦП: 4; ОС: Windows 10.0 Build 16299; Отрисовка ИП: по умолчанию; VCL: win
Locale: ru-RU (ru_RU); ИП: ru-RU
Calc: threaded
Comment 1 Army_bloodcore 2020-08-21 20:49:27 UTC
Created attachment 164542 [details]
Low resolution of a formula object
Comment 2 Army_bloodcore 2020-08-21 20:52:15 UTC
Created attachment 164543 [details]
Test document, see end of page 4 and beginning of a page 5 to broken formulas.
Comment 3 Telesto 2020-08-22 18:24:33 UTC
Confirm.. its solved by entering the frame containing the formula. This is a known problem IIRC

Version: (x64)
Build ID: 8700bace8c0714d853f5df6918ab9c8bb3d81f77
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 4 Telesto 2020-08-22 18:34:34 UTC
There is an issue with DOC export. So saving a formula to doc will produce low res formula's (until clicking side the formula). Another work around is saving to DOCX
Comment 5 Army_bloodcore 2020-08-24 17:00:04 UTC
Telesto, most of my documents and projects contains hundred of formulas, and find everyone and click on it is a big problem. When printing, it is also make a big problems.

So, I know about export in *.docx format, it is strictly NOT RECOMMENDED TO DO THIS, NEVER EXPORT YOUR FILES IN DOCX FORMAT, it is avsolutely useless.
And I know about this bug:

DOC format is balanced and universal format standart. I mark stable version is, in this version is all right with formulas.
Comment 6 Army_bloodcore 2020-11-03 04:02:24 UTC Comment hidden (obsolete)
Comment 7 Timur 2020-11-13 10:19:10 UTC
Created attachment 167265 [details]
Test DOC 1 page

This bug wasn't reported and triages well. 
Not clear if DOC attached is MSO or LO saved, which is most important. I assumed it's MSO saved and resaved as 1 pages DOC (wrong to attach original document with many irrelevant pages). 
Than it's not clear if this is Fileopen or Filesave bug. While steps refer to Filesave, simple Fileopen shows worse visibility. 
Important that it was OK in 6.2, so likely a regression in 6.3. 
Not easy to find, because not much different.

Assuming this is fileopen for DOC attached: 

commit 12f72c57cddfa822e6113b345fa20ab64c1914bf
Date:   Fri Oct 25 09:53:38 2019 +0200
    source 1560adf9cfd1d4ef076561b1c48e80c9936c940d
    previous source e63d60c90d465ea6d9177bb82c25a35185a05a6e

author	Xisco Fauli <xiscofauli@libreoffice.org>	2019-10-21 17:41:52 +0200
committer	Miklos Vajna <vmiklos@collabora.com>	2019-10-25 09:38:08 +0200
commit 1560adf9cfd1d4ef076561b1c48e80c9936c940d (patch)
tree 3a557d7e7e65fdc3133b891aa1339a0018f61914
parent e63d60c90d465ea6d9177bb82c25a35185a05a6e (diff)
tdf#115967: Revert "sw: Use primitive renderer for graphics"
This reverts commit 302af8c2da58719844d22483b65a9fe5b3674684

Note: As for DOCX saved in MSO from DOC, it's worse in LO.
Comment 8 Timur 2020-11-13 10:19:59 UTC Comment hidden (obsolete)
Comment 9 Army_bloodcore 2020-11-17 08:53:21 UTC Comment hidden (obsolete)
Comment 10 Army_bloodcore 2020-12-02 16:30:58 UTC Comment hidden (obsolete)
Comment 11 Timur 2021-06-10 10:21:12 UTC
(In reply to Timur from comment #8)
> Xisco, which is a base bug now for a duplicate, is it bug 129244?

Please see this.
Comment 12 BogdanB 2021-07-31 05:38:18 UTC
*** Bug 142970 has been marked as a duplicate of this bug. ***
Comment 13 QA Administrators 2023-08-01 03:16:32 UTC
Dear Army_bloodcore,

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