Gfx:Win and Gfx:Gtk2:Xft support font.name-list.<generic>.<langGroup> in addition to font.name.<generic>.<langGroup>. It seems like Gfx:Thebes doesn't. font.name-list is useful in allowing users to set up a customized font-set (a concept both used in old Xlib and Win32 throughout 1990's). Some non-European users don't like rather ugly Latin glyphs in fonts for their own languages/scripts. What they do is set font.name.foo.<lang> to a nice Western European font (e.g. Bitstream Vera Sans|Serif|Monospace on Linux) and list fonts for their own scripts/languages in font.name-list.foo.<lang>. That way, Latin letters are rendered with a nice Western European font while other characters are rendered with one of fonts enumerated in font.name-list. BTW, on Linux and Mac OS X where no 'monospace' font is available for CJK, this is more than 'asthetic'. See bug 327946 and bug 202901 A little off-topic: I'm wondering what font search and fallback tactics are used in Cairo/Gfx:Thebes. A lot of refinements have been made over years for Gfx:Win and I guess quite a lot of tinkering can be saved if Gfx:win is referred to.

It's bug 202921 (not bug 202901)

nsICommandLineService interface needs to be fixed first.

it is now supported on windows.

fixed by bug 339513.

.

-> FIXED # sorry for the spam.