Subject: | |
From: | |
Reply To: | |
Date: | Mon, 30 Oct 1995 20:08:00 GMT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Jeff Kell ([log in to unmask]) wrote:
: In this, and in another suggestion or two, we're missing the point. He has
: a raw binary PCL file to send to a printer. Every HP utility that I know
: of (print/fcopy/etc) will do a record-oriented transfer. In such cases,
: even with binary designations, each record will be written followed by at
: least a carriage return/linefeed - and this <cr><lf> will interrupt the PCL
: data stream.
This is correct.
: The only solution I know of is either third party, or else write your own
: program which reads the input file on a record-by-record basis and then
: writes it to the output device with a no-space (%320) carriage control.
This is (currently) also correct, and is quite easy. Bulletproofing (such
as processing only true raw binary files) may add somewhat to the complexity.
I wrote a simple program in about 30 minutes as part of our network printing
testing.
: I've never tried it, but one *possibility* might be to send the file to the
: output device as if it were an environment file (which I think does indeed
: do a binary transfer); so if you have file 'rawpcl' perhaps (just guessing)
: you might be able to:
: :file out;dev=xx;env=rawpcl
: :fcopy from=;to=*out
: <either hit ctl-y or type :eod>
Bzz-z-zt! Nice try, but not today. The ENV processing for the new network
printing stuff should work this way, but I never thought of trying that.
You bet I will now. Thanks for the tip Jeff. :-)
-Larry "MPE/iX Network Printing 'R' Us" Byler-
|
|
|