search

googlefonts / fontc

Where in we pursue oxidizing (context: https://github.com/googlefonts/oxidize) fontmake.
Apache License 2.0
83 stars 13 forks source link

Handle DesignSpace+TTF merging like fontTools.varLib? #672

Open twardoch opened 10 months ago

twardoch commented 10 months ago

FontLab currently builds VFs so that it builds a DesignSpace file and a set of compatible master TTFs (not UFOs), and then calls fontTools.varLib to perform merging into a VF.

Would fontations + fontc support such a scenario?

Let's say we have a DesignSpace like in:

https://github.com/fonttools/fonttools/blob/main/Tests/varLib/data/SparseMasters.designspace

which actually references the TTFs (not UFOs), and we have master TTFs — like those in (but not TTX, just TTF):

https://github.com/fonttools/fonttools/tree/main/Tests/varLib/data/master_ttx_interpolatable_ttf

What would be a way to produce a TTF VF from such a setup using fontc? Or what would need to happen to make it possible?

rsheeter commented 9 months ago

Pardon the slow response, was OOO.

Thinking "aloud," building from TTF/TTX statics is basically reintroducing the merge process; I don't think we want that.

If you have the data to produce compatible master TTFs then I would think you have the data to produce fontc IR so my kneejerk reaction is to want to add a fontlab2ir crate and avoid handling statics.