forked from wez/wezterm
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This was a bit of a PITA to run down; the essence of the problem was that the shaper was returning an x_advance of 0 for U+3000, which caused wezterm's shaping layer to elide that glyph. I eventually tracked down the x_advance to be the result of scaling by an x_scale of 0, which in turn is the result of harfbuzz not knowing the font size. The critical portion of this diff is the line that advises harfbuzz that the font has changed after we've applied the font size. The rest is just stuff to make it easier to debug and verify. This: ``` printf "x\u3000x." ``` Now correctly renders on screen as "x x". fixes: wez#1161
- Loading branch information
Showing
5 changed files
with
198 additions
and
23 deletions.
There are no files selected for viewing
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
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
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
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
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