http://bugs.winehq.org/show_bug.cgi?id=16745
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2009-02-27 02:59:06 --- (In reply to comment #7)
It shouldn't break anything, as least as far as I know. My understanding is that Windows knows nothing about the hinting, as that relates to freetype. I also made sure not to break existing substitution code in Wine.... if someone substitues Arial for Verdana using the Wine substitutions, and has fontconfig replaces Verdana with DejaVu, then the patch tells Wine "Here is Verdana", and proceeds to load and display DejaVu. So, I don't think it will break anything. Besides, it's not set up as a default... if someone wants to use it they enable it with a registry setting.
What happens if an app requests GGO_UNHINTED,NONANTIALIASED_QUALITY, ANTIALIASED_QUALITY,CLEARTYPE_QUALITY and similar flags? Freetype's autohinting is far not the same as the bytecode interpreted glyphs, and Wine has enough problems due to the missing bytecode interpreter already. Forcing anything the Linux distro developers think or a user sets on their own is going to lead to all kind of hardly to debug/weird font rendering bugs.