Typeface app
My feedback
1 result found
-
7 votes
As reported, the issue has been resolved with the Typeface 4.3.1 update. Hope the Typeface team comments on the nature of changes made.
An error occurred while saving the comment Typeface app
supported this idea
·
An error occurred while saving the comment Typeface app
commented
It appears that 30.3 only loads fonts that are 'available'. On macOS fonts can be provided on demand by other apps.
Previously when a document was opened all used fonts in that document were loaded by Illustrator. This allowed other apps to provide fonts that were not already available, in order to display them in the document. So missing fonts were provided and displayed correctly.
In 30.3 that doesn't happen: missing fonts are not 'loaded', therefore they cannot be provided by other apps. I suspect there is some new check such as 'if font is available then load font'.
This may also affect 'Document-support fonts'. These are macOS system fonts that do not appear 'available' for new documents (users cannot select them). However if an existing document tries to load such a font the system automatically provides it for that document. So existing documents will render the font correctly, because the missing font is loaded and automatically provided by the system.
If someone on the Adobe team wants more info please feel free to reach out.
Adobe Illustrator v30.3 and later doesn't support native macOS auto activation anymore, as it doesn't send any font requests. The Illustrator team reached out to ask for more information and potential solutions, but unfortunately they didn't reply to clarify whether this is now expected behaviour or whether reverting to previous behaviour is being considered.
Since that is still unclear, Typeface app now actively checks for missing fonts in order to auto activate them when opening documents.
Support for macOS Document-support fonts seems to remain unavailable due to the Illustrator changes. These fonts cannot be provided by font managers.