http://bugs.winehq.org/show_bug.cgi?id=23097
--- Comment #16 from Alexey Loukianov mooroon2@mail.ru 2010-06-23 00:33:44 --- I had spent some time recompiling wine-1.2-rc4 with and without fontconfig support. Here are the results:
1. If wine was compiled without fontconfig then the AA will be active if the Xft Xresources are set. If there are no Xft Xresources set then it would be the registry values who control the fonts AA.
2. If wine was compiled with fontconfig then the registry settings seem to be completely ignored. In case there are Xft Xresources defined then they would take precedence, in other cases fontconfig determines would be the fonts AA active or not. There's an odd behavior with it as if fontconfig returned that antialias=false and rgba=rgb then wine still would do ClearType-like font AA for this font. It is inconsistent behavior with the rest of the system as setting antialias=false would turn off any of subpixel AA methods as well. This might be treated as a reason to reopen bug #17148 but I don't this that the issue is major enough to care.
As for this bug I think that it would be reasonable to close it WONTFIX INCORRECT and to document the details of "registry settings"<=>"fontconfig"<=>"Xft Xresources"<=>"Wine" relations in docs/wiki.