On Tue, Feb 24, 2009 at 11:02:10AM +0100, Joachim Breitner wrote:
>
> The .ppd file is the one downloaded from
> http://kyoceramita.com/download/
> for Kyocera_FS-C5300DN (German, that is at
> http://www.kyoceramita.eu/index/service/dlc.false.driver.FSC5300DN._.EN.html
> the very bottom.
>
> I have
Hi Jerome,
Am Montag, den 23.02.2009, 23:58 +0100 schrieb a...@librelogiciel.com:
> Unfortunately they've decided against fixing this problem upstream
> finally, see their BTS link above.
>
> If you know for sure these datas were produced with foomatic maybe you
> could see if its authors would m
Hi,
On Mon, Feb 16, 2009 at 06:43:26PM +0100, Joachim Breitner wrote:
>
> Am Montag, den 16.02.2009, 18:39 +0100 schrieb a...@librelogiciel.com:
> > On Mon, Feb 16, 2009 at 06:23:56PM +0100, Joachim Breitner wrote:
> > >
> > > I’d expect them so see the latter case (PS interpreter), but from a use
Hi,
Am Montag, den 16.02.2009, 18:39 +0100 schrieb a...@librelogiciel.com:
> On Mon, Feb 16, 2009 at 06:23:56PM +0100, Joachim Breitner wrote:
> >
> > I’d expect them so see the latter case (PS interpreter), but from a user
> > point of view, it doesn’t matter much :-)
>
> It seems the bug report
On Mon, Feb 16, 2009 at 06:23:56PM +0100, Joachim Breitner wrote:
>
> I’d expect them so see the latter case (PS interpreter), but from a user
> point of view, it doesn’t matter much :-)
It seems the bug report was accepted by GhostScript's upstream
developers, and there's a patch, please see :
h
Hi,
Am Sonntag, den 15.02.2009, 18:37 +0100 schrieb a...@librelogiciel.com:
> On Sun, Feb 15, 2009 at 03:05:04PM +0100, Joachim Breitner wrote:
> >
> > I’m not sure if I can follow this argument. The attached print file was
> > not valid postscript, but rather postscript wrapped in an PJL print jo
On Sun, Feb 15, 2009 at 06:37:42PM +0100, a...@librelogiciel.com wrote:
> I'm not 100% against implementing a workaround for this problem, but I'd
> prefer that ghostscript developers handle this situation, otherwise
> other developers would have to create similar workarounds for their own
> softwa
On Sun, Feb 15, 2009 at 03:05:04PM +0100, Joachim Breitner wrote:
>
> I’m not sure if I can follow this argument. The attached print file was
> not valid postscript, but rather postscript wrapped in an PJL print job,
> if I understand it correctly. Therefore, it can not be a bug in
> ghostscript.
Hi Jerome,
thanks for your quick answer.
Am Samstag, den 14.02.2009, 16:13 +0100 schrieb a...@librelogiciel.com:
> On Sat, Feb 14, 2009 at 03:21:00PM +0100, Joachim Breitner wrote:
> This is a bug in GhotScript, not in pkpgcounter as can be seen below :
>
>
> jer...@lafrime:~$ gs testprintfile
On Sat, Feb 14, 2009 at 04:13:12PM +0100, a...@librelogiciel.com wrote:
>
> This is a bug in GhotScript, not in pkpgcounter as can be seen below :
In any case, if you want a workaround to be considered for a future
release, please create a ticket asking so on http://trac.pykota.com
thx in davance
On Sat, Feb 14, 2009 at 03:21:00PM +0100, Joachim Breitner wrote:
> Package: pkpgcounter
> Version: 3.50-4
> Severity: normal
> Tags: patch
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> when trying to get ink accounting working here, it failed because the
> file that CUPS sent to
Package: pkpgcounter
Version: 3.50-4
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
when trying to get ink accounting working here, it failed because the
file that CUPS sent to pkpgcounter (via pykota) contained a PJL header:
$ pkpgcounter -cGC /var/spool/cups/tm
12 matches
Mail list logo
