Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!abvax!icd.ab.com!jaz
From: jaz@icd.ab.com (Jack A. Zucker)
Newsgroups: comp.windows.ms
Subject: Re: EPS rendering on screen.
Message-ID: <1872@abvax.UUCP>
Date: 19 Sep 90 12:48:39 GMT
References: <1866@abvax.UUCP> <57507@microsoft.UUCP>
Sender: news@abvax.UUCP
Reply-To: jaz@icd.ab.com (Jack A. Zucker)
Organization: Allen-Bradley Company, Industrial Computer Division
Lines: 27

In article <57507@microsoft.UUCP>, philba@microsoft.UUCP (Phil BARRETT) writes:
> 
> EPS stands for encapsulated postscript.  the whole point of EPS is to
> provide a `header' that can be rendered on screen in systems that aren't
> capable of displaying PS (i.e. allmost all Windows PCs).  If you want better 
> on-screen display of your EPS files, the best way to do.

No, that is not the point of EPS. The point of EPS is that it is a self
contained "sub-routine" that does not change the state of any of the
global postscript variables. It also defines a bounding box size that the
host application uses to determine what space to allocate to it on the page.

Now granted, it does provide for a bit-mapped header to be placed in the
file for previewing purpose, however the preview is many times grossly
inaccurate. I've found when cropping pictures for example, that the bitmap
does not register exactly with the postscript, causing WYSINWYG (What you see
is not what you get).

-jaz



| Jack A Zucker	                 {cwjcc,pyramid,decvax,uunet}!jaz@icd.ab.com |
| Allen-Bradley Company, Inc.     or                       ICCGCC::ZUCKER    |
| 747 Alpha Drive                 
| Highland Hts., OH 44143         phone: (216) 646-4668   FAX: (216)
646-4484 |