Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!natinst!rpp386!woody
From: woody@rpp386.cactus.org (Woodrow Baker)
Newsgroups: comp.lang.postscript
Subject: Re: Bitmap of PostScript code..
Summary: hmmm
Message-ID: <18020@rpp386.cactus.org>
Date: 23 Feb 90 18:57:15 GMT
References: <1990Feb14.041704.14844@athena.mit.edu> <2761@bacchus.dec.com> <1990Feb22.155435.1578@uwslh.slh.wisc.edu>
Organization: River Parishes Programming, Plano, TX
Lines: 24

In article <1990Feb22.155435.1578@uwslh.slh.wisc.edu>, lishka@uwslh.slh.wisc.edu (Chris Lishka (controlled by cockatiels) ) writes:
> glenn@heaven.woodside.ca.us (Glenn Reid) writes:
> 
> Although this may deviate from the original thread slightly, I think
> that a bitmap *is* a useful object to have.  In fact, a postscript
> interpreter that is capable of producing an *arbitrary* size bitmap
> would be a very useful tool, because one could use it to create
> bitmaps of different sizes to send to many different types of printers
> (or to computer screens).  Bitmaps are a useful way of moving from
> postscript code to a non-postscript output device, because many output
> devices use a bitmap-like "model" for printing. 
> 
As I said before the bit map is the rosetta stone of graphics world.  They are
the most portable form of graphics file.  They are easy to convert
from one representation to another. 

> On the other hand, I can see where trying to get the 300dpi bitmap
> produced by a postscript printer (such as a LaserWriter) is sort of

It would certainly be large, but suppose that you could just grab
Specific regins?....

Cheers
Woody