![]() To add to the fun, FontExplorer showed the former locations of those font files-where the font files lived before Catalina moved them. I noticed that hundreds of fonts in FontExplorer were marked as Conflicts, colored red in its list of fonts. I don’t expect the Catalina font chaos to return, since FontExplorer won’t try to activate any font already activated by the System. What about the now-inactive fonts I need for my projects? No problem: with FontExplorer’s auto-activation feature enabled, any new fonts needed when I open documents or apps are automatically activated. Apparently, there is a conflict between some of the Mac’s core fonts and some fonts that I long ago had activated in FontExplorer. ![]() ![]() After confirming that I had cleared the font caches and checked permissions on Fonts folders, I disabled all the fonts in my font manager, which, in my case, is, FontExplorer X Pro. Finally, I contacted the font experts at Monotype. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |