🚀 go-pugleaf

In article <1992Dec21.171203.29295@cs.brown.edu> jgm@cs.brown.edu (Jonathan Monsarrat) writes:
>
>>Has anyone ever done a program (be it postscript or a tool creating
>>postscript), that can draw on an (infinitely large) virtual page, then
>>break it down into an acceptable size (say the printer's default),
>
>Here's a hack that may be of use to you. I've used it to create
>posters 18 feet high! :)
>
>Right now it's set to print "normal size" -- just one page.
>
>-Jon
>
	(Another of Jon's Obfuscated PostScript figures deleted) 8-{)


Has anybody been able to answer this question in general?

I do not believe this can be done in most PostScript interpreters for an
ARBITRARY image. 

The basic premise of the example in the Blue Book is to build a procedure
that captures the page's imaging code, then repetitively translate
the origin around and re-image the entire picture but only printing
a single page-worth of it.

Obviously this works. That is until the PostScript code which represents
the image gets so large that it overflows the stack, or some other 
implementation limit is reached. Then it DOESN'T work.

My own experience is exactly as described. I was trying to tile a picture
generated by Cadre TeamWork but the image was bigger than the stack could
hold to create the procedure. I had to resort to a program to read the
PostScript code and break it up into many (50-100) smaller procedures, and 
then re-image for each translate position. 

Yes, this worked. But it took explicit knowledge of the PS emitted by TeamWork.
Not applicable to an ARBITRARY piece of PS code.

Comments???

Regards,

Bill Lee