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
When a GSFont object is constructed, it instantiates .axes with the default axes, width and weight. Glyphs 3 files specify the axes explicitly, so this is replaced with GSAxis objects read from the plist. But Glyphs 2 files don't have an axes entry, so they continue to get the default ones. This means that a font which has no meaningful variation on the weight axis still reports having a weight axis.
Whether this is correct or wrong is probably a matter of interpretation. I feel like it's wrong, personally.
The text was updated successfully, but these errors were encountered:
When a GSFont object is constructed, it instantiates
.axes
with the default axes, width and weight. Glyphs 3 files specify the axes explicitly, so this is replaced withGSAxis
objects read from the plist. But Glyphs 2 files don't have anaxes
entry, so they continue to get the default ones. This means that a font which has no meaningful variation on the weight axis still reports having a weight axis.Whether this is correct or wrong is probably a matter of interpretation. I feel like it's wrong, personally.
The text was updated successfully, but these errors were encountered: