How does FC handle a contour with one point? It appears that FC v12 on Win10x64 passes it right through to the output, and that’s causing me heartburn. Maybe FC should delete such contours?
This does happen in production fonts. Times New Roman v7.00 has a flock of them - for example: Glyph #3022, mapped to $2000 (En Quad). This and the next handful of glyphs / code points all have a single contour with a single point. The other tools I am using on my project see this as a non-empty glyph, and then crash trying to deal with the degenerate contour. I opened this font through FontCreator, in the hopes of fixing this clearly erroneous situation, but can find no way to edit the “contour”.
So this is not really a bug in FC in the traditional sense, but it might be nice if FC could gracefully deal with this clearly bogus situation (in the latest version of the most heavily (over)used font in the world) and delete such contours - producing a valid output font out of a mangled input font.
I realize I can rebuild such glyphs by hand. However …
- typical users would have no way to detect that this degenerate situation exists in the font, and
- If the glyph had other contours in addition to the degenerate contour, I’m not sure how I might handle it.