- Add fonts/READY-PACKAGE.md: exact woff2/ttf names, OFL license steps, pixel-match checklist vs verae-2026-design CERT-01.html/png - Cross-link README, LICENSE-FONTS, fetch-fonts.example.sh status - certificate.html residual points at READY-PACKAGE (ops drop-in) Software path unchanged; go test pdfcert + statuslang PASS. Binaries remain operator deploy-host only (not committed).
1.5 KiB
Font license note (printit CERT)
This directory does not ship Fraunces (or JetBrains Mono) binaries.
Operator responsibility
The operator (site deploy owner) must place SIL Open Font License 1.1 (OFL) Fraunces themselves if they want self-hosted brand type:
- Obtain Fraunces under OFL from upstream (e.g. google/fonts
ofl/frauncesor underscript-type/fraunces). - Drop planned woff2 filenames here (see
README.md). - Place the upstream
OFL.txtbeside those binaries (keep copyright notices). - Do not vendor proprietary faces or strip OFL notices.
Until those files exist on the deploy host, certificate.html falls back to the Google Fonts CDN (or system serif). Git keeps only placeholders (.gitkeep, docs, example fetch script) — no woff2 in-repo by default.
Optional mono: JetBrains Mono is also OFL; same operator drop-in rules.
PDF certificates
Issued PDFs (internal/pdfcert) use core Times/Helvetica by default.
EmbedBrandFonts is off unless explicitly enabled (Input or VERAE_EMBED_BRAND_FONTS).
When on, gofpdf may register a licensed .ttf/.otf from VERAE_BRAND_FONTS_DIR or this directory; unsupported faces log and keep Times (not provided here).
See also
README.md— planned filenames, local-first probe, fetch exampleREADY-PACKAGE.md— exact names, license steps, CERT-01 pixel checklistfetch-fonts.example.sh— commented upstream URLs only- OPEN-ISSUES #7 (CERT Fraunces pixel residual)