http://bugs.winehq.org/show_bug.cgi?id=16745
--- Comment #11 from Dmitry Timoshkov dmitry@codeweavers.com 2009-04-16 22:00:57 --- (In reply to comment #10)
Perhaps the patch isn't correct, but I'd like to confirm this as a problem. There's also a launchpad bug: https://bugs.launchpad.net/wine/+bug/318478 Basically, a user goes into their system, configures it to use font hinting a certain way, then opens up a program in Wine and finds that it isn't working.
In order to enable hinting in Freetype it's necessary to recompile it. Freetype doesn't have a run-time option to turn on/off hinting. And no, bytecode interpreter and autohinter are different things in Freetype with very different results.
How does Windows tell apps to use different font settings? I'm pretty sure Windows has a centralized control panel for this similar to the one for fonts already on the system.
It's apps who tell what font attributes they would like to have.
http://www.winehq.org/pipermail/wine-devel/2009-March/074261.html So it's OK to query the global antialiasing setting (on or off).