Line spacing has changed for some typefaces, certainly Palatino and I think Times, Adobe Caslon. Others seem unaffected. Seems lines have tightened up and reduced line space. Saving the file as doc and opening with Word shows the original line spacing (more open). This is observed for screen display.
Hello Adrian, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 131451 [details] Odt document section. This is a cutdown section of one of the mis-displaying files - it has text in Paltino displaying incorrectly and in Courier (which seems to be fine).
This is a phenomenon affecting some typefaces but not others (Palatino, Times, Garamond at least show it). It also affects some but not all of the files in a folder where I have accumulated files over several years - they are odt files saved in earlier versions of Libre I think (and maybe some in Open Office earlier?) If I copy/paste the contents from these to a blank new odt in 5.3 they display correctly. If I open the odt in Word, it tells me there is a problem with unreadable content, and then in a secod box asks if I wish it to find missing content. Then it opens and displays correctly in Word. Saving from Word to odt creates a file which opens and displays properly in Libre. The misdisplaying type sections also print wrongly on an inkjet and "print" incorrectly to pdf with Distiller.
Created attachment 131455 [details] pdf printed version
It is weird, that they work when pasted to a blank document. I first suspected this would be related to the move to HarfBuzz, but that pasting solution makes me wonder. Unfortunately, as this is about proprietary fonts shipped with some Adobe apps, the pool of developers available to fix this is greatly limited. Not to mention QA members to first test this.. I don't have any Adobe products, so cannot confirm.
I'm wondering if it was fixed by 0c8b749e602b6743857a9bc4efb24b6183690311... Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
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-20180502
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-20180530