New Fontbakery error "Ensure VFs have 'ital' STAT axis."

I exported a font with all my usual settings, but am getting an error I’ve never seen before.

Strangely, the error says VFs but the font files are static .otf

Using Glyphs 3.3.1 (3341)

John

Ensure VFs have 'ital' STAT axis.

opentype/STAT/ital_axis

Check that related Upright and Italic VFs have an 'ital' axis in the STAT table.

Since the STAT table can be used to create new instances, it is important to ensure that such an 'ital' axis be the last one declared in the STAT table so that the eventual naming of new instances follows the subfamily traditional scheme (RIBBI / WWS) where "Italic" is always last.

The 'ital' axis should also be strictly boolean, only accepting values of 0 (for Uprights) or 1 (for Italics). This usually works as a mechanism for selecting between two linked variable font files.

Also, the axis value name for uprights must be set as elidable.

* FAIL :

Font Hellafine-ExtraBold.otf has no STAT table

* FAIL :

Font Hellafine-BoldItalic.otf has no STAT table

* FAIL :

Font Hellafine-Bold.otf has no STAT table

Perhaps the VF part is a misnomer. STAT tables make sense in static fonts as well. You can force the table with the Write STAT table parameter. But I’m not sure if it always works the way it should in static fonts. YMMV.

I added the “Export Stat table” custom parameter to every Export. Now I get this error:

And these warnings:

Just for comparison, I ran some older files that passed through without any issues and they also brought up the errors, so the problem might be in Fontbakery.

It depends on the profiles/checks you are running in fontbakery. Some tests are unnecessarily strict. You can exclude a check with the -x flag. So the command may look like this:

fontbakery check-profile opentype -x opentype/STAT/ital_axis font.otf

Typenetwork confirmed that this is a FontBakery error. Hopefully it will be fixed soon, but in the meantime we can ignore. Thanks for looking into it though! :smiley: