[cups.general] CUPS 1.3.x: really can't print PCL files inlatin iso-8859-1 any longer??

[Michael Sweet]

No, for CUPS 1.1.x it is entirely up to the locale CODESET and the  
default character set in the message catalogs - DefaultCharset is only  
used when responding to a bad request that does not contain the  
attributes-charset attribute.

On Mar 10, 2009, at 11:25 AM, Tim Waugh wrote:

> ekkard gerlach wrote:
>> Michael R Sweet schrieb:
>>> This only affects printing of plain text files, not other file  
>>> formats  which embed the necessary character set information.
>> I've tested PCL files and postscript 1.0 files. Both don't work.  
>> Convertation with iconvs doesn't work. Printing from Suse 10.2  
>> (CUPS 1.2.7) to Suse 11.1 (CUPS 1.3.7). A week before a Suse 8.2  
>> machine
>> worked properly.
>
> I think the confusion here is that even with a correctly-encoded  
> *file*, the IPP *request* sent to the server needs to be encoded in  
> UTF-8.  In other words, clients with a system character encoding  
> other than UTF-8 are going to have problems talking to recent CUPS  
> servers.
>
> I *think* the DefaultCharset cupsd.conf option can be used on the  
> client to overcome this -- can anyone confirm?
>
> Tim.
> */
>
> _______________________________________________
> cups mailing list
> cups at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups

________________________________________
Michael R Sweet, Senior Printing System Engineer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20090310/094c31e9/attachment-0001.html>