Comment 7 for bug 937200

Okay - I played a little bit around and got this results:

The only thing that is relevant for this problem seems to be the setting "font-name". The other font settings don't matter.

That can be changed with:
gsettings set org.gnome.desktop.interface font-name 'Droid Sans 10'

Now it should with *non-default* Look-and-Feels (e.g. Nimbus, GTK).

Details:

I am setting my font settings using this script:
--------------------
gsettings set org.gnome.desktop.interface document-font-name 'Droid Sans 10'
gsettings set org.gnome.desktop.interface font-name 'Droid Sans 10'
gsettings set org.gnome.desktop.interface monospace-font-name 'ProFontWindows 8'
gsettings set org.gnome.nautilus.desktop font 'Droid Sans 10'
gconftool --set /apps/metacity/general/titlebar_font 'Droid Sans Bold 10' --type STRING
--------------------

Reading the values using
--------------------
echo "Document Font: "
gsettings get org.gnome.desktop.interface document-font-name
echo "Font: "
gsettings get org.gnome.desktop.interface font-name

echo "Monospaced Font: "
gsettings get org.gnome.desktop.interface monospace-font-name

echo "Nautilus Desktop Font: "
gsettings get org.gnome.nautilus.desktop font

echo "Titlebar Font: "
gconftool --get /apps/metacity/general/titlebar_font
--------------------

I got the following:
With changed fonts, it looks ok, when:
- Nimbus or GTK LnF is used
It *does* work with the default LnF.

The AA settings just do what one expects: The change the AA settings...