chore: update examples to gg v0.50.15 - #487
Merged
Merged
Conversation
TestADR054_ShearVariableFont_BoldVsRegular failed locally with GPU CoverageFiller (SparseStrips) because at 40px, AA fringe pixels dominate glyph body — pixel count comparison inverts for bold vs regular. Root cause: SparseStrips (4×4 tiles) and AnalyticFiller (scanline) produce different sub-pixel coverage at small sizes. NOT a gvar bug — variations applied correctly (verified via TextPath coordinate comparison). Fix: increase to 80px where glyph body dominates over AA fringe. Both rasterizers now produce bold > regular consistently.
Introduce advanceResolver — unified advance resolution used by Advance(), Glyphs(), and AppendGlyphs(). Priority: TT hinted > HVAR > raw hmtx. This matches drawGlyphs' hintedOrRawAdvance() ensuring MeasureString and DrawString agree on character positions (Skia/Chrome pattern). Enterprise research: Skia, FreeType, Chrome all enforce measurement == rendering advances from a single source controlled by hinting level. Fixes #479
MultiFace.Source() returns nil → panic in 4 GPU text locations. Add nil checks that return error instead of panic, causing graceful fallback to CPU path. Full per-font-run support planned in ADR-065.
advanceResolver incorrectly prioritized TT-hinted advances over HVAR for variable fonts. TT hint cache uses default-weight phantom points (no gvar deltas), producing wrong advances at non-default instances (wght=700). Fixed priority (FreeType ttgload.c:964-977 pattern): Static fonts: TT hinted > raw hmtx (unchanged) Variable fonts: HVAR > raw hmtx (TT cache skipped) Regression reported by @tsl0922: letters overlapping under shear at v0.50.14.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
14 examples updated