Repository navigation
feat(text): DynamicTextCoverage finds characters a font stack cannot draw - #17
Merged
Merged
Conversation
zignd
force-pushed
the
feat/font-coverage
branch
from
October 10, 2026 23:09
1ea5ca4 to
ea95b91
Compare
zignd
force-pushed
the
feat/font-coverage
branch
from
October 10, 2026 23:29
ea95b91 to
67cb2e1
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.
Closes #12.
DynamicTextCoverage.FindMissingGlyphsover aDynamicUIFont(face plus fallbacks) or a list of faces, returning each uncovered code point once with the first string that contains it; control and format characters are ignored. Additive; tests for covered text, a missing glyph, and a fallback face restoring coverage.