Note: please don't spam any of the e-mail addresses which you see here. Follow this link if you want some addresses to misuse.
From: David Chappell <David.Chappell@trincoll.edu> Date: Fri, 25 Mar 2005 21:45:45 -0500 Subject: Re: PPR: problem with a charge' printer Jan Kohnert wrote: >Benoit Marchal schrieb: > > >>Hello >> >>I use ppr 1.53b1 on a Rehat 3.0 ES. >> >>When a student want to print a multiple pages on a single page, the >>charge is not the cost of one printing but the cost multiple by the >>number of pages. ie. If I want to print on a single page the content of >>six pages, the cost is six. >> >I think David knows about the problem, AFAIK you can use some kind of >"filter", that sets the correct paying number. Just look in the >documentation, search for something like editps, maybe also in the mailing >list archive. This is only a workaround, of course. > >David, could you clearify this one? I searched the sources for payment, but >could not find the correct part to edit (And I must confess, I still not >understand how the payment is computed). Maybe it's related to any bad >Win-drivers, that don't produce the corretc ps-headers? As I got some >complants about this problem in the recent time, I think this has to be fixed >in some way. > I believe that when N-Up mode is selected in PPR, it computes the charge correctly. Perhaps the Windows printer driver is inserting PostScript code to perform N-Up without PPR perceiving it? PPR currently charges for the number of pages which ought to have been printed based on the information available to it. The charge is computed by compute_charge() in libppr/charge.c. I don't think there is anything wrong with that function. The problem is that it is receiving the wrong input. I might be able make an editps filter which would allow compute_charge() to receive the proper N-Up number. I suppose we could use the number of pages reported by the printer (where available) to work back to the correct data, but I am not yet sure how to do that. If someone will post a PostScript file demonstrating the problem somewhere where we can download it, I will have a look.