@madig - I wonder if when you updated the requirements.txt file in our last PR that something changed in the way instances are generated from the designspace file. Because we've never modified the instance naming before and it always worked OK.

I'll take a look later, gotta run now. If you haven't, try changing the static fonts compilation function to also change the family names for all instances in the designspace before instantiating the instantiator and then remove the single name setter after it.

I'll take a look later, gotta run now. If you haven't, try changing the static fonts compilation function to also change the family names for all instances in the designspace before instantiating the instantiator and then remove the single name setter after it.

:)

:)

It's like you read my mind.

@madig - I wonder if when you updated the requirements.txt file in our last PR that something changed in the way instances are generated from the designspace file. Because we've never modified the instance naming before and it always worked OK.

I think this is a case of setting things in a different order. Font naming is annoying as is and maybe the Designspace ergonomics aren't the best here... you could probably get rid of the familyname, stylemapfamilyname and stylemapstylename instance fields and ufo2ft would do the right thing for you, as long as you set the correct familyName (and unset styleMapFamilyName) in the sources.

@madig - I wonder if when you updated the requirements.txt file in our last PR that something changed in the way instances are generated from the designspace file. Because we've never modified the instance naming before and it always worked OK.

I think this is a case of setting things in a different order. Font naming is annoying as is and maybe the Designspace ergonomics aren't the best here... you could probably get rid of the familyname, stylemapfamilyname and stylemapstylename instance fields and ufo2ft would do the right thing for you, as long as you set the correct familyName (and unset styleMapFamilyName) in the sources.

Right, but the point I was making before was that the code had worked fine with just setting names in the sources and then suddenly stopped working. That’s why I was wondering.

Something I just thought of. Previously we were setting the font family name in the source font files (eg, source.info.familyname) but I don’t believe that actually changed anything in the designspace document. Potentially, the designspace document is now being given greater priority over the source fonts info for instance generation, for whatever reason, requiring modification of the designspace naming.

I have been a poor steward of this repository, and I should have produced a build in the interim to make it easier for folks who want to use Cascadia.

I've been off the ball for quite a while, and it is time to get back on it. Sorry for any delay/for disappearing.

It's ok, we're all open-source here.