Adobe Postscript Type 1 Font not displaying in LibreOffice Mac


I have Adobe Postscript Type 1 Fonts that do not display in LibreOffice Mac:

  • They do not appear in the pull-down font menu on the toolbar, or in the scrolling pane in the Format/Character/Font dialog box.

  • Characters in the fonts, in imported .doc documents created in MS Word, display as another font I don’t recognize. Looks a bit like old English or Old German italic script.

I have checked that the problem is not a Mac OS X snafu: the fonts perform fine in other applications.

Any ideas? Does LibreOffice require the fonts to be installed somewhere other than in root/Library/Fonts ?

Thanks all.

Why to file a new bug, when one already exists?

And yes, it is reproducible in LibO 4.0.0 under Mac OS 10.8.

@Pekka L.J. Jalkanen, Thanks for the update!

Couple of notes:

  • The bug references “classic Mac PostScript Type 1 fonts format”. Do the particular fonts mentioned in the Question (“Adobe Postscript Type 1 Fonts”) and/or the fonts you’re using to test on 4.0.0 fall under that description?
  • The latest comments on that bug seem to indicate that the problem might be solved. Please add your own comment to the bug report with repro steps for osx 10.8.


I’m having the same problem with LibreOffice under Ubuntu 12.04.

Type 1 fonts display correctly in all other applications, including Thunderbird, Chrome and Midori.

Still experiencing this problem with LibreOffice under Xubuntu 13.10 and Bodhi 2.4.0
This appears to be identical to an existing bug fdo#37453
Note, this problem does not occur under Win7. Type 1 font installed there is visible and properly rendered under LO for Windows.

This thread is about Type 1 fonts not displaying under Mac, while your queries are about GNU/Linux. The bug for Mac platform (indicated above) is fdo#37453. This thread relates to the same problem for GNU/Linux (which you have already commented in).

Hi @quourteous,

Still experiencing this issue when using the latest release?

If so, please file a bug about this problem, and provide a list of steps that can reproduce it. The QA team will be happy to help you track down this issue!

Please post a link to any bugs you file in a comment below using the format “fdo#123456”.