Remove fallback code for glyph indices#30168
Merged
QuLogic merged 1 commit intomatplotlib:text-overhaulfrom Jun 19, 2025
Merged
Remove fallback code for glyph indices#30168QuLogic merged 1 commit intomatplotlib:text-overhaulfrom
QuLogic merged 1 commit intomatplotlib:text-overhaulfrom
Conversation
Glyph indices are specific to each font. It does not make sense to fall back based on glyph index to another font. This could only really be populated by calling `FT2Font.set_text`, but even that was fragile. If a fallback font was used for a character with the same glyph index as a previous character in the main font, then these lookups could be overwritten to the fallback instead of the main font, with a completely different character! Fortunately, nothing actually uses or requires a fallback through glyph indices.
Member
Author
|
As an example, in DejaVu Sans, the letter A is glyph index 36: which has metrics like: In the Last Resort font, the Tibetan block is glyph index 36: So if we have a string with both using fallbacks, then the last glyph 'wins': If we had multiple fonts in the fallbacks, and multiple characters in those fonts that used the same glyph index, then lookup would depend on the order of characters in the text! |
anntzer
approved these changes
Jun 15, 2025
Member
|
looks good! Can you please drop the last commit and self-merge? The windows failures are a know issue with a new numpy release that is fixed on main. |
tacaswell
approved these changes
Jun 19, 2025
1c722e0 to
41cc933
Compare
Member
Author
|
Not going to wait for CI, because it's just going to fail, and then run again when merged, and fail there too... |
wavebyrd
pushed a commit
to wavebyrd/matplotlib
that referenced
this pull request
Mar 13, 2026
Remove fallback code for glyph indices
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
3 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.
PR summary
Glyph indices are specific to each font. It does not make sense to fall back based on glyph index to another font.
This could only really be populated by calling
FT2Font.set_text, but even that was fragile. If a fallback font was used for a character with the same glyph index as a previous character in the main font, then these lookups could be overwritten to the fallback instead of the main font, with a completely different character!Fortunately, nothing actually uses or requires a fallback through glyph indices, and this is all internal to the extension.
Note to reviewers: the second commit here is just the last commit from the
text-overhaul-imagesbranch, but is not actually relevant here. Please only review the first commit as the second will be dropped before merging. If you prefer, I can targetmain, but I thought this was relevant to thetext-overhaulbranch.PR checklist