zooqueen 95614191a8 the release tree names itself Zen ...

fonts/ was built before the family was renamed, so every binary a clone
installs — otf, ttf, variable, woff2 — still read the upstream family name, vendor VRCL
and the upstream designers in its name table. @font-face hid it, because a face
is bound to whatever family the CSS declares, so the npm copies looked right
while the desktop release, the QA input and anything a designer dragged into a
font book announced the wrong foundry.

The sources were already right — Glyphs holds familyName Zen and set-fontinfo
keeps HNZO there — so a rebuild fixes Sans and Mono outright. Zen Pixel is the
exception: gftools builds only its variable, its five static cuts are exported
by hand, and an export skips the source fields. name.py now covers exactly
those, and the build runs it after restoring them, so the tree is correct
whichever way a file arrived. Each cut is its own family with a Regular
subfamily — nothing orders five drawings of one alphabet, so a font menu should
list them side by side.

create-release-zip copied OFL.txt, which this repo has never had; the licence is
LICENSE.txt. copy-npm-fonts wrote to packages/next, which does not exist, so the
package's fonts were whatever was last committed rather than what was just
built. Both now name the real paths, and the pixel variable reaches the package
as woff2 so the web can have the element axis too.

nameID 0 keeps the upstream notice above ours. OFL §2 binds each copy to it.

2026-08-24 14:36:44 -07:00

18 KiB

Raw Permalink History

View Raw