[17226] in Athena Bugs
Re: [Siwaphong Boonsalee] Thai Fonts
daemon@ATHENA.MIT.EDU (t. belton)
Thu Sep 30 13:19:02 1999
Date: Thu, 30 Sep 1999 13:18:50 -0400 (EDT)
From: "t. belton" <tbelton@MIT.EDU>
To: Dan Winship <danw@MIT.EDU>
Cc: boonsale@MIT.EDU, bug-infoagents@MIT.EDU
In-Reply-To: <199909292110.RAA152632@antharia.mit.edu>
Message-Id: <Pine.GSO.3.96L.990930131138.15292B-100000@iphigenia.mit.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Netscape doesn't use a font path of its own. It uses the one that 'xset'
reports. Here's the only germane part of the wrapper script:
---
if xset -q | grep -s /infoagents/ > /dev/null; then
: font path is ok already
else
fontdir=`cd /mit/infoagents/arch/share/lib/X11/.big_endian; pwd`/
xset fp+ ${fontdir}
xset fp rehash
fi
---
The problem is that I just tried 'xset' and it told me that
/usr/athena/lib/X11/fonts/intlfonts is already IN the font path, i.e.
Netscape should see those fonts without needing more help from me.
Now ... I need a Thai page, one which is known to have Thai characters, to
test this.
It may be that it works on my system, and the user's system has a
different font path for some reason. Or it may be that there are other
problems - for example, Netscape does not appear to have a Thai "Character
Set" setting. If that turns out to be the issue, we can't fix it.
-Todd
