http://bugs.winehq.org/show_bug.cgi?id=23097
--- Comment #19 from Alexey Loukianov mooroon2@mail.ru 2010-06-23 03:43:28 --- (In reply to comment #17)
could someone explain why Xft Xresources takes precedence over fontconfig? IMHO it's not correct behavior, because in my case (Ubuntu 10.04) Xft Xresources always defined by GNOME and there is no way to reset Xft Xresources.
You may read a long comment by me here: http://bugs.winehq.org/show_bug.cgi?id=23114#c4
As for reseting Xresources, try this in terminal (not as root but as currently logged in user): # xrdb -query | grep -vE 'Xft.(anti|hint|rgba)' | xrdb
It should clean up Xft-related Xresources from active instance of Xorg and make Wine use the fontconfig instead.
On my desktop it seems that the behavior for apps other than Wine is as following: 1. Qt3 apps (KDE3) ignore Xft and always use fontconfig. 2. GTK+ apps - here are two cases: 2a) gnome-settings-daemon is not runing: GTK+ apps will not use fonts AA if it is forbidden by Xft OR by fontconfig. 2b) gnome-settings-daemon is active: GTK+ apps will ignore fontconfig/Xft and use the settings from gconf (one that are set in gnome control center). 3. XUL apps (like Firefox) use cairo and here are three cases: 3a) cairo isn't specially patched with "cairo-respect-fontconfig.patch": it would behave just like ordinary GTK+ apps. 3b) cairo was patched with "cairo-respect-fontconfig.patch", no active gnome-settings-daemon: it would behave like Qt3 apps. 3c) cairo was patched with "cairo-respect-fontconfig.patch", there is active gnome-settings-daemon: it would behave like GTK+ apps.
That's it how it is working now on my desktop. As you can see Wine just declares it's own rules of behavior, nothing more.