Created attachment 81672 [details] Screenshot of LibreOffice bug side-by-side with NeoOffice's correct rendering of font Problem description: There is a font on the Mac called "Hoefler Text", an elegant serif font, Apple's version of Garamond. In the latest LibreOffice (4.0.4), and earlier, text formatted as Hoefler Text is rendered--incorrectly--as an ordinary-looking sans-serif font. If the same text is changed to bold or italic, the text is shown in the correct, elegant, bold or italic serif font, but if it is not formatted as bold or italic, the problem persists--the wrong font is rendered. I have not noticed any similar problem with any other Apple font. This problem also occurs in OpenOffice, but not in NeoOffice, and not in any other application on the Mac that I have tried. The font is rendered properly in such diverse apps as Thunderbird mail composer, Finale and MuseScore music-writing apps, and the native Mac apps TextEdit and FontBook. I have attached a screenshot of a LibreOffice window and a NeoOffice window, side-by-side, both with four lower-case and upper-case alphabets formatted as Hoefler Text, in regular, italic, bold, and bold italic. It is quite obvious from the screenshot that the upright (regular) text is rendered as the wrong font in LibreOffice. Also note in the example that in NeoOffice, when a word ends in "t" and is formatted as Hoefler Text italic (both bold and not bold), the final "t" has a fancy little trailing curlicue (sorry, I don't know the proper typographical name for it). LibreOffice does not do that, which I believe to be another bug in the rendering of this font. Steps to reproduce: 1. Format text as "Hoefler Text" regular, upright text, not italic or bold. Current behavior: Some unrelated sans-serif font is rendered. Expected behavior: The correct elegant serif font should be rendered. Operating System: Mac OS X Version: 4.0.0.3 release
On Macos 10.7.5 with LO 4.0.4.2, I reproduced the problem, put it at New
The swash t in NeoOffice is a bug there, this feature is not enabled in the font by default (we have no UI to activate optional font features, but that is another issue). The wrong font is a bug indeed, looks like when asked for plain “Hoefler Text” we load the Ornaments variant not the Regular one.
Also reproducible with the master build.
I tried to debug this a bit last week. The problem is that there is a “Hoefler Text Ornaments” fonts that has the family name “Hoefler Text” and of regular weight so we end up choosing it over the real “Hoefler Text” regular. I couldn’t find the exact place in the code where this happens, though.
Khaled: thank you for the explanation, I think Caolán may help here by providing a code pointer. Caolán: any idea?
It's been fixed in OO 4.0, which was just released. Maybe you can find the fix in their latest source.
A quick look does not show any commits that might have been fixed this issue. While debugging this issue, it would often just fix itself randomly in certain builds and reappear again after few rebuilds, so it might just be the case here.
Comment on attachment 81672 [details] Screenshot of LibreOffice bug side-by-side with NeoOffice's correct rendering of font Hello, same bug for me without explanation, as I have got the latest version and as the proper font is present indeed in the "Book of fonts" of Mac OS X. Jan. 29th, 2014
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
This works for me, normal hoefler texts renders fine with serifs Version: 5.2.3.3 Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf CPU Threads: 2; OS Version: Mac OS X 10.12; UI Render: default; Locale: en-US (en_NO.UTF-8); Calc: group