[comp.sys.apollo] lpr, lpd problem?

mcguire@math.uiowa.edu (Charlie McGuire) (10/11/90)

I have a number of hosts that send postscript files to 
apollos via remote lpr. The problem is many of the postscript
files have very long lines, and lpr (or lpd - I'm not sure
which) refuses to deal with anything longer than 130 
characters. I've tried various options for both to no avail.

I'm running SR10.2.0.6 on DN3500's and using /com/prf as the
print command in /etc/printcap. PRF alone doesn't care how
long lines are once it recognizes the file is postscript.

Any suggestions?

Charlie McGuire
Dept. of Computer Science
The University of Iowa

mcguire@math.uiowa.edu
mcguire@cs.uiowa.edu

goldfish@CONCOUR.CS.CONCORDIA.CA (-- Paul Goldsmith) (10/12/90)

"lpr" has 132 hardcoded into it (at least the shipped Berkeley source
does).  

So much for academics and all that object oriented navel gazing.
Either:
	change lpd (if you can)

	note that postscript can accept line breaks between most
	tokens  and use "fold", or "sed" or "awk" to
	intelligently place line breaks. 

	modify the output to split long lines. (most Postscript
	filters will do this automatically).

The key here is that "lpr" has a hardcoded line length.

-- Paul Goldsmith
    (goldfish)        (514) 848-3031         <goldfish@concour.cs.concordia.ca>
         (Shirley Maclaine told me there would be LIFETIMES like this)