Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!ames!apple!agate!shelby!polya!rokicki From: rokicki@polya.Stanford.EDU (Tomas G. Rokicki) Newsgroups: comp.lang.postscript Subject: Re: encapsulated postscript Message-ID: <12917@polya.Stanford.EDU> Date: 2 Dec 89 08:17:14 GMT References: <288@peyote.cactus.org> Organization: Computer Science Department, Stanford University Lines: 18 jcgs@wundt.uk.co.harlqn (John Sturdy) writes: > (4) Some tools produce poor encapsulation of their PS. For example, > one of the well-known packages put some necessary PS code between > %%EndProlog and the first %%Page marker (to cope with this, I had to > treat everything up to the start of the first page as the prologue - I > don't like having to produce kludges like that to get round other > people's kludges, especially when there is a written spec to follow). This is not a kludge. Check out %%BeginSetup/%%EndSetup. This (between the end of the prolog and the beginning of the first page) is where you set document-global parameters, such as orientation or placement, manual feed or number of copies. Then you can gsave showpage grestore to get around showpage's ugly way of resetting everything. Remember, the prolog should not *execute* anything, just define things. The pages should not *define* permanent things.