Version string format invalid

Definition

Version string doesn't match the OpenType "MAJOR.MINOR" convention (e.g. "1.000", "2.345"). Many tools parse it into head.fontRevision and round non-conforming strings — best to follow the convention for predictable behavior.

How Patens surfaces this

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

npx patens audit your-project.font.json

Related rules in Metadata

• meta-no-copyright Copyright notice empty
• meta-no-designer Designer field empty
• meta-no-designer-url Designer URL empty
• meta-no-license License field empty
• meta-no-license-url License URL empty
• meta-no-manufacturer Manufacturer field empty
• meta-no-vendor-id OS/2 vendor ID empty
• meta-vendor-id-invalid OS/2 vendor ID invalid