http://bugs.winehq.org/show_bug.cgi?id=23114
--- Comment #9 from Alexey Loukianov mooroon2@mail.ru 2010-06-22 04:38:54 --- (In reply to comment #7)
See the fontconfig documentation/source.
Good catch, thanks. Will take a look into fc source, hope the relations with the Xft resources would become more clear for me then.
If Wine behaviour doesn't match what other Linux applications do that's another problem, and it's the subject of this bug report.
As I know a bunch of cases when with some set of the fc/Xresources settings the font AA behavior would be different fot GTK+, XUL and Qt3 apps I still don't think that it should be considered the bug. It is perfectly enough for wine to have well-determined and documented behavior of how to configure fonts AA. You have posted that for now the "system defaults" are configured by fontconfig so the only non-documented question left is what is the current purpose of "FontSmoothing"/"FontSmoothingType" registry values. Wine's approach that "fonts anti-aliasing system desktop defaults" are configured with fontconfig is good enough for me to be content with it.
The fact that there are some other apps violating this "configuration rule" is not a wine's fault thus is not a wine bug.