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
Italic isn’t a design axis; it’s handled separately, for two reasons: first, you don’t really want people to be producing semi-italic fonts, and second, often the italic shapes of characters are quite different to the upright shapes, so it’s not possible or sensible to interpolate between them.
From a design perspective, this all makes sense. From a tech perspective, the spec does provide the 'ital' axis for those who want to go there. More importantly, the italic axis must appear in the STAT table for a font (even if the given font is a Roman) in order to tell software how the given font fits into the overall family. Essentially, the STAT table entry for a Roman tells the OS that there exists elsewhere an italic version of this font, which allows applications to nicely organize all the fonts in a family.
The text was updated successfully, but these errors were encountered:
There's a little aside in the doc:
From a design perspective, this all makes sense. From a tech perspective, the spec does provide the 'ital' axis for those who want to go there. More importantly, the italic axis must appear in the STAT table for a font (even if the given font is a Roman) in order to tell software how the given font fits into the overall family. Essentially, the STAT table entry for a Roman tells the OS that there exists elsewhere an italic version of this font, which allows applications to nicely organize all the fonts in a family.
The text was updated successfully, but these errors were encountered: