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

Export variable instances as DSv5 variable-fonts #977

Merged
merged 3 commits into from
Feb 1, 2024

Conversation

khaledhosny
Copy link
Collaborator

Export Glyphs 3 as DesignSpace v5 variable-fonts, setting their custom parameters is the variable-font lib, mainly using the "public.fontInfo" key.

In the next commits we will be generating DesignSpace variable-font’s
for them, and these values will generate noise in the lib even though
they are not actually set in the source.
Introduces some formatting change, to minimize the diff in the next
commit.
Export Glyphs 3 as DesignSpace v5 variable-fonts, setting their custom
parameters is the variable-font lib, mainly using the "public.fontInfo"
key.
ufo_varfont.lib["public.fontInfo"] = info

for key in ufo.lib:
ufo_varfont.lib[key] = ufo.lib[key]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder, what could end up here? Any params for which there isn't a corresponding fontinfo key basically? I guess it's fine to store them here, even though they won't be used right know by anybody.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. They might be useful for round-tripping, though this PR does not handle it right now.

Copy link
Member

@anthrotype anthrotype left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Khaled!

@anthrotype
Copy link
Member

This does not round-trip back to .glyphs, if I understand correctly, right? How hard do you reckon will that be? Maybe we could file an issue as a TODO for later.

@khaledhosny
Copy link
Collaborator Author

I don’t use ufo2glyphs myself, but I might look into it later. I’ll file an issue for now.

@khaledhosny
Copy link
Collaborator Author

I don’t use ufo2glyphs myself, but I might look into it later. I’ll file an issue for now.

#978

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

Successfully merging this pull request may close these issues.

2 participants