Does it work for you with CUPS 1.3.7?
If yes, I am very interested about the details
to learn why it works for you but not for me.
I don't find anything in the CUPS 1.3.7 CHANGES.txt file
which indicates that CUPS 1.3.7 is less strict regarding
which encodings it accepts so that from my point of view
it is still the same:
Since CUPS 1.3.4 all communication with the cupsd must
happen in any case only in UTF-8 encoding or 7-bit ASCII.
This means
- a client which talks to the cupsd must use UTF-8 encoding
- all strings which are sent to the cupsd must be in UTF-8
in particular stuff like file names, queue names, job title,...
- all strings which the cupsd responds are in UTF-8
in particular stuff like queue state messages,...
- all input files which are sent to the cupsd must be in UTF-8
in particular files with MIME type text/plain
It does not work with CUPS 1.3.7 for us, /bugzilla. novell. com/show_ bug.cgi? id=386853
see for example
https:/
Does it work for you with CUPS 1.3.7?
If yes, I am very interested about the details
to learn why it works for you but not for me.
I don't find anything in the CUPS 1.3.7 CHANGES.txt file
which indicates that CUPS 1.3.7 is less strict regarding
which encodings it accepts so that from my point of view
it is still the same:
Since CUPS 1.3.4 all communication with the cupsd must
happen in any case only in UTF-8 encoding or 7-bit ASCII.
This means
- a client which talks to the cupsd must use UTF-8 encoding
- all strings which are sent to the cupsd must be in UTF-8
in particular stuff like file names, queue names, job title,...
- all strings which the cupsd responds are in UTF-8
in particular stuff like queue state messages,...
- all input files which are sent to the cupsd must be in UTF-8
in particular files with MIME type text/plain
See also: /bugzilla. novell. com/show_ bug.cgi? id=387130
https:/
and follow the links therein.