Depending on which character is used first in a font instance, that will set the look for the symbols for other unicode characters. To demonstrate this behavior see the following code (I have tested on windows 10 and 11, python 3.11.1):
This is my understanding of the problem: If a font instance does not support a unicode character, then the font instance will select a fallback font-family. However, depending on which unicode character that is used, I believe different fallback font-families are selected and therefore the look of the characters may differ.
I do not know if this is a bug in tkinter because I noticed this behavior in VSCode, IDLE, Google Chrome, Edge and Slack.
Depending on which character is used first in a font instance, that will set the look for the symbols for other unicode characters. To demonstrate this behavior see the following code (I have tested on windows 10 and 11, python 3.11.1):
This is my understanding of the problem: If a font instance does not support a unicode character, then the font instance will select a fallback font-family. However, depending on which unicode character that is used, I believe different fallback font-families are selected and therefore the look of the characters may differ.
I do not know if this is a bug in tkinter because I noticed this behavior in VSCode, IDLE, Google Chrome, Edge and Slack.
I asked this question on stackoverflow if you want to read more on the comments we had, see https://stackoverflow.com/questions/75026676/why-does-some-unicode-characters-change-shape-depending-on-which-character-is-fi/.
The text was updated successfully, but these errors were encountered: