Problem in === at font size 16 and below

[asifahmad134]

The space between the three bars of ligature (===) is not even at small fonts, please take a look at screenshots both in playground and in vs code

[subframe7536]

That is a common issue in small size among all popular monospace fonts and that depends on the screen resolution of your monitor.

[asifahmad134]

Thanks for prompt reply, I am using hp laptop with 15.3' 1080p display. As per repo instructions, i am using hinted NERD fonts. can there be any solutions for it? so far i have experienced this with === ligature only.

[subframe7536]

Maybe you should adjust the zoom factor, line height or font size in VSCode.

[asifahmad134]

yes, increasing the font size to 20 or above removes this, but my requirement is 16. Also, at size 14, this discrepancy removes, and below it appears again. So, please take a look at it in the next release. Otherwise, I am OK and grateful for this awesome font.

[subframe7536]

Have you tried increase the font weight? That may affect the font hint.

[subframe7536]

Or you can try this verion. The spacing of === is increased

MapleMonoDebug-Regular.zip

[asifahmad134]

Sorry, but No; increasing weight or DEBUG fonts don't work. I am enclosing my vs code settings, may be there it can be error. Also Note: I am using Maple Mono NF hinted 7.5.

settings.json

[subframe7536]

The font family of the debug font is Maple Mono Debug

[asifahmad134]

The font family of the debug font is Maple Mono Debug

Yes, I have also tried vs code with that, it still doesn't work

[subframe7536]

There exists similar issues in other popular monospace font:
tonsky/FiraCode#119
JetBrains/JetBrainsMono#25

And you can test it using hb-view /path/to/ttf --font-size=13 --font-ppem 8:8 --text="===" -o test.png (what is it?) to see if the font itself is correctly rendered.

[asifahmad134]

Thanks, sub frame, you are right. i have read through the firacode and jbmono issues, i think the reason is due to rendering of these fonts in vscode on linux (in my case ubuntu 25.04)

vscode 103, ubuntu 25.04, s16

NOW check other editors gedit, gnome-text-editor and sublime tex. only sublime text has very slight

NOW, check vscode 103 rendering on win 1124H2, s16

I am a beginner, at age 44 learning to code, but my guess is that perhaps issue is not on all these fonts. its rendering of vscode on linux. i request you to file issue at vscode, as perhaps you will be better to explain technically

[subframe7536]

Thanks again for the detailed discussion. But to be honest, I also have very limited knowledge about font rendering—even though I created this font! Typography is a deep and nuanced field, and I’m still learning as I go.

[subframe7536]

Oh I found another option that may would work for VSCode: workbench.fontAliasing.

[asifahmad134]

Please look at these screenshots in playground, the first one is using librewolf 141 (firefox), look your font is perfectly rendered

Here, in chrome 138, ubuntu 25.04

As vs code uses electron / chrome, so the issue most probably lies there.

[subframe7536]

I believe this is likely a Chromium-related issue. To be honest, it's beyond my current knowledge, so I'm unable to offer further assistance.