Bug#644444: pkpgcounter does not properly handle all postscript documents with copies or n-up options

2011-10-05 Thread alet
Hi, On Wed, Oct 05, 2011 at 06:05:48PM -0500, Brian Paul Kroth wrote: > > I attempted to pass this info to the original dev, but haven't gotten > any response. I'm sorry for this. I'm slowly recovering from an accident and I'll try to be back at work on this and several other issues in this soft

Bug#644444: pkpgcounter does not properly handle all postscript documents with copies or n-up options

2011-10-05 Thread Brian Kroth
a...@librelogiciel.com 2011-10-06 01:20: Hi, On Wed, Oct 05, 2011 at 06:05:48PM -0500, Brian Paul Kroth wrote: I attempted to pass this info to the original dev, but haven't gotten any response. I'm sorry for this. I'm slowly recovering from an accident and I'll try to be back at work on t

Bug#644444: pkpgcounter does not properly handle all postscript documents with copies or n-up options

2011-10-05 Thread Brian Paul Kroth
Package: pkpgcounter Version: 3.50-7 Severity: normal As stated, the current pkpgcounter's postscript.py native implementation trusts files to be a DSC compliant a little too much. It doesn't properly handle documents printed n-up or certain copies options. For example, I had a document tha