03-01-2024, 02:04 PM
(This post was last modified: 03-01-2024, 02:08 PM by a740g.
Edit Reason: Fix typos
)
@bplus @TerryRitchie I think what you are seeing is the change in the subpixel hinting behavior in newer versions of FreeType. Technically this would mean that any application that uses the current version of FreeType will have the same behavior.
That said, I think there is a way to tell FreeType to select a different hinting behavior with FT_LOAD_TARGET_xxx
https://freetype.org/freetype2/docs/hint...nting.html
https://freetype.org/freetype2/docs/hint...neral.html
The good part about all this is that _LOADFONT takes optional comma separated parameters:
handle& = _LOADFONT(fontFileName$, size&[, "comma_separated_parameters"][, fontIndex&])
So, we could easily introduce some new options for _LOADFONT that allows us to pick the hinting type we want.
We can perhaps use the older hinting behavior by default and let users use the newer behavior or FreeType default behavior if they want.
Interesting stuff really. I'll deep drive into this when I get some time.
That said, I think there is a way to tell FreeType to select a different hinting behavior with FT_LOAD_TARGET_xxx
https://freetype.org/freetype2/docs/hint...nting.html
https://freetype.org/freetype2/docs/hint...neral.html
The good part about all this is that _LOADFONT takes optional comma separated parameters:
handle& = _LOADFONT(fontFileName$, size&[, "comma_separated_parameters"][, fontIndex&])
So, we could easily introduce some new options for _LOADFONT that allows us to pick the hinting type we want.
We can perhaps use the older hinting behavior by default and let users use the newer behavior or FreeType default behavior if they want.
Interesting stuff really. I'll deep drive into this when I get some time.