Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.postscript > #3618

Re: convert this PostScript file to one which works with \includegraphics

From ken <ken@spamcop.net>
Newsgroups comp.lang.postscript, comp.text.tex
Subject Re: convert this PostScript file to one which works with \includegraphics
Date 2021-01-27 17:12 +0000
Message-ID <MPG.3a7baf409d5043ef9898c3@usenet.plus.net> (permalink)
References <rupulf$11ao$1@gioia.aioe.org> <MPG.3a7b2d8488376b989898c2@usenet.plus.net> <rur9m2$jlb$1@gioia.aioe.org>

Cross-posted to 2 groups.

Show all headers | View raw


In article <rur9m2$jlb$1@gioia.aioe.org>, 
helbig@asclothestro.multivax.de says...

> I admit that I don't fully understand when showpage is needed and when 
> not.  Certainly \includegraphics does display some PostScript files with 
> the showpage command.

showpage 'shows' the page, transfers the accumulated marking operations 
to the output device and erases the canvas ready for the next page.

It is possible in PostScript to define a 'showpage' procedure (and any 
other operator) which will be used instead of the built-in operator, if 
the lookup is managed properly.

/showpage {} bind def

defines a function called showpage in the current dictionary which does 
nothing. As long as this dictionary is ahead of systemdict on the 
dictionary stack, then that's the definition of showpage which will be 
used. It's not an uncommon approach.

In your case, simply remove the line with 'showpage' in it from the 
output PostScript file. It will still be a crappy level 1 PostScript 
program, but it at least won't reset the page for you.

Provided you are placing it within another PostScript program (which is 
what EPS files are for) then the enclosing program's showpage will show 
the accumulated operations.

			Ken

Back to comp.lang.postscript | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

convert this PostScript file to one which works with \includegraphics helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2021-01-26 20:39 +0000
  Re: convert this PostScript file to one which works with \includegraphics Peter Flynn <peter@silmaril.ie> - 2021-01-26 22:33 +0000
  Re: convert this PostScript file to one which works with \includegraphics ken <ken@spamcop.net> - 2021-01-27 07:58 +0000
    Re: convert this PostScript file to one which works with \includegraphics helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2021-01-27 08:53 +0000
      Re: convert this PostScript file to one which works with \includegraphics ken <ken@spamcop.net> - 2021-01-27 17:12 +0000
      Re: convert this PostScript file to one which works with \includegraphics Scott Pakin <scott+ctt@pakin.org> - 2021-01-28 14:07 -0700
        Re: convert this PostScript file to one which works with \includegraphics helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2021-01-29 12:45 +0000
  Re: convert this PostScript file to one which works with \includegraphics "Jeffrey H. Coffield" <jeffrey@digitalsynergyinc.com> - 2021-01-27 11:53 -0800
  Re: convert this PostScript file to one which works with \includegraphics Dr Eberhard W Lisse <nospam@lisse.NA> - 2021-01-30 16:15 +0200
    Re: convert this PostScript file to one which works with \includegraphics helbig@asclothestro.multivax.de (Phillip Helbig (undress to reply)) - 2021-01-30 20:28 +0000
      Re: convert this PostScript file to one which works with \includegraphics Dr Eberhard W Lisse <nospam@lisse.NA> - 2021-01-31 16:07 +0200

csiph-web