Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!uc!cs.umn.edu!ux.acs!vx.acs.umn.edu!dhoyt
From: dhoyt@vx.acs.umn.edu
Newsgroups: comp.lang.postscript
Subject: Re: PostScript vs TrueType?
Message-ID: <2128@ux.acs.umn.edu>
Date: 24 Aug 90 17:14:28 GMT
Sender: news@ux.acs.umn.edu
Organization: University of Minnesota, Academic Computing Services
Lines: 23

In article <1331.26d577e2@waikato.ac.nz>,
> ccc_ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) writes...
>>In <1990Aug24.012301.23588@motcad.portal.com>,
>> jtc@motcad.portal.com (J.T. Conklin)
>>says "The whole point of PostScript is that there should be only one print
>>driver for all PostScript devices, regardless of manufacture or
>>implementation."
> 
>I agree this was one of the original aims. So you tell me: has PostScript
>lived up to its design goals?

  Yes.  I can create a postscript file in Pagemaker, proof it on a Laserwriter
then send the same file to a printer to print on a Linotronic or Agfa
typesetter with only a small chance of problems.  I don't care what their
rasteriser is and they don't care about mine.  Downloading 68000 code seems
very stupid to me.

  But I don't really care what TrueType does.  I'll never use it.  I've got my
fonts, I've got my ATM, I've got real Postscript printers in house and at the
printers.  The pros all use postscript.  Where does that leave Royal &
TrueType?

david | dhoyt@vx.acs.umn.edu | dhoyt@umnacvx.bitnet