@g0nz4 Same problem as in Bookworm. I just can't get full #hinting. Look at the #Debian 9 screenshot: the fonts are so crispy I want to chew them. Compare with the grayish blurry fonts in #Mint 22 - with the same settings in Xfce. I've been told that support for hinting is gone in new versions of the font renderer.
I just added code to #Xmoji applying #hinting settings from #fontconfig. I had an immediate reason...
Rasterizing my glyphs with #freetype (for rendering with #XRender), kerning breaks horribly for Microsoft fonts using the "native" truetype hinting. Forcing freetype's autohinter instead, it's (almost) fine (but hinting itself might be slightly lower quality).
Am I doing something wrong, or what the ... is the problem here? Example screenshots using "Segoe UI".
Heard #GNOME are trying to replace #Cantarell with #Inter as their default #UI #typeface?
Would hate to see Cantarell go. It has great #character, and hits some really right spots in terms of #metrics and #hinting on medium #dpi
The venerable #DejaVu and #Liberation families never really looked right for me, (and neither did #Qt's font rendering under 1080p, FWIW) - but as far as #FOSS fonts go, #Cantarell on #720p-#1440p IPS is up there with what #Georgia and #Verdana were on #480p-#600p #CRT
Is TrueType hinting still necessary in 2023? Here’s a possible answer.
So I've heard overlapping components in a hinted TT font is a big No — this comes up a lot in, for example, the `ç`, which usually has a `cedilla` component overlapping the `c` — but I've never seen an issue caused by overlapping components! But maybe I haven't been paying close enough attention.
Does anyone have an example of when overlapping components caused some sort of rendering issue?