You mean I shouldn't have 'fixed' it? Aaahh!
The file worked fine for me when it had the spurious lines, printed O.K.,
viewed via Solaris pageview fine, and Adobe Exchange read it as a .ps file
with no complaints.
Now that I 'fixed' it by removing spurious characters, all works but for
LPR printing on my IIIsi.
Spurious characters will return to the posted .PS version, you may resume
postscript editing if you like.
At 03:39 PM 9/20/96 -0500, Doug Hughes wrote:
>On Fri, 20 Sep 1996, Richard Johnson wrote:
>> At 19:52 9/19/96, Bill Stout wrote:
>> Beware on the PS version. It's not a Postscript file until you edit what
>> you grab from the site and remove the following spurious line from the top
>> ^[%-12345X @
PJL ENTER LANGUAGE=POSTSCRIPT
>> and the following spurious line from the end:
>> Most of my printers spew reams of Postscript code when they're given such a
>> text file that doesn't start with %!PS-Adobe-...
>> I've learned the hard way to carefully check any so-called Postscript file
>> that was generated on an MS Windows system. Looks like Windows adds more
>> than a ^D at the beginning and end of the files now.
>FYI, that is the PCL escape code to go into PostScript modes. Apparently
>he has an HP PCL/PS laser printer to which he normally sends his print
>Doug Hughes Engineering Network Services
>System/Net Admin Auburn University
> doug @
Senior Systems Admin NT/UNIX/I-net/Routers/Mainframes/Janitor ;)
Hitachi Data Systems 408-970-4822 --- Disclaimer: I speak only for myself
___________"Infowar, Cyber-war, yes, 'they' _are_ out to get you..."___________