Windows rendering (ttf 1.400)

[eldair]

After testing the latest ttf version on windows, this is still the same

14px (!= is the only issue unless it should be small like this):

13px:

12px:

15px:

[okonet]

Is this still an issue? I see your comment in #19 and not sure now if we should be investigating it still.

[eldair]

Hi, yeah, it is still the same, on version 1.5

[bebraw]

@eldair Which resolution are you using on your display? That's a good extra piece of information to have.

[eldair]

Same thing on both 1920x1080 (24") and 2560x1440 (27")

[bebraw]

Ok, thanks!

Is it the same regardless of the editor (VS Code and others)?

[eldair]

Sublime is the same but for different font size (their 10 is the same as vscode 14)

These screenshots are from the larger display (1440p)
If you need more font sizes let me know

[bebraw]

Can you check with 1.6 as there were ttf rendering improvements there? You can use the original download link.

[eldair]

Hello,

13px and 14px are perfect on both 1440p (27") and 1080p (23")

12px

11px and below have an issue with .= only

15px

16px and above is same as 11 and below .=

[bebraw]

@MarcusSterz Can you comment when you have time? TTF looks better now and I guess the question is, can the rest be improved?

I know there are inherent limitations in font rendering so the problem often is that you cannot make each size perfect especially on lower resolutions. Based on that it's possible we won't be able to make it perfect on each but let's see what Marcus has to say.

[MarcusSterz]

I will pass the torch to @mekkablue – Is there a final answer to this?

[mekkablue]

Will employ ‘natural’ rather than ‘quantized’ gridfitting, which will deliver a smoother scaling across sizes at the cost of a bit more antialiasing (i.e., a bit more fuzziness). This should be a slight improvement.

However it is not mathematically possible to always gridfit three equally distant stems at equal pixel distances in all pixel sizes, and line them up with the rest of the font at the same time. There will have to be some compromise in some pixel sizes.

[bebraw]

The fix has been included to the newly published 1.700.