Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!wuarchive!mailrus!iuvax!rutgers!rochester!ken
From: ken@cs.rochester.edu (Ken Yap)
Newsgroups: comp.text
Subject: Re: TeX gf,pk,pxl files
Keywords: TeX,pk,pxl,gf,metafont
Message-ID: <1989Sep23.154108.13738@cs.rochester.edu>
Date: 23 Sep 89 15:41:08 GMT
References: <251AB757.452@marob.masa.com>
Reply-To: ken@cs.rochester.edu
Organization: U of Rochester, CS Dept, Rochester, NY 14627, (716) 275-1448
Lines: 14

|Considering the fact that many device drivers (dvi2ps, dvijet, dvi2ln3,
|etc.) look for different types of pixel files (gf,pk,pxl), how is one
|to avoid keeping a full complement of pixel files for all interesting
|sizes, three times? Is there a set of drivers (for postscript and

Patronize only the drivers that use pk files.

|laserjet, at least) that use the same type of pixel files? Wouldn't it
|be reasonable if everyone just used gf files, to avoid confusion?

No. Pxl can be junked. Gf has to be retained because MF generates that
and also it is easy to generate. Pk is the most compact but is
complicated to decode, but the reading routines have to be written only
once (borrow code from MC-TeX, or the Utah drivers).