<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br><div><div>On Mar 10, 2009, at 11:25 AM, Tim Waugh wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>ekkard gerlach wrote:<br><blockquote type="cite">Michael R Sweet schrieb:<br></blockquote><blockquote type="cite"><blockquote type="cite">This only affects printing of plain text files, not other file formats which embed the necessary character set information.<br></blockquote></blockquote><blockquote type="cite">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<br></blockquote><blockquote type="cite">worked properly.<br></blockquote><br>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.<br><br>I *think* the DefaultCharset cupsd.conf option can be used on the client to overcome this -- can anyone confirm?<br><br>Tim.<br>*/<br><br>_______________________________________________<br>cups mailing list<br><a href="mailto:cups@easysw.com">cups@easysw.com</a><br>http://lists.easysw..com/mailman/listinfo/cups<br></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>________________________________________</div><div>Michael R Sweet, Senior Printing System Engineer</div></div></div></span></span>
</div>
<br></div></body></html>