Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GSFont.axis axes on format 2 files with one axis returns two axes #990

Open
simoncozens opened this issue Mar 4, 2024 · 2 comments
Open

Comments

@simoncozens
Copy link
Collaborator

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.

@anthrotype
Copy link
Member

I noticed that as well at some point.. What does Glyphs.app's python API returns for such a font when you ask it to list its axes?

@schriftgestalt
Copy link
Collaborator

schriftgestalt commented Mar 4, 2024

I didn’t check but that is most likely fixed in the Glyphs3 branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants