Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!uc!cs.umn.edu!ux.acs!clarson From: clarson@ux.acs.umn.edu (Chaz Larson) Newsgroups: comp.lang.postscript Subject: Re: PostScript vs TrueType? Message-ID: <2120@ux.acs.umn.edu> Date: 23 Aug 90 17:12:55 GMT References: <9724@goofy.Apple.COM> <438@three.mv.com> Reply-To: clarson@ux.acs.umn.edu (Chaz Larson) Organization: Iron City, USA Lines: 32 In article <438@three.mv.com> cory@three.mv.com (Cory Kempf) writes: >chewy@apple.com (Paul Snively) writes: >>My understanding (I'm not a gnarly printing dude, so don't quote me on >>this!) is that the curve equations will be downloaded to the printer along >>with machine code to do the rendering. So the printer will still do the >>rendering, but will do it as fast as its processor can. > >MACHINE CODE???? This sounds like a solution that will only work with >Apple's Laserwriter (or other 68k based systems). What about all of >the non-Apple postscript devices? What about the non-68k based postscript >engines? I would presume that these non-68K-based PostScript engines have machine code of their own, which would be generated by the drivers which would be written for these printers. This seems like it would be faster than sending PostScript to be interpreted by the printer. In some fictional printer controlled by an 80486, instead of a PostScript program being interpreted by a PostScript interpreter running on the 80486, you'd have curve equations being rendered by 80486 machine code. Seems like a good idea to me, but then I'm not a gnarly printing dude, either. -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ "Does Captain Kirk Exist?" Chinese AI Experts Offer New Evidence." - spew clarson@ux.acs.umn.edu AOL:Crowbone