Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mintaka!think.com!spool.mu.edu!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Getting Postscript output printed correctly
Summary: FlameMaker!
Message-ID: <1722@toaster.SFSU.EDU>
Date: 15 Jun 91 08:34:03 GMT
References: <676783283@macbeth.cs.duke.edu> <1714@toaster.SFSU.EDU>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 21

Aha!  I just ran into a PostScript document with problems very
much like what Henry described.  The culprit here is:

% FrameMaker PostScript Prolog 2.0, for use with FrameMaker 2.0
% Copyright (c) 1986,87,89 by Frame Technology, Inc.  All rights reserved.

containing the test

	Encoding StandardEncoding eq

By changing this to

	Encoding dup StandardEncoding eq exch NextStepEncoding eq or

I was able to get it to Preview correctly.


Note that the NeXT version of FrameMaker uses a different prolog
and produces proper Conforming PostScript.

					-=EPS=-