rimas-kudelis
commented
1 week ago Quoting the relevant FontValidator help file below:
glyf: Intersecting contours
The glyph indicated in the validation log contains contours that intersect with themselves (overlap) or other contours of the glyph shape. These intersections may cause the rasterizer to unpredictably fill the glyph shape. The different type of intersections are discussed below.
Self-intersecting contours
This type of intersection may take the form of a tiny loop on one of the contours of the glyph and results from a poorly controlled Bezier curve becoming undesirably deformed. This self-intersection can be very hard to see, even at high magnification. Other types of self-intersection occur when a straight line doubles back on itself, and when a single contour loops around and touches itself. To fix these problems, use an outline editing tool to shift the problematic control points or alter the type of curve used.
Multi-contour intersection
Contours located very near each other may be separate at some sizes but may intersect at other sizes due to scaling and gridfitting. This problem may be fixed by using an outline editing tool to move control points and make the contours more distant.
For more information, see the glyf table specification.
HinTak
What needs to be checked?
Intersecting and/or duplicate contours or contour parts in font glyphs.
Detailed description of the problem
One of MS Font Validator's checks that I think I'm missing in FontBakery is that of intersecting contours (error code E1111). While sometimes intersections are okay and intended, that check also helps find cases of mistakenly duplicated contours in fonts.
For example, here I have a glyph where the second contour (original letter z) is a subset of the first contour (letter z with the retroflex hook). The smaller contour was likely pasted from another glyph before the designer drew the new glyph on top, but was then simply forgotten. All it does there is occupies extra bytes at the very minimum.
It would be nice if FontBakery could warn about such cases.
Again, while Font Validator reported even things like lines that barely touched, I find that less useful than if it reported matching vectors/parts of contours/contours.
Resources and steps needed to reproduce the problem
Could the glyph file above serve as a test?
Suggested profile
Universal (broadly accepted best practices on the type design community)
Suggested result
⚠️ WARN (A potential issue that may need to be addressed)
Severity assessment
2