🚀 go-pugleaf

In article <1992Sep1.115007.5434@uniwa.uwa.edu.au> medrh@uniwa.uwa.edu.au (Richard Hockey) writes:

OK, assuming you didn't have the fonts already, creating the fonts was the
Right Thing to do.

I don't know what kind of machine you're running, but what dvips has done
for you is creating a program that can generate the fonts for you provided
that you use emTeX on an MS-DOS compatible computer. Since you already
have created the fonts, you don't need this program that dvips has created
for you.

Let's drop the technicalities - dvips needs _both_ tfm _and_ pk files, I'm
not going to tell you why since you don't want to be an expert. Suffice to
say that dvips assumes that you _may_ be using an 8 character + dot +
three characters file name operating system. 

So there's a way to specify the path to the pk files, in which you can
substitute reserved characters as variables. A pk file is usually named
after these conventions:

	< name > dot <resolution > pk, forinstance

	cmr10.300pk: 

		< name > 	= cmr10	= %f
		< resolution> 	= 300	= %d
		pk		= pk	= %p


(this is slightly oversimplified, still, you get the general idea)

You specify the path in dvips' config.ps file.  If you told dvips at
compile time where to find config.ps, you don't need to recompile. If
cmr10.300pk is placed in

	/local/lib/tex/fonts/pk/cmr10.300pk,

in config.ps you say

	P /local/lib/tex/fonts/pk/%f.%d%p

on an MS-DOS system you might instead place cmr10.300pk in 

	c:\texfonts\pk\dpi300\cmr10.pk

in which case you'd tell config.ps that

	P c:\texfonts\pk\dpi%d\%f.%p


--
       Rolf Lindgren           |       "The opinions expressed above are
       616 Bjerke Studentheim  |        not necessarily those of anyone"
       N-0589 OSLO 5           |           rolfl.lindgren@usit.uio.no