-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LibreOffice doesn’t recognize font name in OTF file #252
Comments
|
Thanks for this observation! BTW – if the PDF file works and fonts are embedded correctly, the font name embedded within the PDF does not really matter in terms of functionality. |
|
Same results when tested on LibreOffice v7.0.3.1 (x64) on Windows 10. So I selected some other OTF-PS fonts to test the export to PDF. So something is in these particular fonts that causes the LO PDF library an issue. |
This is the relevant bit of information. Based on this, I conclude that LibreOffice uses Macintosh font menu names for embedding OTF files to PDF. See here the difference between an old-school OTF (Tekton Pro) and a current OTF (Minion 3): You’ll see that all the entries are duplicated in Tekton, once as Mac variant ( You’ll also see that in the name table dump of Minion 3 how MacRoman encoding might represent a problem in keeping all entries in sync. As far as I know, macOS itself does not rely on the Mac-specific name table entries. It would be good to bring up this issue with LibreOffice – they seem to know how to reference the Windows menu names, judging by the properly-embedded TTF fonts. |
|
I don't understand. I have tested over 150+ fonts families in LibreOffice for Windows to find out what works, and what does not work, and why. So that is why this issue has me intrigued. Searched for "DummyName" with various other font and PDF related terms - found nothing. Hmmm ... just did Export to PDF from Affinity Publisher to test. Ugh, I really do not want to get back into the LO bug tracker pit of despair. @yrogge |
|
I have a feeling that LO may use one route for embedding TTFs, another for OTFs. |
|
For reference, OP opened an issue for LibreOffice: https://bugs.documentfoundation.org/show_bug.cgi?id=138325 |
|
Thanks for submitting the bug upstream! |
|
This issue is now fixed in LibreOffice. (LibreOffice was trying to get the font name from the CFF table but couldn’t find either FontName or FullName. It now reads the name from name table unconditionally). |
|
Thank you! This reminds me of |
I’m using LibreOffice 7.0.3 with SourceCodePro v.2.030 (v.1.050 for italics) on Linux system (Ubuntu 20.10).
When OTF fonts are installed, everything is perfect (LaTeX and other documents producing software), but LibreOffice export tool to PDF.
When I look to fonts used in PDF file, all SourceCodePro fonts are indicated as “DummyName” font.
If I install the TTF version of the same fonts, LibreOffice does export the font name correctly.
Strange, isn’t it?
I’m using static version, because variable fonts cannot be used when creating PDF documents.
The text was updated successfully, but these errors were encountered: