Xref: utzoo comp.fonts:360 comp.text:2666 comp.lang.postscript:1075
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ukma!sean
From: sean@ms.uky.edu (Sean Casey)
Newsgroups: comp.fonts,comp.text,comp.lang.postscript
Subject: Re: METAFONT & PostScript
Message-ID: <10417@s.ms.uky.edu>
Date: 22 Oct 88 23:31:59 GMT
References: <902@cps3xx.UUCP>
Reply-To: sean@ms.uky.edu (Sean Casey)
Organization: The Leaning Tower of Patterson Office @ The Univ. of KY
Lines: 26

In article <902@cps3xx.UUCP> smithda@cpsvax.cps.msu.edu (Daniel Smith) writes:
[A good article comparing METAFONT and Postscript]

I'm no great fan of either, but I have to point out that METAFONT does a lot
more to generate fonts of a certain size than Postscript does. You can always
send font outlines to Postscript for scaling, but the results aren't going to
look as good as if you let METAFONT do it.

I'd like to see the functionality of both combined, but I'm not sure how it
could be done. I don't like the idea of storing bitmaps on the host system
because (1) it uses a lot of disk space and (2) someone always seems to want
something in a size that isn't there.

If you generate stuff on the fly, you either do it really slow and good with
METAFONT, or fast but not quite so good with Postscript.

Perhaps this will all be a moot point in the future, when output device
resolution will be so high that finicky differences in rasterization won't
be visible.

Sean
-- 
***  Sean Casey                        sean@ms.uky.edu,  sean@ukma.bitnet
***  The Hacker from Spaaaaaaaaace.    {backbone|rutgers|uunet}!ukma!sean
***  U of K, Lexington Kentucky, USA  ..where Christian movies are censored.
***  ``The World... she's a flat! She's a round! Flat! Round! Flat! Round!''