Font Menu Corruption: Can't get rid of duplicate font styles listed in Affinity

[uneMule]

Bonjour à tous.
FontAgent de insider est un gestionnaire de polices qui fonctionne bien (pour avoir utiliser suitcase, et d'autres avant). Mac ou Windows. Mais est-ce la bonne réponse à votre problème.

*****

Hello everyone.
FontAgent from insider is a well working font manager (for having used suitcase, and others before). Mac or Windows. But is it the right answer to your problem.

[nwhit]

11 minutes ago, uneMule said:

Bonjour à tous.
FontAgent de insider est un gestionnaire de polices qui fonctionne bien (pour avoir utiliser suitcase, et d'autres avant). Mac ou Windows. Mais est-ce la bonne réponse à votre problème.

*****

Hello everyone.
FontAgent from insider is a well working font manager (for having used suitcase, and others before). Mac or Windows. But is it the right answer to your problem.

Sadly, no, a font manager does not solve the problem in newer versions of macOS such as Big Sur. Catalina and especially Big Sur and Monterey automatically add a few hundred fonts, all of which cannot be turned off (unless you use TypeFace font manager to turn off a few). Thus the font menu has many, many fonts showing that are hardly ever used.

TypeFace font manager is one of the only ones that can actually disable the "Supplemental" set of fonts Big Sur installs, which is helpful, but it does not turn off the many, many others that show up in the Affinity All Fonts menu. The only real solution (prior to Affinity v1.9) had been using Apple's Font Book's customized collections so that in all apps you could go to/view a smaller subset of displayed fonts. Worked great until recently, so hopefully Affinity can sort it out and get it working again. 

[GaryLearnTech]

I was in what seemed to be a similar position earlier this week.  I had issues with Montserrat - it would appear perfectly on screen, but exported PDF's displayed what looked like a Cyrillic style version of Montserrat.  I had several older versions installed (they came with Final Cut Pro plugins from FXFactory) as well as my personally installed latest version.  All apparently managed properly in Font Book, with just my preferred version active - the others showing as inactive.  In the end, I cleared them all and reinstalled just a single recent version, but that led to duplicate entries in the font menu.  Yikes!

Then I remembered an old, old Word troubleshooting tip - Save As to produce a brand new document from scratch.  Evolving documents contained hidden 'baggage' and this would clear that baggage, producing a clean version of the document and would often resolve problems.  (If nothing else, it could make documents considerably smaller!)

I tried the same thing with the Publisher document I had been working on and, hey presto, the duplicate Montserrat entries had vanished - and my exported PDF's now displayed as expected.  My reckoning is that each Publisher document contains some sort of unique reference to every font - not quite a cache maybe, but something similar.  Those references somehow got out of whack as I was trying to straighten out my Montserrat versions and was only finally cleared when I did a Save As.

[nwhit]

I can see that problem happening. Of course, the issue in this thread isn't the same since the font menu corruption occurs on each and every new, blank document in all 3 apps. No carryover. For some reason, Affinity cannot use the Font Book collections without subsequently corrupting the All Fonts menu.

And as per the various posts and pics, it's not just with a single font. The duplicate font styles happen to numerous fonts. As said before, the All Fonts menu is correct initially (in a blank, new document in any of the 3 apps), but if you then select one of the custom collections you've created in Font Book, there are then numerous duplicate styles showing for many fonts in the various collections. Following that, the main All Fonts menu now shows an increased number of duplicate styles for many fonts. That makes it pretty tough to pick a font and style, not knowing if it's "real" or not! 

Note: This issue is new as of v1.9.x since I used to use these same Font Book collections constantly in previous versions without any issues. Never had a problem previously.

[nwhit]

@Jon P Any update on this serious issue for possible fix in 1.10.2? Thanks.

[Jon P]

Unfortunately not, but I've given the issue linked to this thread a bump.

[nwhit]

Thanks.