From: wolf@sol.cs.uni-sb.de (Wolfgang Huwig) Subject: Re: TeX & doc only work for Root Date: 20 Feb 1993 15:33:18 GMT
In article <1993Feb20.023133.10598@CSD-NewsHost.Stanford.EDU> cwilson@Xenon.Stanford.EDU (Christopher S. Wilson) writes:
> [text about using $HOME/fonts instead of world writeable
> /usr/TeX/lib/tex/fonts deleted]
Another possibility would be a system-wide temporary font directory
with permissions set to 1777. You easily could overlook what's there
and what would be worth being kept.
> Caution: Make sure you change both MakeTeXPK files! SLS includes one
> in /usr/TeX/bin and an identical copy in /usr/TeX/lib/tex (does that
> second one ever really get used?).
It depends only on your PATH variable which gets used. I guess, it
contains /usr/TeX/bin, as the tex and mf programs reside there, too.
> [text about including the temporary font path in $TEXFONTS for every
> user deleted]
> I set up my system this way and it seems to work well enough for xdvi,
> but for some reason dvips seemed to ignore the TEXFONTS variable when
> I tried it. Theoretically, dvips and xdvi are supposed to use the
> same standard algorithm for finding fonts, so this difference
> shouldn't exist -- I'm going to recompile dvips from source and see
> why this doesn't work (of course, if anyone happens to know what's
> going on, I'd welcome suggestions).
You can use different ways of to provide information to dvips where to
search for bitmap fonts (.pk):
1. a compiled in path (normally something like /usr/local/lib/tex/fonts)
2. a path given to the P option in config.ps or $HOME/.dvipsrc
3. a path set via the TEXPKS environment variable (overrides option 3)
4. the path in $TEXFONTS if it can't find a font somewhere else
Don't know why it can't find it in the path in $TEXFONTS, maybe there
are subdirectories and dvips doesn't search them?
Anyway, you don't have to recompile dvips, just use the runtime
options (2 and 3, above).
Greetings,
Wolfgang