🚀 go-pugleaf

In article <3669@ecicrl.ocunix.on.ca>, clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
>In article <1992Aug2.001052.23580@cco.caltech.edu> carl@SOL1.GPS.CALTECH.EDU writes:
>|In article <3668@ecicrl.ocunix.on.ca>, clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
>|>While things that are DSC compliant will lead off with %!PS-Adobe-, you're
>|>being much too strict.  By convention, PostScript always starts with
>|>%!.  So if the file starts with %!, you can assume it to be PostScript.
>|>Regardless of whether the file claims to be DSC compliant or not.
>
>|>Almost all applications use this convention.  Though, there are some stupid
>|>broken ones.  Ie: WP apparently leads files with <control-D>%!.
>
>|Which is, in my opinion, a reasonable thing to do, as it's the only way to
>|guarantee that the previous PostScript program has ended before yours starts.
>
>A much better way is to fix the spooler to always emit the ^D at the end of
>jobs.  Applications should *not* be generating ^Ds.

In principal, I agree with you:  Applications should not HAVE to generate
control-D's.  In practice, an application has no guarantee that the software
that sends the file to the printer will do the right thing.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.