You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing Variable Font support in my software, I tried Fraunces and it seems that the Italic font has different information than I expected.
Please see below image of the fonts open in FontForge:
The italic font does not seem to have a preferred family name, and the Family entry is Fraunces instead of "Fraunces 144pt S100 Black Italic", which would be the same structure as the Regular font.
In my case I use the preferred Family name to group the different fonts into one entry eg. "Fraunces", and then map the entries back to their actual the font Family name, which doesn't work with the current structure.
To test, I checked Arial and Arial Black which seem to have the same preferred name but unique Family names.
Apologies if this has been logged somewhere, I couldn't find an issue.
Please close this issue if intentional/not a real bug.
Screenshots
Environment
OS: Windows 10 v1709
The text was updated successfully, but these errors were encountered:
While testing Variable Font support in my software, I tried Fraunces and it seems that the Italic font has different information than I expected.
Please see below image of the fonts open in FontForge:
The italic font does not seem to have a preferred family name, and the Family entry is Fraunces instead of "Fraunces 144pt S100 Black Italic", which would be the same structure as the Regular font.
In my case I use the preferred Family name to group the different fonts into one entry eg. "Fraunces", and then map the entries back to their actual the font Family name, which doesn't work with the current structure.
To test, I checked Arial and Arial Black which seem to have the same preferred name but unique Family names.
Apologies if this has been logged somewhere, I couldn't find an issue.
Please close this issue if intentional/not a real bug.
Screenshots
Environment
The text was updated successfully, but these errors were encountered: