Because Suitcase Fusion can help you manage all your fonts, not just the. Instead of logging in as the root user, as suggested by Summers, you can use an invisible file tool like Invisible Finder to seek out the fontTablesAnnex file. What does the end of support of PostScript Type 1 fonts mean for designers. So if you are having problems with fonts auto-activating through Suitcase, search out this file and put it in the Trash or another place where you can retrieve it later, restart, and check for auto-activation. I then opened the document I had been having problems with, and the fonts were auto-activating again I'm guessing that this file hadn't been purged and refreshed in a while, because the new file it created was much smaller less than 200KB." "I restarted, logged in as a normal user, and started up Suitcase and Illustrator as I normally would.
![font in suitcase fusion but not fontbook font in suitcase fusion but not fontbook](https://ww1.prweb.com/prfiles/2012/04/17/9414607/SF4-SS-MainUI-Mac.png)
Not knowing what exactly was kept inside, but pretty sure it would be rebuilt, I dragged it to the trash, but didn't delete it (just in case). "I logged out and back in as 'root.' In my search for various caches which might be the culprit, I ran across a file in the System/Library/Caches/ directory which was named ' fontTablesAnnex.' It's size was a suspicious 10.8MB. I finally decided to dive deeper into the system. Then I was told to Boot in Safe Mode and run Disk Repair (no issues) and finally told to REINSTALL the Operating System. I don't use Font Book (because it's garbage) but I did a Validate Fonts and Restore Standard Fonts which did not fix the issue. I moved on to deleting any instance of an AdobeFnt.lst file, and any user-level font-related cache or database file. First, SUPPORT asked me to go through the Font Book Checks. I got more desperate as nothing seemed to help. "I tried the normal tricks making sure the correct options were set in Suitcase and in the Auto-Activation plug-in for Illustrator, replacing my Illustrator preferences with backups I keep, deleting the Suitcase preferences and re-dropping my fonts into Suitcase. These fonts include Apple Chancery, Arial, Baskerville, Brush Script, Futura, Georgia, Gill Sans, Impact, Papyrus, Times New Roman, Trebuchet, Verdana, Webdings, Wingdings (1, 2 and 3) and Zapfino.MacFixIt reader Steve Summers found a culprit cache file that was causing fonts to not auto-activate through Extensis' Suitcase: In Catalina, all the fonts not required by the system-but that Apple wants to make always available to apps-are placed into a Supplemental folder, located in System/Library/Fonts.
#Font in suitcase fusion but not fontbook mac
To add to the fun, FontExplorer showed the former locations of those font files-where the font files lived before Catalina moved them. If youre new to Typeface and you still have a different font manager installed on your Mac that manager might be.
![font in suitcase fusion but not fontbook font in suitcase fusion but not fontbook](https://igetintopc.com/wp-content/uploads/2017/06/Extensis-Suitcase-Fusion-7-Direct-Link-DOwnload_1.jpg)
![font in suitcase fusion but not fontbook font in suitcase fusion but not fontbook](https://i.pinimg.com/originals/f6/47/9a/f6479aea04140b483a1f1d427b2f75c1.jpg)
![font in suitcase fusion but not fontbook font in suitcase fusion but not fontbook](https://mac-cdn.softpedia.com/screenshots/FontBook_9.png)
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.