🚀 go-pugleaf

In article <1992Aug2.194857.28249@cco.caltech.edu>
carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:

|> In article <3669@ecicrl.ocunix.on.ca>, clewis@ferret.ocunix.on.ca
|> (Chris Lewis) writes:
|> >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.

I have the understanding that none of the Adobe documentation
specifies Control-D, but that specific Postscript implementations
require it.  (I'm sure someone will fla... uh... correct me if I'm
wrong.)

With the above understanding, if the application knows only that the
target printer accepts Postscript (and perhaps even the level of
Postscript), then it is not application's business to worry about
whether the printer needs a Control-D.

If the application has knowledge of each precise brand and model of
printer (and I know some do), then it's less clear.  In the
single-user PC environment, this is unfortunately necessary, but in a
shared environment, this detailed knowledge is A Bad Thing because it
causes more problems than it solves.$$
-- 
INET: mrl@uai.com      BANG: uunet!uaisun4!mrl      ICBM: USA; Lower Left Coast
  "You can get a crowd to clap at a phone number, if the inflection is right."
   -- Dave Ross