Replies: 3 comments 9 replies
-
It looks like a Font Bakery bug. Are you able to provide sample font files so that I can try to replicate the problem locally and then try to fix it? |
Beta Was this translation helpful? Give feedback.
-
The issue could have been the same as the one that was fixed by fonttools/fonttools#2684 |
Beta Was this translation helpful? Give feedback.
-
When the VF is purely Italic there is no 'Regular' or 'Bold' styles (but 'Italic' and 'Bold Italic' instead), and it seems FontBakery gets confused with these checks in particular, and fails: Shouldn't it behave differently in such a situation? |
Beta Was this translation helpful? Give feedback.
-
We have 2 Variable Fonts for the same Family, one for Romans and one for Italics, they should be style linked.
Fontbakery raise
Fails
about the italic VF:The “wght” axis coordinate of the “Regular” instance must be 400. Got None instead. [code: wght-not-400]
obviously the font doesn’t have Regular but Italic insteadThe “wght” axis coordinate of the “Bold” instance must be 700. Got None instead. [code: wght-not-700]
same thing, no Bold but Bold Italic insteadThe following AxisValue entries on the STAT table should not contain “Italic”: [‘nameID 258: Light Italic’, ‘nameID 259: Regular Italic’, ‘nameID 260: Bold Italic’, ‘nameID 261: ExtraBold Italic’] [code: bad-italic]
Q: Should we add an
ital
axis withdefault=“1" maximum=“1” minimum=“1"
for specifying the font is italic even though it doesn’t vary on this axis? (similarly the Roman VF could have thisital
axis set withdefault=“0” maximum=“0" minimum=“0”
)Is there a standard way at solving this issue that must be quite common indeed?
Thanks for your input.
Beta Was this translation helpful? Give feedback.
All reactions