Bug#471228: [Pkg-cups-devel] Bug#471228: Cannot print any more: Print-Job client-error-bad-request: Unsupported character set "iso-8859-15"!
On Tue, 29 Apr 2008 23:26:03 +0200
Martin Pitt <mpitt@debian.org> wrote:
> tag 471228 upstream wontfix
> forwarded 471228 http://www.cups.org/str.php?L2686
> thanks
>
> Hi Christian,
>
> Christian Hammers [2008-03-16 20:07 +0100]:
> > The desktop from which I try to print from is using Debian etch with
> > CUPS 1.2.7-4etch2 and locales de_DE@euro ISO-8859-15. The server is using
> > Debian sid with the same locales.
> > On the client side there is no cupsd but only:
> > # cat /etc/cups/client.conf
> > ServerName app109.intern
> >
> > # cat /etc/cups/lpoptions
> > Default epson
> >
> > I tried to print an US-ASCII text file using a2ps. The generated postscript
> > file itself includes "/ISO-8859-1Encoding" if that matters.
> >
> >
> > ==> /var/log/cups/error_log <==
> > E [16/Mar/2008:19:48:11 +0100] Unsupported character set "iso-8859-15"!
> > D [16/Mar/2008:19:48:11 +0100] Discarding unused server-audit event...
> > D [16/Mar/2008:19:48:11 +0100] Print-Job client-error-bad-request: Unsupported character set "iso-8859-15"!
>
> This is known upstream as http://www.cups.org/str.php?L2686. Since
> 1.2, cupsd only supports ASCII and UTF-8 encoding of IPP requests.
>
> Seems that upstream considers this a design decision and isn't going
> to do anything about it. I won't either, I'm afraid; Adding support
> for non-UTF8 locales in Debian, and maintaining this patch would be
> utterly painful (aside from the fact that non-UTF8 locales should just
> die, die, die! :-) ).
>
> Do you want to keep the bug open given the situation?
Well we currently have a problem that etch desktops cannot print
any more after their printserver gets upgraded from etch to lenny
and they happen to use an ISO locale on the Desktop.
If that conclusion is valid then it deserves a place in the release
notes :(
Would a patch to the cupsys-client package in etch that converts
everything send to a CUPS server to UTF-8 be possible?
bye,
-christian-
Reply to: