Add font comparison test stand for GF build validation#3
Draft
Add font comparison test stand for GF build validation#3
Conversation
psd-coder
force-pushed
the
gf-fonts-test-stand
branch
3 times, most recently
from
0e292db to
f0756ce
Compare
Add config.yaml, requirements.txt, AUTHORS.txt, CONTRIBUTORS.txt, .gitignore, and Instructions.txt for Google Fonts compliance. Add build.py that patches glyphsLib Smart Component bugs at runtime (Group key handling + missing masters for UltraBlack) before running gftools builder. Original source is never modified.
Do a set of changes described in the Instructions.txt. Replace designer-named fonts (Cn/Nr/Std/sWd/Wd/xWd/uWd shorthand naming) with GF-spec builds: standard width/weight naming, STAT table, variable font named MartianGrotesk[wdth,wght].ttf, covering 63 statics + VF across 7 widths x 9 weights in TTF, OTF, and WOFF2 formats.
Add sources/build.sh as single-command entry point per Google Fonts upstream guide.
HTML page for visual validation of GF build against designer fonts: side-by-side and overlay glyph comparison across all Unicode blocks, with variable and static font support (7 widths x 9 weights), fullscreen single-glyph view, and controls for weight, width, opacity, and glyph size.
psd-coder
force-pushed
the
gf-fonts-test-stand
branch
from
f0756ce to
694ab6d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Adds a browser-based visual comparison tool for validating that the GF-compliant font rebuild didn't break any glyphs compared to the original designer fonts.
Note: This is a temporary testing artifact for the GF build branch, not intended to be merged into main.
Problem Statement
After rebuilding fonts with GF-compliant naming and tooling, there was no way to visually verify that glyph shapes remained identical across all 662 codepoints, 7 widths, and 9 weights.
Solution Approach
documentation/comparison/index.html: a self-contained HTML page that loads both old (designer) and new (GF) variable fonts side by sidedocumentation/comparison/old-ttf/with full name mapping (e.g.Cn->Condensed,Nr->SemiCondensed,Std-> Normal, etc.)Testing
Open
documentation/comparison/index.htmlin a browser. Click any glyph to inspect it fullscreen. Use overlay mode with opacity slider to spot shape differences. Switch between variable and static font sources to verify all 63width/weight combinations.