Hello,
It seems that Glyphs adds two anchors in (all?) Arabic glyphs at (0,0) and FontValidator is not happy with it.
Who knows more about this?
Which version of the app?
Possibly makeOTF generating zero offsets to non-existing anchors. Can be interpreted as an anchor record with invalid format.
1 Like
2.6.1. 1230
Same Problem Version 2.6.1 (1230)
This is actually a bug in fontvalidator. It will be fixed, soon.
And the new version of makeOTF writes empty anchors differently. Both are technically correct.
1 Like
I’m running FontValidator 0.1 (8) and Glyphs Version 2.6.6 (1343). I’m seeing a whole load of these errors (but there are no problems with the font on Mac or Unix). Is it a genuine error, or just a problem with FontValidator…?
Is this a variable font?
No. But there’s a weight custom parameter in File > Font Info > Font… ? Perhaps I’ll delete it and see what happens.
I’ve seen that error, too. I suspect that it is a fontValidator problem.
1 Like
Cool, thanks.