Path: utzoo!attcan!uunet!lll-winken!ames!xanth!ukma!rutgers!njin!princeton!phoenix!mbkennel
From: mbkennel@phoenix.Princeton.EDU (Matthew B. Kennel)
Newsgroups: comp.sys.next
Subject: Re: Postscript Previewing?
Keywords: postscript, preview
Message-ID: <5412@phoenix.Princeton.EDU>
Date: 15 Jan 89 04:23:37 GMT
References: <16435@iuvax.cs.indiana.edu> <1485@mace.cc.purdue.edu> <6104@polya.Stanford.EDU>
Reply-To: mbkennel@phoenix.Princeton.EDU (Matthew B. Kennel)
Organization: Princeton University, NJ
Lines: 18

In article <6104@polya.Stanford.EDU> aozer@NeXT.com (Ali Ozer) writes:
>
>The source is in /MyDisk/Programming/Examples, and the executable is in
>/MyDisk/Programming/Demos. Unfortunately, Yap isn't suitable for
>previewing the output of programs such as TeX, word processors, CAD
>programs, etc. Yap doesn't know about bounding boxes, and nor does it know
>how to deal with multiple page documents.
>
Why should "Yap" have to know about bounding boxes & stuff like that;
shouldn't the Postscript interpreter know how to deal with that stuff?

Or is Postscript alone inadequate?

>Ali Ozer, NeXT Developer Support
>aozer@NeXT.com

Matt Kennel, Princeton Physics Peon
mbkennel@phoenix.princeton.edu