[comp.windows.x] Unable to add a FontPath

rlk@THINK.COM (Robert L. Krawitz) (11/23/88)

   Date: 23 Nov 88 01:39:07 GMT
   From: sunybcs!sbcs!yong@rutgers.edu  (Yongdeng Chen)

[...adding fonts to path doesn't work...]

I've had the same problem on a Sun 3/140 running SunOS 3.5.  I'm using
xset to do this.

harvard >>>>>>  |		Robert Krawitz <rlk@think.com>
bloom-beacon >  |think!rlk
topaz >>>>>>>>  .		rlk@a.HASA.disorg

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (11/23/88)

My guess is that both of you are using R3 (it really does
help to give this information) and are trying to specify a directory
that is missing both a fonts.dir and a fonts.alias file (see the
mkfontdir man page).  The server will just (silently) ignore your
request in that case.  (The server probably should complain, granted.)
If the directory in question really has one of those files (and the
file is well-formed), then send a more complete description of the
environment and the sequence of steps in a bug report to xbugs.

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (11/25/88)

    But mkfontdir creates fonts.dir file without removing the "." from
    the file names.

Right, there is a bug in mkfontdir that causes this when using "old"
fonts that don't have a "FONT" property.  We'll probably post a fix
at some point, but the correct thing to do is fix your fonts to have
a correct FONT property.