Closed kateliev closed 8 months ago
It seems that the affected glyphs are:
...all of which had a faulty
@tphinney this is now solved. I had to also regenerate some auto-glyph recipes. It is now fixed and the font builds again using UFO+fontmake.
That was… “interesting”! sheesh
@tphinney investigating the issue of the font not compiling under UFO+fontmake we discussed over private chat the there was anchor mismatch in glyph /m. Looking at the glyph in question it seems that the missing anchor is actually present but wildly out of sane glyph bounds.
This is only a speculation, but could it be that FL or fontmake is dropping the anchor because it is outside some given tolerance? Will have to investigate further.... Interesting enough this is happening only on slanted masters, perhaps it was due to some slanting error back then when we made those... or perhaps these were anchors with some smart formula that got lost?
Nevertheless I've experimented a bid and added new audit test to our toolset that will report such problems. The test found 64 possible candidates with anchors out of bounds on one or more layers, that i will manually check today.