You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Older fonts don't work with Catalina: Why/ Is it possible to fix them?

I have a fairly large number of both Type 1 PostScript and older TrueType and OpenType fonts that worked just fine until Catalina.


These fonts display properly in both FontBook and FontAgent 9 (current version).


Now Pages in particular has problems, including:

  • Font name won't display in the WYSIWYG font list, but the font WILL render in the text and in the font selector.
  • Font name doesn't display AND won't render.


It doesn't matter where they are installed (in system with FontBook or managed with FontAgent). I read in another thread that Type 1 Fonts just don't work anymore. But I am wonder about the other TrueType and Open Type fonts.


What is it about these fonts that's unacceptable to Catalina? Is there a way to clean them up or fix them?

iMac 27", macOS 10.15

Posted on Jan 22, 2020 10:52 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 23, 2020 5:46 AM

I have a bunch of Type 1 fonts that I have kept since the Illustrator v3 days. These work on Mojave in Pages v8.2.1, and when I copied them over to Catalina 10.15.2 — they no longer appeared in Pages. I had copied them through iCloud Drive.


Then, I zipped the folder these fonts were in on Mojave, and copied that zipped folder through iCloud Drive to my Catalina machine. I unzipped the folder, and drag/dropped it into my local Library/Fonts folder. Then, Pages was able to see these undamaged Type 1 fonts; display them on its font menu, and use all sixteen faces of ITC Garamond (by example). The ITC Garamond entry on the font menu is styled in ITC Garamond Light, an worded, ITC Garamond.


As an aside, I also copied the EB Garamond and Cormorant Garamond OpenType Postscript fonts from within MacTeX 2019 into the above fonts folder and these are also now usable by Pages v8.2.1.

Similar questions

3 replies
Question marked as Top-ranking reply

Jan 23, 2020 5:46 AM in response to Steve Allison-Bunnell

I have a bunch of Type 1 fonts that I have kept since the Illustrator v3 days. These work on Mojave in Pages v8.2.1, and when I copied them over to Catalina 10.15.2 — they no longer appeared in Pages. I had copied them through iCloud Drive.


Then, I zipped the folder these fonts were in on Mojave, and copied that zipped folder through iCloud Drive to my Catalina machine. I unzipped the folder, and drag/dropped it into my local Library/Fonts folder. Then, Pages was able to see these undamaged Type 1 fonts; display them on its font menu, and use all sixteen faces of ITC Garamond (by example). The ITC Garamond entry on the font menu is styled in ITC Garamond Light, an worded, ITC Garamond.


As an aside, I also copied the EB Garamond and Cormorant Garamond OpenType Postscript fonts from within MacTeX 2019 into the above fonts folder and these are also now usable by Pages v8.2.1.

Jan 23, 2020 3:56 PM in response to VikingOSX

Thank you for your answer.


I discovered that the problem for me was FontAgent v9. These are actually old TrueType Font Suitcase files ("FFIL") without file extensions. FontBook can import and render them fine. But something about FontAgent won't let them work with other apps, even though FontAgent can import, display, and activate them.

Older fonts don't work with Catalina: Why/ Is it possible to fix them?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.