STAT composed name does not match fvar instance

Audit code: stat-instance-name-mismatch

Definition

A STAT axis-value combination produces a style name that doesn't match the corresponding fvar named-instance style name. Result: the OS may display the STAT-derived name in some apps and the fvar-derived name in others. Convention: keep them identical. Patens can rename one to match the other.

How Patens surfaces this

The Patens audit module checks for stat-instance-name-mismatch 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 stat-instance-name-mismatch firing on real glyphs, or check your own work from the CLI:

npx patens audit your-project.font.json

Canonical references

Primary literature where this rule is established or explained. Drawn from the open-licensed corpus — browse the full 38-source canonical library or read the research artifact.

OpenType Specification 1.9.1 ↗
Microsoft Typography · 1997 · Microsoft Corporation· § STAT — coordination with fvar instances

OpenType 1.8.2 spec notes that STAT axis-value names should compose to the same instance name that fvar declares — divergence causes inconsistent display across apps.

Related rules in Variable-font compatibility

← All 101 audit rules