Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!angel.Eng.Sun.COM!henry
From: henry@angel.Eng.Sun.COM (Henry McGilton)
Newsgroups: comp.lang.postscript
Subject: Re: Encapsulated PostScript
Summary: Some More Of The Story
Message-ID: <1929@exodus.Eng.Sun.COM>
Date: 1 Nov 90 22:56:59 GMT
References: <1990Nov1.145512@ecn.purdue.edu>
Sender: news@exodus.Eng.Sun.COM
Lines: 45

In article <1990Nov1.145512@ecn.purdue.edu>, zentner@ecn.purdue.edu (Michael Zentner) writes:

    *  I've read some of the recent information on EPS posted
    *  here, and have not seen this problem covered yet.  First,
    *  what's meant by EPSI, EPSF, ,ect...  These obviously are
    *  not the same thing (according to the programs I'm trying to
    *  use to import them).
EPS is Encapsulated PostScript.

EPSF is Encapsulated PostScript File.  From previous discussions,
Encapsulated PostScript files can contain an optional BINARY preview
section so that importing applications lacking a working PostScript
interpreter can display on the screen an approximation of what will
appear on the printing device when the entire page is printed.  The
optional preview section can be in PICT, TIFF, or Metafile.

The BINARY preview section creates a severe problem.  You cannot
easily view or edit this stuff with a regular text editor such as
VI.  `Why do you need to view or edit EPS files?' I hear you ask.  You
need to edit EPS files to fix the PostScript when it's broken for
some reason, as it so frequently is.  So, the EPSI specification is a
fairly recent addition to the preview capability.  EPSI is an all
ASCII readable preview section.  Such an EPS file is all ASCII and
readable and editable.

    *  Specifically, I'm trying to import an EPS file created
    *  with Sundraw into Framemaker on the Sun system.  I
    *  think the Sundraw file is EPSF.
The SunDraw file is EPSF that conforms to the EPSF 1.2 specification.
SunDraw EPSF files contain a binary header, PostScript, and a TIFF
preview section.
    *  Framemaker says they require EPSI, and does not
    *  recognise the file as graphics.
SunDraw's EPSF interchange method was impelemnted before there was 
a completely defined `official' EPSI specification.

    *  Another funny thing that happens that I can't explain:
    *  I create the EPS file with Sundraw and it exists on the
    *  system.  Then I try to look at it with 'more', 'od',
    *  'view', etc...  After I look at it once, the file has a
    *  length of 0 and no longer contains any information.
    *  Anybody know what's happening?
I say Bar Steward -- more tranquilisers please!!!

	........  Henry