🚀 go-pugleaf

In article <809@adobe.UUCP> greid@adobe.COM (Glenn Reid) writes:

] You missed the most important part of his message.  The script/program
] to add a control-D is easy.  The important part is OMITTING IT when you
] are writing to a file and you know you are writing to a file, and
] INCLUDING IT when you are writing to a device like a tty:

] The right solution is to do something different when you write to a
] local file.  In fact, lots of things should probably be different, not
] just the ^D at the end.  You should include the prologue, not just the
] document part (if you have downloaded the prologue separately into the
] VM of the printer on a "DEDICATED" printer).  You should TAKE OUT any
] device-specific code that selects, say, a paper size, and put in
] COMMENTS instead that will teach a spooler somewhere else how to print
] the file correctly on a different printer.

Unfortunately, the right solution *was* to do something better with
the language/EPSF/printer planning, but it's too late now.

From what I can tell from all these discussions, the purpose of the
implementation-dependent-EOT-marker ( e.g. ^D ), is to tell the
printer this print job  is done, so it can play games with  EPSF
like reversing pages.  (Otherwise, all it would need to do is wait
for showpage messages and print stuff.)

Shouldn't this have been done by  defining the  appropriate EPSF code?
-- 
# Bill Stewart, AT&T Bell Labs 2G218 Holmdel NJ 201-949-0705 ho95c.att.com!wcs
# also found at 201-271-4712 tarpon.att.com!wcs 

# welcome, to mars, eh, hosers!  Have a brew and some donuts, eh?