Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!eos!aio!poirot
From: poirot@aio.jsc.nasa.gov (Daniel T. Poirot)
Newsgroups: comp.lang.postscript
Subject: PS Utilities (was: Re: Diatribe, revisited)
Summary: Do you have them?
Message-ID: <1991May8.141344.17298@aio.jsc.nasa.gov>
Date: 8 May 91 14:13:44 GMT
References: <1991May5.214431.27894@neon.Stanford.EDU>
Reply-To: poirot@aio.jsc.nasa.gov (Daniel T. Poirot)
Organization: NASA Johnson Space Center
Lines: 23

In article <1991May5.214431.27894@neon.Stanford.EDU> rokicki@neon.Stanford.EDU (Tomas G. Rokicki) writes:

>                                           Adobe should write and make
>available a simple C routine that properly reads and parses a properly
>formed PostScript file, passing resource requirements up to the next higher
>level and performing any other relevant operations.  

>Heck, I can envision a single tool---a C program with a few prolog
>files---that would take example output from an application and test it in
>all of the above ways, and print out an analysis of the PostScript and
>suggestions for improvements.

>-tom

How about even an INDENT program?  I have had to look at postscript files
from all sorts of sources.  If there was a program like indent(1) that
would at least know where to put in newlines, random ps files could be
filtered into something you could at least READ.
-- 
Daniel Poirot           poirot@aio.jsc.nasa.gov
NASA JSC                "The mind is a terrible thing."
ER3                     tel: (713)483-8793
Houston, TX 77058       fax: (713)483-3204