🚀 go-pugleaf

In article <1992Sep3.192032.8916@cv.ruu.nl>, koen@cv.ruu.nl (Koen Vincken) writes:
> In <2SEP92142336@thisbe.ece.arizona.edu> chd@thisbe.ece.arizona.edu (Chris De Young) writes:
> 
>>I'm having a problem using DVIJET with TeX Version 3.1 [PD VMS 3.3/DECUS]....
>>A few questions:
[stuff deleted]
>>%Font file [cmbx10 [mag 868]] could not be opened; 0 font files are open
>>Proceeding with zero size characters for this font
>>Current TeX page counters: [0]

> I had a similar problem. If you look carefully in one of the readme documents
> (or one of the text-files, I believe) you can see that you have to set an
> environment variable. Out of my head, I think it was TEXFONTS, or
> something like that. Set it to your local tex-font directory where
> dvijet looks for fonts (for instance, TEXFONTS=/usr/local/lib/tex/fonts/pk/)
> If you don't have such font-directories, get them first from colleagues,
> ftp-sites, whatever.

As you're using VMS, it's more likely to be the font file organisation.
You can do it one of two ways, either one huge directory with all files
at all \magsteps, names, eg, cmr10.300pk, cmr10.329pk etc, OR
lots of different directories, each named with the numeric dot-density
[.300], [.329] etc, and the files in them named like the PC ones, cmr10.pk
etc. If you pick the second method, your tex_pk definition must end
with a period before the closing "]", which implies the fonts are in 
separate subdirectories, eg def/nolog tex_pk dua2:[tex.pkfonts.]
Omitting the trailing period implies the first type of organisation.

///Peter