Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!uunet!rosie!aozer
From: aozer@next.com (Ali Ozer)
Newsgroups: comp.sys.next
Subject: Re: graphics in WriteNow 2.0
Message-ID: <425@rosie.NeXT.COM>
Date: 28 Mar 91 20:02:32 GMT
References: <19419@lanl.gov>
Sender: news@NeXT.COM
Distribution: na
Organization: Next Computer, Inc.
Lines: 31
Nntp-Posting-Host: twinpeaks.next.com

In article <19419@lanl.gov> silbar@mpx2.lampf.lanl.gov writes:
>Peculiar thing happened yesterday when I tried to look at a WriteNow
>file that I put together under OS 1.0.  It had a logo in it, an EPS
>file that I had made using YAP ... 
>Under 2.0 ... it opens up with the graphic hidden.

Your .eps file probably isn't a totally valid; ie, it's missing some
required component in the header or the bounding box. Under 1.0, WriteNow
parsed .eps files itself; under 2.0, it uses NeXTstep's .eps parser, which is
somewhat more sensitive about errors.

Your 1.0 WriteNow document knew the image size, so under 2.0 the area the 
image would've occupied is shown correctly, although the image isn't displayed.
When you try to put the image in a new document using 2.0 WriteNow, the file
isn't parsed, so WriteNow never even finds out about the bounding box.
That explains the mystery of why your original document has some idea of
the size of the image and why a new one doesn't.

Your .eps file should minimally have something like the following in its
header:

%!PS-Adobe-2.0
 ... possibly other lines starting with %% ...
%%BoundingBox: 100 20 600 750

 ...


Ali, Ali_Ozer@NeXT.com