these options are already correct by default, as "testparm -v" says:
unix charset is UTF8, dos charset is 850 and display charset is LOCALE.
Since smbclient and gvfsd work just perfect with umlauts, I think the problem is either the kernel module or mount.cifs.
Probably the kernel module, as the non-utf8-umlaut turns up in /proc/mounts (where it then causes gnomevfsd to fail to start, because it passes this data via dbus and then dbus seems to kill the connection, which is very bad).
Hi,
these options are already correct by default, as "testparm -v" says:
unix charset is UTF8, dos charset is 850 and display charset is LOCALE.
Since smbclient and gvfsd work just perfect with umlauts, I think the problem is either the kernel module or mount.cifs.
Probably the kernel module, as the non-utf8-umlaut turns up in /proc/mounts (where it then causes gnomevfsd to fail to start, because it passes this data via dbus and then dbus seems to kill the connection, which is very bad).