On Thursday 22 November 2007, Stefan Dengscherz wrote:
> I've already played around with the font settings in about:config,
> but they don't seem to affect the UI, just the html rendering engine.
>

Yes. I'm fairly sure the about:config options *only* affect the HTML 
rendering and not the UI.

> I'll take a look ath the UserChrome.css options maybe there's some
> switch to adjust.

You can change the UI fonts with UserChrome.css -It's the only way that 
I know how to do it. 

Since you already do have anti-aliasing working, I figured I didn't need 
to mention it but what the heck... You should have the following 
defined and exported for anti-aliasing to work with gtk and qt.

GDK_USE_XFT=1
export GDK_USE_XFT
QT_XFT=1
export QT_XFT

Some people like to adjust specific elements of the firefox UI in 
different ways (as noted in the URL I previously posted by the element 
names) but personally, I just do a global change on everything in the 
UI with the following lines in my UserChrome.css file.

* {
  font-family: Terminus !important;
  font-size: 16pt !important;
  font-weight:600 !important;
}

Yep, it forces the above font on the entire UI. If your system/user font 
configuration is doing anti-aliasing on the specified font, then it is 
anti-aliased in the firefox UI (I don't use thunderbird).

Firefox, (and I suspect thunderbird) control its UI via XUL, so by 
default they ignore many/most settings in of your gtkrc-2.0 file.

http://www.xulplanet.com/tutorials/xultu/
http://www.xulplanet.com/references/elemref/ref_StyleProperties.html

Sadly, UserChrome is a work in progress, constantly changing and the 
docs *always* suck.
http://kb.mozillazine.org/Chrome_element_names_and_IDs
http://kb.mozillazine.org/UserChrome.css

There are settings within your gtkrc-2.0 file that firefox will use, in 
particular, settings for scroll bars and if you use them, 
effect 'engines' like xfce.

XUL and UserChrome can do some impressive things once you learn them, 
unfortunately, it means you'll be doing a lot of trial and error 
testing since the docs are just plain missing in most cases.

This is what I did...
http://www.designtools.org/files/firefox.png

kind regards,
jcr

Reply via email to