Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!news.syd.connect.com.au!phaedrus.kralizec.net.au!news.mel.aone.net.au!news.netspace.net.au!news.mira.net.au!pumpkin.pangea.ca!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-xfer.netaxs.com!news.fast.net!newsgate.ptd.net!news.ptd.net!not-for-mail From: nickf@ptd.net (Nick Folino) Newsgroups: comp.unix.bsd.freebsd.misc,comp.periphs.printers Subject: Re: Remote LPD Postscript printing quandary... Date: 15 Mar 1997 16:16:19 GMT Organization: ProLog - PenTeleData, Inc. Lines: 32 Message-ID: <332bcb0d.48972344@news.ptd.net> References: <E704sD.FAw@rockyd.rockefeller.edu> Reply-To: nickf@ptd.net NNTP-Posting-Host: cs1-5.pot.ptd.net NNTP-Posting-User: nickf Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Newsreader: Forte Agent .99g/32.339 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37104 comp.periphs.printers:61559 On Thu, 13 Mar 1997 21:53:01 GMT, Dan Ts'o <dan@dnn.rockefeller.edu> wrote: > A problem that's been bugging me for years... > We have an HP Postscript printer with a network interface that >groks LPD. The way I understand it, under these conditions the local lpr/lpd >just ships the print job to the remote LPD host sans any filtering and the >local /etc/printcap entry is rather bare, only having rp= and rm= entries >(more or less...). In particular no local filtering is done. > > What we want is for the lpr command to behave such that it will >accept either raw Postscript or plain ASCII text and behave correct *without >having to specify any options to lpr*. Why ? because many Unix programs like >elm, tin, Netscape, etc. all default to print by piping to lpr (no options). >So lpr should be smart enough to take both ASCII and Postscript jobs >straightup and do the right thing. This is pretty easy if the remote LPD >host is a Unix machine, but in this case, it is a network printer. > > It all actually works except that HP PCL needs CRLF instead of just >LF to print ASCII text correctly. It seems that if Unix would just add CR's >before sending jobs to the remote printer, both ASCII text and Postscript >would be happy. Indeed in other configurations that works. > > Any hints ? Thanks. > >-- Check out the handbook. There's some samples in there on setting up HP's to print both PS and PCL. It works fine on my HP. Nick