Description: I create a WP 3.5e for Mac document (within Mac OS 8.6 with the original application) with three lines in Verdana, Times New Roman and Arial respectively. When imported into LibreOffice 6.2.2.2 for Mac, the three lines appear but the first two lines are in Times New Roman. Steps to Reproduce: 1. Create a WP 3.5e for Mac document (within Mac OS 8.6 with the original application) with three lines in Verdana, Times New Roman and Arial respectively. 2. Import into LibreOffice 6.2.2.2 for Mac. 2. ???? 3. PROFIT! Actual Results: Document appears with the line in Verdana appearing in Times New Roman instead. Expected Results: The three lines should appear in Verdana, Times New Roman and Arial. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 150867 [details] Test file Test file
@Hal : I had to add a WPD extension to the file in order for it to be loaded by LO. Indeed, the first line is shown in the UI as Times New Roman, instead of Verdana, and the 2nd line is also TNR (although displayed differently). The third line is indicated as Arial. I'm guessing that there is some kind of font substitution going on here; but given that the fonts in use in macOS8 were probably not OTF, and given that even macOS has undergone font management changes since then, it isn't going to be surprising that current LO attempts to substitute the fonts with something else when it loads the file, unless this document was displayed correctly in an earlier version of LO, which would be a regression. Confirming - yet another font display bug on macOS.
Tested against Version: 6.3.0.0.alpha0+ Build ID: c74ec989eabdf7ffb5ea4d6f43757116261eaeed CPU threads: 4; OS: Mac OS X 10.14.4; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded
Reproduced in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 so problem isn't new.
Same substitution happens on Windows TNR, TNR, and Arial Version: 6.4.0.3 (x64) Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8 CPU threads: 2; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Dear hal.sulphur, 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 MassPing-UntouchedBug
Based on Comment 2 and Comment 4, it appears this may be expected behavior. I'll set to Resolved NotABug, change it back if you don't agree.