🚀 go-pugleaf

>  In article <1992Oct2.114504.26092@dsg.cs.tcd.ie> cjmchale@dsg.cs.tcd.ie (Ciaran McHale) writes:
> 
> 	  In <RMF.92Oct1203636@chopin.cs.columbia.edu> rmf@chopin.cs.columbia.edu
> 	  (Robert M. Fuhrer) writes:
> 
> 	  >[wants to be able to determine how big the output page is so PS
> 	  >programs can scale themselves to fill it]
> 
> 	  The default clipping path is the imagable area of the output page.
> 	  Simply call "clippath flattenpath pathbbox".
> 
>  Try to avoid doing such things UNLESS you are sure that noone will EVER try
>  and use this as an inserted figure.  If your graphics is included as an
>  EPS file somewhere this trick will kill any positioning and scaling done by
>  the enclosing PS code.  Most annoying that some reall applications produce
>  code just like this!  In defense, the application importing the PS has to
>  play games like changing the clipping path...

The idea was to be able to write postscript code that would "work" regardless
of the output medium. Therefore, I needed to be sure that such code could be
reasonably inserted (i.e., scaled and translated) in an output page. So the
included code would not have the "clippath flattenpath pathbbox", the including
code would.
--

-- Bob