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

Start thinking about "static-second" development workflows #1753

Open
skef opened this issue Aug 21, 2024 · 0 comments
Open

Start thinking about "static-second" development workflows #1753

skef opened this issue Aug 21, 2024 · 0 comments

Comments

@skef
Copy link
Collaborator

skef commented Aug 21, 2024

We have put a lot of effort into developing a variable-first workflow, and plan to put more effort into it until it's finished. One thing this eliminates is the need to generate a lot of individual feature files corresponding to different input masters.

Generally speaking the variable font produced in this way should have just about all the information that corresponds to one of our static fonts. So I think we should start to consider whether we can shift our static font production process from separately interpolated font files with their own feature file hierarchies to files generated by a process something like:

  • Instancing the variable font to produce a temporary static fonts
  • Removing overlap from the glyphs in the instanced version
  • Cleaning up other remaining values (PostScript name, etc.)

as this would mean we only ever have to have one set of feature files, and only need to worry about the mechanics of interpolation to produce the variable glyph outlines.

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

1 participant