Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!decwrl!shelby!polya!rokicki
From: rokicki@polya.Stanford.EDU (Tomas G. Rokicki)
Newsgroups: comp.lang.postscript
Subject: Re: PostScript beginner needs help with "image" command
Keywords: image bitmap postscript
Message-ID: <12886@polya.Stanford.EDU>
Date: 27 Nov 89 05:43:00 GMT
References: <9790@saturn.ucsc.edu> <128392@sun.Eng.Sun.COM>
Distribution: na
Organization: Computer Science Department, Stanford University
Lines: 22

> The basic problem with this approach is that the 
> 	    {< . . . >}
> code sequence is placing a hexadecimal string on the stack.
> Strings are limited in length to 65535 bytes (documented on
> page 260 of my Red Book).  When you have a 256 x 256 x 4
> bit image, this translates into 32768 bytes of data, and
> when you double that (two hex characters per byte) you have

Just a minor nit.  Actually, the <...> syntax requires 2n+2 bytes
to represent a string of length n, but that string requires only
n bytes (plus 8 or so overhead) inside of the printer.  So you
can have a string of length 65535 represented with 131072 input
bytes with no troubles.

In other words, the string

   <0001020304050607>

requires only eight bytes (plus some minor overhead) inside the
printer . . .

-tom