Newsgroups: comp.lang.postscript
Path: utzoo!utgpu!watserv1!watdragon!dahlia!acli
From: acli@dahlia.uwaterloo.ca (Ambrose)
Subject: Re: reading image data
Message-ID: <1991Mar21.021614.7445@watdragon.waterloo.edu>
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
References: <21257@shlump.nac.dec.com> <12925@adobe.UUCP> <1991Mar20.190919.25355@cbnewsm.att.com>
Distribution: na
Date: Thu, 21 Mar 1991 02:16:14 GMT
Lines: 22

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. According to the green book (PostScript language program design)
[p.145], this will be *extremely* fast if the image can fit into the font
cache.


In article <9103191412.AA27314@stork.cs.rochester.edu> bukys@cs.rochester.edu writes:
>This is a futile plea, I know, but here it is.
>
>	Please stamp out bad PostScript generators.

On a related note, I think the green book is a good start in learning how to
avoid writing bad PostScript generators.


-Ambrose