Previously Travis Freeland wrote:
> For page counting we simply ask the printer how many pages it printed
> after the job is complete.
Unfortunately I need to know the number of pages in advance in order
to decide of a user has enough credit available.
Wichert.
--
__
essential that I have the pagecount of
>a printjob before I send it to the printer.
>
>Looking at the samba sources the number of pages in a printjob is
>sent as part of the job_info_2 structure and extracted by
>smb_io_job_info_2(). What I don't see is what is done with that
>inf
On Fri, 2002-05-24 at 17:55, John E. Malmberg wrote:
> If you could charge by the killobyte sent to the printer, that could
> probably done accurately.
with raw data kilobytes are NOT a good choice.
printers today accept many data formats.
the same image in postscript and jpeg use a really diff
ources the number of pages in a printjob is
> sent as part of the job_info_2 structure and extracted by
> smb_io_job_info_2(). What I don't see is what is done with that
> information. Ideally I would like to have all the information
> in that struct available in the print command.
&
> On Fri, May 24, 2002 at 02:55:58PM +0200, Wichert Akkerman wrote:
>I'm working on a system where customers have to pay for pages they
>print, and as such it is essential that I have the pagecount of
>a printjob before I send it to the printer.
This is a difficult thing to do accurately.
For p
ources the number of pages in a printjob is
> sent as part of the job_info_2 structure and extracted by
> smb_io_job_info_2(). What I don't see is what is done with that
> information. Ideally I would like to have all the information
> in that struct available in the print command.
&
I'm working on a system where customers have to pay for pages they
print, and as such it is essential that I have the pagecount of
a printjob before I send it to the printer.
Looking at the samba sources the number of pages in a printjob is
sent as part of the job_info_2 structure and extr
