Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!elroy!jplopto!earle
From: earle@jplopto.UUCP
Newsgroups: comp.lang.postscript
Subject: Why on earth does TranScript pass the # of copies on to the spooler?!?
Message-ID: <4868@elroy.Jpl.Nasa.Gov>
Date: Thu, 19-Nov-87 04:32:56 EST
Article-I.D.: elroy.4868
Posted: Thu Nov 19 04:32:56 1987
Date-Received: Sat, 21-Nov-87 14:29:13 EST
Sender: news@elroy.Jpl.Nasa.Gov
Reply-To: earle@mahendo.JPL.NASA.GOV (Greg Earle)
Followup-To: poster
Organization: Rockwell International, Seal Beach  CA
Lines: 20
Keywords: TranScript 2.0  enscript  psroff  ptroff

Can someone from Adobe (or elsewhere) please tell me - Why on earth do the
TranScript utilities (enscript, psroff, ptroff) pass the `-#n' option (for
# of copies) on to the printer spooler, so the stupid thing can generate
*n* times as many bytes to shove down the printer's throat, and take (at
least, I presume) n times as long to print out all of the copies of the
document?  Why is this done instead of inserting a `/#copies n def' into
the output stream, thus not only saving n times the download time, and all that
added printing time, but presumably all the extra time saved by having the
n pages printed bang-bang-bang while the page is still inside the printer's VM?
I will never print out `n' copies of big documents (like Xlib or the GNU
Emacs manual) via `-#' again, I'll dump the PostScript to a file and jam it
in there myself!

I'm absolutely stumped as to why this isn't done.  I hope there's a logical
explanation ...

	Greg Earle		earle@jplopto.JPL.NASA.GOV
	S(*CENSORED*)t		earle%jplopto@jpl-elroy.ARPA	[aka:]
	Rockwell International	earle%jplopto@elroy.JPL.NASA.GOV
	Seal Beach, CA		...!cit-vax!elroy!smeagol!jplopto!earle