Control-glyph set incomplete
Audit code: control-glyphs-missing
Definition
The 12-glyph control set (the letters foundries draw first to establish proportion + texture: H, O, n, o, +, period, etc.) is incomplete. These should land before mass-drawing the rest because they set the visual rhythm everything else has to match.
How Patens surfaces this
The Patens audit module checks for control-glyphs-missing across five teaching surfaces: the edit-panel inline issue list, the
project-wide audit page, the release pre-flight check, the family hub,
and the home-page project tile. Every surface shows the same plain-English
explanation and links back to this page. This rule is detection-only — there's no automatic fix because the
correction is design-dependent (it requires a judgment call about the
glyph's intended shape or the font's intended behaviour). The audit
message links to the specific glyph or field that needs attention.
Run this check yourself
Patens runs every audit rule live as you draw — including this one.
The editor (in private alpha) shows control-glyphs-missing firing on real
glyphs, or check your own work from the CLI:
npx patens audit your-project.font.jsonCanonical references
Primary literature where this rule is established or explained. Drawn from the open-licensed corpus — browse the full 42-source canonical library or read the research artifact.
- The Unicode Standard, Version 16.0 ↗
Unicode Consortium · 2024 · Unicode Consortium· § C0 Controls (U+0000 - U+001F)
Control codepoints (CR, LF, tab) should have glyph entries (typically zero-advance or .notdef) for proper text handling.