> From [EMAIL PROTECTED] Wed Jan 3 09:39:06 2001
> Date: Wed, 3 Jan 2001 17:27:04 +0100
> From: Hermann Lauer <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: LPRng: ifhp: pjl_console messages & printer status/debug output
>
>
> --6c2NcOVqGQ03X4Wi
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> Dear List readers,
>
> I discovered the new 'pjl_ready_msg' to set the ready msg of hp
> printers - nice stuff !
> This should be also possible for the JOB display message - so
> I implemented this with the appended patch, which unifies
> the building of the DISPLAY string. Maybe there are other places
> (while doing accounting?) to insert this. Works rather nicely
> here, now.
>
> One thing which would be very helpfull to use the 32 chars
> display of my hp4050 would be a formatting sequence to
> cut out the last n chars of a string - the first N chars works
> good with the following formatting:
>
> \%N.Ns{var}
I have perused the code and it looks like you can only get the first N
charrs.
>
> I tried several variations with no success - is it possible
> with the current code ?
No.
>
> Some comments on the processing of the status messages from the
> printer:
>
> 1) Is it possible to extract PJL and PS status together ? At the
> moment it look like this is not possible together, and my
> printer delivers sometimes nice page counts during processing
> of a pjl encapsulated ps job.
Yes, but there is a problem: the job page counts are for the
ENCAPSULATED jobs... you may have 1 file with multiple jobs, and you
get multiple DIFFERENT page counts, 1 for each job. This is a favorite
trick of ... users... who send a 200 page report followed by a 1 page
'job' in a file and get billed for one page... but I digress...
>
> 2) Is it possible to get the full status returns from the printers
> at stderr, separated from the normal ifhp output which goes
> to the status file (or to a separate file) ? Is it possible to
> redirect only debug messages to stderr ?
> In my opinion that would be nice options, as the "lpq -l" output
> looks rather ugly with debugging enabled.
Yes. You have the code! Go for it!
>
> Many thanks for all the work on ifhp - it can do rather impressive
> things already.
>
> Greetings
>
> Hermann
>
> --
> Bildverarbeitungsgruppe des Interdiziplinaeren Zentrums fuer
> wissenschaftliches Rechnen, Universitaet Heidelberg
> INF 368; 69120 Heidelberg; Tel: (06221)54-8826, -6314 Fax: -8850
> Email: [EMAIL PROTECTED]
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
