Xref: utzoo comp.fonts:2237 comp.text.tex:6650
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!manuel!anucsd!csis!ken
From: ken@csis.dit.csiro.au (Ken Yap)
Newsgroups: comp.fonts,comp.text.tex
Subject: Re: Request help with mf, gftopk
Keywords: resolution
Message-ID: <1991Apr7.231813.10310@csis.dit.csiro.au>
Date: 7 Apr 91 23:18:13 GMT
References: <1991Mar29.024139.23256@zorch.SF-Bay.ORG> <1991Apr6.054156.19982@zorch.SF-Bay.ORG>
Organization: CSIRO Division of Information Technology
Lines: 15

>Last things first; creating a whole rasterized metafont in a nice
>selection of sizes can take literal days; I ran mine overnight to get
>just a few sets of fonts built. You _really_, _really_ don't won't this
>overhead in your printing loop, which is why TeX/Metafont users have
>megabytes of already rasterized fonts online and ready to use. Metafont
>makes lovely fonts, but it makes a snail look turbocharged.

Yes, running MF to make fonts is slow, especially if you don't have a
workstation, but many DVI to foo converters have scripts that will run
MF on the fly and *thereafter the filter uses the newly made pk file*.
So if the users are happy to wait a little while on their first print
run, you're ok. Otherwise, the installer should run a bunch of
documents through the system (you don't actually have to print the
documents, just redirect the PDL output to /dev/null) to make the most
commonly occuring fonts.