At 01:05 PM 1/3/01 -0800, [EMAIL PROTECTED] wrote:
>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...
I assume that this is a Postscript "trick?"
Are you saying there is positively, absolutely no way to defeat this
trick? That it is impossible to write a parser that can root out a
true page count in a queued file?
It seems to me that "forewarned is forearmed"- knowing that jobs can
be encapsulated, you simply write your parser to deal with that fact
from the beginning. If the printer can interpret the data, then a
sufficiently intelligent parsing program should be able to do the same.
Did I miss something important?
Cheers.
--
Learning Linux is like joining a cult. Sure it's fun at first but you waste
time, become brainwashed, and then have to be de-programmed by Bill Gates
before you can work for Him again.
- Ray Lopez, in UFhK4.33289$[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.
-----------------------------------------------------------------------------