Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!iggy.GW.Vitalink.COM!widener!netnews.upenn.edu!grip.cis.upenn.edu!sal
From: sal@grip.cis.upenn.edu (Marcos Salganicoff)
Newsgroups: comp.windows.ms
Subject: Re: Printing Uploaded Windows Postscript files from Unix 4.3bsd??
Message-ID: <41729@netnews.upenn.edu>
Date: 22 Apr 91 19:59:17 GMT
References: <41541@netnews.upenn.edu> <1991Apr20.082038.21633@agate.berkeley.edu> <1991Apr20.181504.699@midway.uchicago.edu> <1991Apr22.191217.11474@bronze.ucs.indiana.edu>
Sender: news@netnews.upenn.edu
Reply-To: sal@grip.cis.upenn.edu (Marcos Salganicoff)
Organization: University of Pennsylvania
Lines: 11
Nntp-Posting-Host: grip.cis.upenn.edu

As a followup: It turns out the windows postscript driver sometimes
uses a lf character to seperate lines in the output file. When I used 
microemacs to delete the ^d at the beginning of the psfile and saved
the result the lfs were removed, ergo my keywords were smushed
together and the psfile was unparsable ==>
Don't use microemacs to diddle ps files from windows. Problem solved.
-Marcos

General Robotics and Active Sensory Perception Lab
The University of Pennsylvania
Philadelphia, PA (USA)