Resolve Typekit Conflicts with Installed fonts
BUG: Installed fonts conflict with typekit fonts
• Proxima nova family fonts installed (sans Medium)
• Typekit fonts installed creates conflict where only limited weights are available from the family list. Typekit overwrites installed fonts on list and matching installed/typekit names appear to disappear altogether.
For us -- many of our clients use Motion for FCPX to edit and Motion does not see typekit fonts at all, so hardcopies must be installed on all edit machines but then in doing so -- AE has conflict with generation of the available typeface list.
I described the incident in more detail to Victoria Nece on the Motion Design Slack and she recommended me to add a comment here to alert the appropriate teams.
This appears to have started with CC19 because we haven't experienced the issue prior to this release.
Jonathan Deshaies commented
I sent you an email at the address provided and shared some screen shots and the fonts that we are experiencing issues with.
Ivan Bettger commented
Hi Jonathan —
I am on the Adobe Fonts team. Victoria apprised me of this situation a bit more in detail and I'm happy to help troubleshoot this with you. I'll need some additional details, if you can provide them — may be best to take this to email (ivanbeATadobeDOTcom).
Some information up front worth sharing: Adobe Fonts activation should not overwrite existing font installs; rather, it asks the operating system to install the requested fonts, and the OS then determines whether they can be installed or whether there's a conflict. That said, it's not unprecedented for the OS to have two of the "same" fonts installed, and that can cause issues in how apps enumerate fonts, which could be happening here. It's difficult to say without additional information about the source font files and install status in the font manager(s).