Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!snorkelwacker.mit.edu!stanford.edu!lucid.com!campeau!jwz From: jwz@lucid.com (Jamie Zawinski) Newsgroups: comp.lang.postscript Subject: Re: reading image data Message-ID: Date: 22 Mar 91 03:29:43 GMT References: <21257@shlump.nac.dec.com> <12925@adobe.UUCP> <1991Mar20.190919.25355@cbnewsm.att.com> <1991Mar21.021614.7445@watdragon.waterloo.edu> Sender: usenet@lucid.com Distribution: na Organization: Lucid, Inc., Menlo Park, CA Lines: 20 In-Reply-To: acli@dahlia.uwaterloo.ca's message of 21 Mar 91 02:16:14 GMT In article <1991Mar21.021614.7445@watdragon.waterloo.edu> acli@dahlia.uwaterloo.ca (Ambrose) wrote: > In article <1991Mar20.190919.25355@cbnewsm.att.com> kalin@cbnewsm.att.com > (andrew.j.kalinowitsch) writes: >> >>I've got a file that makes the printer execute all kinds of funky >>arctangents and curvetos to produce the exact same image over and over >>again -- I'd like to get the image in a bitmap without scanning it >>to optimize execution time/throughput. > > The best way to do it is to create a type 3 font and let the font machinery > do the job. Once PostScript Level II starts actually showing up in implementations, I think it will be pretty simple to use the "forms" facility to do this. As I understand it, this is an interface to a font-cache-like mechanism without having to go through all the hairy goop necessary to define a font. Until then, I think defining a font is probably the best way. -- Jamie