On Tue, Jan 29, 2008 at 06:08:04PM +0100, Elmar Haneke wrote: >> Can you check what you currently >> have for your 'dos charset', 'unix charset', and 'display charset' settings >> in smb.conf?
> unix charset = iso8859-15 > "dos charset" and "display charset" are not set. > Is it realy required to rename files on disk to resolve this problem? Since it appears to be the 'display charset' which governs interaction with CUPS, probably not. >> Your 'display charset' value may be set to 'LOCALE'. I see that you filed >> the bug report from a UTF-8 locale, but is it possible that other users on >> your system (e.g., root) are still using an ISO8859-1 locale? > How can I check this? > Is it sufficient to reconfigure locales package and reboot afterwards? When you sent your initial bug report, reportbug listed "de_DE.UTF-8" as your locale. Was this on the machine where you experienced the problem? If so, it should be sufficient for you to run: LANG=de_DE.UTF-8 /etc/init.d/samba restart to test whether this fixes your problem. If it does, then I guess you need to reconfigure your locale so that the change is persistent across reboots. Thinking about this report, it's my opinion that this is a bug in Samba. We know that CUPS 1.3.5 and above require UTF-8, so Samba should always use UTF-8 when talking to CUPS, regardless of the display charset setting. If you can confirm that the above changes fix the problem for you, I'll forward the report upstream. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
