-
Notifications
You must be signed in to change notification settings - Fork 93
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
"No default source" when I have a discrete axis map AND split variable fonts defined #1011
Comments
This seems related to #920, but slightly different. There, a variable font output is specified as having a location that doesn’t have a source at all (which should still work, IMO). While here, the location does have a source, but it’s just not the default location for the full designspace. |
In the error message from fontmake, after "Found master locations:" there's nothing, so it sounds like a bug in the function splitVariableFonts that may not preserve the correct sources in the italic-only designspace. Could you either share your designspace file (axes + sources) or check on your side the following:
|
I’m currently using FontMake
3.6.0
(the current release).I have a designspace which is building well with:
ital
axis with a mapping to make it a discrete, binary, on/off axisital
rangeHowever, if I also add
variable-font
elements that use just one side or the other of theital
range (e.g. split roman vs italic VFs), I get an error.However, I do have a source at Optical Size=8, Weight=700:
Here’s my
ital
axis and map:Here’s my variable-fonts element:
If my variable fonts element is only the first font, things work fine, and that font compiles as expected:
Or, if I remove the
mapping
from myital
axis, all three variable fonts build as expected:As far as I understand things, this should all be working, with both the
ital
mapping and all three variable font outputs.Here’s my full `axes` element, in case that is helpful. (Click to expand)
Am I doing something wrong, or missing something?
Thanks so much for any insights here!
The text was updated successfully, but these errors were encountered: