On Wed, 31 Dec 2003 [EMAIL PROTECTED] wrote: > Good. So no need to worry about the html page.
Actually, there is. By 'sun_devanagair_font', I didn't mean that you use that verbatim but that you have to replace that name by the actual name of Sun's font. Besides, it's always a good practice to put one of five CSS generic font families (serif, sans-serif, etc) at the end of your font list as I wrote. > Remains to worry about Mozilla and/or the X server and/or fontconfig. Xserver does only little part in the equation as long as it supports Render extension. Did you put your Sun's Saraswati fonts (two of them) in one of directories looked into by fontconfig? > things work. Am quite prepared to use cryptic names like > -altsys-saraswati5-medium-r-normal--0-0-0-0-p-0-iso10646-1 Well, with that XLFD name, Mozilla (X11core build) wouldn't recognize it as a SunIndic font so that Devanagari wouldn't get rendered as it should. You have to alias it so that the last two field of XLFD is sun.unicode.india-0 (or something like that) by editing fonts.alias file and some other chores involved in the X11 font installation. That's one of reasons I told you to use an Xft build. > but you seem to imply that life is simpler today. Not yet for me. If you yearn for the old days of XLFD, X11core fonts and mkfontdir/mkfontscale/xset fp/chkfont/xfs/fonts.dir/fonts.alias/ fonts.scale etc, you can stay there by continuing to use a non-Xft (X11core) build of Mozilla. However, for the increasing number of programs in modern Linux distributions, you won't have a choice soon when gtk2 stops honoring GDK_USE_XFT=0. > [Answering my own question from yesterday night - the new Mozilla build > shows as possible font choices things in the output of fc-list on the > client.] Where have you been during the client-side font revolution? On Mars ;-) ? -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
