You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to theleagueof/raleway#17 the variable font builds seem to use the first named instance as the family name, which makes this project's VF is rendered “League Spartan Extralight”. Not so smooth for something with a weight axis that goes to 900.
Having poked at his a little I don't think it's even a bug in Fontship, I think it goes all the way up the tree to fontmake. But wherever the bug is and however it gets fixed a new release should be done for this font when this is taken care of.
The text was updated successfully, but these errors were encountered:
Yeah, this is unfortunate but common. A workaround would be to insert the regular instance as a master, and make that the font origin. Not ideal to make a separate master just to account for this. I thought running gftools fix-vf-meta in the build was supposed to fix this, but clearly not.
Similar to theleagueof/raleway#17 the variable font builds seem to use the first named instance as the family name, which makes this project's VF is rendered “League Spartan Extralight”. Not so smooth for something with a weight axis that goes to 900.
Having poked at his a little I don't think it's even a bug in Fontship, I think it goes all the way up the tree to
fontmake
. But wherever the bug is and however it gets fixed a new release should be done for this font when this is taken care of.The text was updated successfully, but these errors were encountered: