Closed vv-monsalve closed 5 months ago
Another interpolation issue detected.
The issue has been solved but will be visible next time we generate fonts.
fixed
Hi @josescaglione. Please find here a PDF produced by Simon with all the interpolation issues detected at the source level.
The fonts in the lang-build
branch at commit 658f99f look good so far. I'm closing this here and will reopen if something new arises.
While this warning can point out some characteristics that may be by design, it has proven valuable in detecting interpolation issues. Please inspect all of the listed glyphs (at the bottom) and solve the wrong cases.
E.g.
- Glyph name: uni1EE1 Contours detected: 6 Expected: 3
makes it possible to detect the following glyph in font: <img width="134" alt="Screen Shot 2023-08-28 at 18 52 57" src="https://github.com/TypeTogether/Playpen/assets/48698976/f74668d1-96b2-454c-a297-c798d17b84c8">Which allows catching an interpolation issue caused by a discrepancy between the first nodes in
tildeshortcomb
in the source file.⚠ WARN: Check if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)