Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uwm.edu!bbn!bbn.com!pdsmith
From: pdsmith@bbn.com (Peter D. Smith)
Newsgroups: comp.graphics
Subject: Re: Postscript <=> EPS
Keywords: Possible?
Message-ID: <51029@bbn.COM>
Date: 17 Jan 90 15:49:02 GMT
References: <12702@cbnewsd.ATT.COM> <7257@lindy.Stanford.EDU>
Sender: news@bbn.COM
Reply-To: pdsmith@spca.bbn.com (Peter D. Smith)
Distribution: usa
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 22

Well, not exactly.  EPS does not have to include a bitmap.  Basically,
an EPS file is a DEAD NORMAL PS file except that
 -1- There are some extra double-% comments; the most important of
     which is '%%BoundingBox: llx lly urx ury
 -2- There are a series of forbidden PS commands, among them
     erasepage, grestoreall, initclip, inigraphics, initmatrix.
     showpage IS allowed (the other program must neutralize it).
 -3- Since the point of an EPS file is that it is swallowed up,
     lock, stock, and barrel by another program which will surround
     (encapsulate!) it, it is CRITICAL that the stack be left just 
     the way it started. 

The book 'Understanding Postscript programming (second edition)' by
David A. Holzgang is a lousy reference, but has a very clear EPSF
section.
     

Note on competance: I am in the finishing stages of converting my
companies product from producing Postscript to producing EPS.


				Peter D. Smith