Closed yanone closed 3 months ago
Thanks @yanone How did you zero-in on those glyphs?
In code. I traced down the EraseOpenCorners filter that was displayed next to the error message. The filter resides in the glyphsLib
package (whereas most other filters reside in ufo2ft
). Then I added a print statement to the filter routine to print the glyph name.
I know, the error messages are terribly useless. Sorry about that.
And then in Glyphs I just tried to play around with the outlines of the respective glyphs and found erratic behaviour around the start point of the contours, which I solved by removing overlaps. That was a shot in the dark but it worked.
Thanks! While searching found the same issue on fontmake issue tracker. https://github.com/googlefonts/fontmake/issues/764
I don't know how the problematic outlines got created exactly (probably a bug in Glyphs), but removing the overlaps on two contours in
G
andcent
fixed the problem.