The === ligature is not the same height as the => ligature or vice versa

[mishamyrt]

The === ligature is not the same height as the => ligature or vice versa

[mishamyrt]

I don't seem to have this problem in either the terminal or the code editor. What operating system and software are you using?

[Quorsor]

Using the Command Prompt in the Terminal in Windows 11.

Was running cargo run when I found it.

[mishamyrt]

There seems to be a problem with win metrics. I'll try to look into it during the week

[Quorsor]

Strange, I just tested it in Word and it works.

Edit: Just looked at it again and I can definitely see that there's some wonkiness going on.

[mishamyrt]

I did some research into this problem and came to this conclusion: this behavior is caused by the aliasing algorithm in the Windows interface.

I was not able to reproduce the problem in macOS and Linux. In Windows, the problem is fixed by disabling text anti-aliasing. I don't know yet how to solve the problem permanently, but I think I was able to improve the situation a bit in the 2.300 release.

I've also noticed that the problem only occurs when installing individual ttf fonts. If you install variable, everything is fine.

[Quorsor]

Installing the variable version instead of individual ttf does fix the problem. Thanks!