text: Fix getCharBoundaries() for 0-width characters
#18860
Conversation
This file contains 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
kjarosh
added
text
adrian17
approved these changes
Dec 9, 2024
| @@ -613,6 +619,9 @@ impl<'gc> Font<'gc> { | |||
| // Step horizontally. | |||
| transform.matrix.tx += twips_advance; | |||
| x += twips_advance; | |||
| } else { | |||
| // No glyph, zero advance | |||
| glyph_func(pos, &transform, &Glyph::empty(), Twips::ZERO, x); | |||
There was a problem hiding this comment.
What's the difference between processing a "noop" glyph and skipping it entirely?
There was a problem hiding this comment.
I've described it in my commit message:
This is a natural assumption of Font::evaluate and makes writing code easier.
Code that renders glyphs will work the same way as non-renderable characters
will produce empty glyphs, but code that evaluates the font for measurement
purposes will use this property.
I'll add a short comment about it here too.
kjarosh
force-pushed
the
evaluate-missing-glyphs
branch
from
2a8e0c7 to
ff00d12
Compare
This is a natural assumption of Font::evaluate and makes writing code easier. Code that renders glyphs will work the same way as non-renderable characters will produce empty glyphs, but code that evaluates the font for measurement purposes will use this property.
kjarosh
force-pushed
the
evaluate-missing-glyphs
branch
from
ff00d12 to
d8404e7
Compare
This test verifies how getCharBoundaries() works when glyphs are missing.
This test verifies how getCharBoundaries() works when glyphs are missing due to embedded font not being present.
kjarosh
force-pushed
the
evaluate-missing-glyphs
branch
from
d8404e7 to
89c2faa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Basically,
getCharBoundaries()returns null for 0-width characters. This PR also fixes a bug where some characters (with missing glyphs) were not taken into account properly becauseFont::evaluateskipped them.