http://bugs.winehq.org/show_bug.cgi?id=23006
Sergiy Zuban s.zuban@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #13 from Sergiy Zuban s.zuban@gmail.com 2010-06-14 05:51:24 --- after deeper investigation I made conclusion that gnome-settings-daemon adds some Xft resources on start and wine treat those settings as higher priority (compared to fontconfig setttings). Here is what I found in gconf-editor, key /desktop/gnome/font_rendering/antialiasing:
The type of antialiasing to use when rendering fonts. Possible values are: "none" for no antialiasing, "grayscale" for standard grayscale antialiasing, and "rgba" for subpixel antialiasing (LCD screens only).
There is no way to delete this option, no way to avoid setting Xft resources. Thus all fontconfig settings simply ignored. IT'S NOT CORRECT BEHAVIOR.
Let me give you several examples where fontconfig settings has higher priority on Xft resources:
* GNOME/KDE allows to disable antialiasing on fontconfig level even if it's allowed globally.
* Mozilla apps (Firefox, Thunderbird) uses fontconfig's smoothing settings even if smoothing disabled globally by Xft resources.
* Qt apps
I'm not familiar with KDE, but I assume there is some kind of gnome-settings-daemon that initializes Xft resources on startup, because this issue occurs not only under GNOME, but under KDE as well.