Created attachment 120105 [details] There are the original odt file, the exported pdf, and images of the glitches Rendering of formulae in Writer is poor (see images in attachment). The middot is too close (1). The upper limit of sums and integrals stands off too much (2). The root is not properly connected (3). The integral sign is not using the correct font (4) which is Times New Roman for all items. The attachment contains the odt file as well as the pdf file created thereof. In the pdf, there is only a minor glitch with the root sign. Everything else looks as expected. It is very difficult to create a professional looking output. My current workaround is like this: a) save as pdf b) open in Inkscape and save as svg or emf, respectively. This is very clumsy!
Not reproduced, everything looks fine. Please try with LibreOffice 5. Win 7 Pro 64-bit, Version: 5.0.3.2 (x64) Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75 Locale: fi-FI (fi_FI) Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
After installing LO 4.4.7, I tried out this document. However, the document looks still the same. All glitches are still there. I am running Windows 10 in a Parallels VM under OS X, if this information helps.
(In reply to rbruenner from comment #2) > After installing LO 4.4.7, I tried out this document. However, the document > looks still the same. All glitches are still there. > I am running Windows 10 in a Parallels VM under OS X, if this information > helps. Ok, now you can try with version 5.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Sun, 11 Sep 2016 21:43:24 +0200
Just installed LO 5.1.5 (32 bit) on Windows 10 Enterprise 64 Bit. Unfortunately, the odt document still renders this way. No improvement. When opening the very same file on LO 5.1 running on Mac OS 10.10.5, output looks the same as the attached pdf. Best regards
It still looks ok to me. I even tried with the exact same zoom 340% as in your first screenshot. Are you still running Windows in a VM? Have you tried on a non-VM Windows? It might be, that this is different in Windows 7 and 10 :( Win 7 Pro 64-bit, Version: 5.2.0.4 (x64) Build ID: 066b007f5ebcc236395c7d282ba488bca6720265 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: fi-FI (fi_FI)
I have tested with two Windows systems running natively. First, Windows 10 Professional 64 Bit with LO 5.0.6: 1. The middot problem is not visible 2. The upper limits of the sums and integrals look acceptable 3. The root looks better 4. The integral sign uses a wrong font as before 5. Now, the sum sign also uses a wrong font. Another colleague running Windows 7 and (ancient) LO 4.1.4 has no display issues with this file. Everything looks as expected on that machine.
Created attachment 127339 [details] Shows the state of the issue on a native Win 10 machine
Yet another two results: Windows 7 and LO 5.0.6 displays the file perfectly (the root sign is better than on the other computer with Windows 10). No display problems. Windows XP and LO 4.2.8 displays the file perfectly as well. So it seems there is a problem with Windows 10. The Parallels VM might make it worse but even native Windows 10 has issues. Best regards
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180302
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180404