You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could be a hinting issue.
The bottom of the g is at -250.
The decender setting is -250.
There is no line gap - it is set to 0.
So the OTF is inside the vertical metrics (and macOS may be hinting it to stay there).
The TTF has the same vertical metrics, but the hinting in the font may be pushing the bottom of the character below what the application is displaying.
Could just be the application rendering is in error (or just dumb - to hint-adjust to clipping).
The TTF hinting is done automatically as the fonts are being generated.
It may be possible to modify the settings for that automatic hinting which may affect this issue.
And the font developer may or may not want to mess around with that.
Manual hinting is very complicated and very time consuming - and not likely to happen.
My guess is if the font developer has the time and the inclination to test automating hinting settings/modifications with these particular applications, and assuming that actually "fixes" this issue, then the earliest this would happen is the next release (whenever that may be).
aren't grid-fitting and hinting the exact same thing? at any rate, macOS does not do it.
also, in my case, it is definitely a clipping issue of line height type, not grid-fitting or hinting issue. If you look at the screen shot, you can see that one of the g's on the second line is not clipped and shows the full form. the clipping is intermittent according to how the line is redrawn as you press enter or backspace.
Activity
kenmcd commentedon Aug 19, 2023
Could be a hinting issue.
The bottom of the
gis at -250.The decender setting is -250.
There is no line gap - it is set to 0.
So the OTF is inside the vertical metrics (and macOS may be hinting it to stay there).
The TTF has the same vertical metrics, but the hinting in the font may be pushing the bottom of the character below what the application is displaying.
Could just be the application rendering is in error (or just dumb - to hint-adjust to clipping).
The TTF hinting is done automatically as the fonts are being generated.
It may be possible to modify the settings for that automatic hinting which may affect this issue.
And the font developer may or may not want to mess around with that.
Manual hinting is very complicated and very time consuming - and not likely to happen.
My guess is if the font developer has the time and the inclination to test automating hinting settings/modifications with these particular applications, and assuming that actually "fixes" this issue, then the earliest this would happen is the next release (whenever that may be).
stlee42 commentedon Aug 20, 2023
actually, on macOS, the fonts are rendered anti-aliased without hinting.
kenmcd commentedon Aug 20, 2023
Bad description on my part.
It is doing its own grid-fitting.
stlee42 commentedon Aug 20, 2023
aren't grid-fitting and hinting the exact same thing? at any rate, macOS does not do it.
also, in my case, it is definitely a clipping issue of line height type, not grid-fitting or hinting issue. If you look at the screen shot, you can see that one of the g's on the second line is not clipped and shows the full form. the clipping is intermittent according to how the line is redrawn as you press enter or backspace.
[-]Clipping on 'g' on macOS Terminal.cpp[/-][+]Clipping on 'g' on macOS Terminal.app[/+]TheKamboy commentedon Aug 21, 2024
I have the same issue, but with the Kitty terminal.
TheKamboy commentedon Aug 21, 2024
fixed the issue by adding this to the config:
modify_font cell_height +2px