Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!uw-beaver!mit-eddie!wuarchive!uunet!nds!brian
From: brian@nds.com (Brian Dockter)
Newsgroups: comp.windows.x
Subject: Re: (none)
Message-ID: <1991Feb21.185841.1899@nds.com>
Date: 21 Feb 91 18:58:41 GMT
References: <9102202223.AA01931@hydro.Saic.COM>
Reply-To: brian@nds.UUCP (Brian Dockter)
Organization: Northwest Digital Systems
Lines: 31

In article <9102202223.AA01931@hydro.Saic.COM>
larry@hydro.saic.COM (Larry Clark) writes:
>I'm having trouble using xset to set my font path.
>Can anyone out there help me?

I have noticed several people having problems lately setting their
font paths.  Here is a little checklist which should help:

    1) Be sure to use absolute font paths (xset fp=./fontdir won't usually
       work).

    2) Make sure the target directory is readable by everyone.

    3) Verify that the files 'fonts.dir' and 'fonts.alias' exist in the
       target directory and are readable by everyone.

    4) If you are accessing fonts using tftp, make sure you either aren't
       using secure mode, or that the target directory is included as one
       of the secure directories when the tftp daemon is started
       (i.e.  tftpd -s /fontdir).

These should solve some of the most obvious problems.  All that most servers
do when you set a new fontpath is go out the each of the directories in the
font path, read the files 'fonts.dir' and 'fonts.alias', and add the contents
of these files to its internal font list.  Any error conditions should be
associated with this process.

-- 
Brian Dockter                    | Northwest Digital Systems
UUCP: uunet!nds!brian            | Voice: 206-524-0014
Internet: brian@nds.com          | FAX: 206-524-0018