Merged
Conversation
wouterlucas
reviewed
Mar 18, 2026
| if (codepoint === undefined) continue; | ||
| let prevGlyphId = 0; | ||
| for (const char of text) { | ||
| const codepoint = char.codePointAt(0); |
wouterlucas
approved these changes
Mar 18, 2026
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
2 participants
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.
What was wrong
Kerning was being added to the next cursor advance, not to the current glyph placement.
That shifts kerning by one glyph, so pairs like AV/To/Wa render too loose in SDF.
Fix applied
In
SdfTextRenderer.ts:343, kerning is now computed as an offset for the current glyph.In
SdfTextRenderer.ts:355, kerning is applied to currentX before emitting the glyph.In
SdfTextRenderer.ts:377, cursor advance now uses only glyph.xadvance + letterSpacing afterward.