no Umlaut in filenames from smbmount by default

[Jörg Höhle]

Binary package hint: smbfs

Hi,
The Gnome desktop network mounter, the smbclient and a native MS-Windows-2k manage to display Umlaute in filenames from a Linux Samba server just fine.
Using smbmount however, an ls command merely displays "?" in lieu of the Umlauts in concerned filenames.

Trying out many combinations of iocharset and codepage options I finally got Umlaute to display fine as follows:
mount -t smbfs -o username=xyz,uid=hoehle,gid=hoehle,file_mode=0640,codepage=cp437,iocharset=utf8 //10.0.0.79/hoehle /mnt/samba
which seems equivalent to:
smbmount //10.0.0.79/hoehle /mnt/samba -o username=xyz,uid=hoehle,gid=hoehle,file_mode=0640,codepage=cp437,iocharset=utf8

codepage=utf8,iocharset=utf8 produces :x84 :x9a for some umlauts in ls output.
codepage=iso8859-1 produces :0084 :009a instead.
codepage=cp437, utf16 or utf-16 produce "?" instead.

codepage=cp852,iocharset=utf8 finally works.
codepage=cp437,iocharset=utf8 also works.
Note that the iocharset option must be given as well.

man mount on fat says: "By default, codepage 437 is used."
For consistency, I'd expect similar defaults with smbfs.
Similarly, I'm quite surprised that iocharset=utf8 is needed. I'd thought most Linux software did the transition to UTF-8 these days (since Hoary, Warty was not fully there).

smbfs should be as easy to use and provide similar defaults as all of smbclient, the Gnome desktop and MS-Windows do.

Affects: Dapper with http://wiki.ubuntu.com/LaptopTestingTeam/FujitsuLifebookC1110

Regards,
 Jörg Höhle

[Daniel Werner (demitsu)]

> codepage=cp852,iocharset=utf8 finally works.
> codepage=cp437,iocharset=utf8 also works.
> Note that the iocharset option must be given as well.

Thanks a lot for these hints -- umlauts are converted correctly at my site, at last. Specifying the encoding as 'utf8' instead of 'utf-8' did the trick. However, I still don't get why smbmount didn't complain about the superfluous dash. Actually, it will happily accept even 'utf66' or 'foobar', only to silently ignore it.

I fully agree with you on this matter, Jörg: More sensible defaults could spare some trouble.

[Chuck Short (zulcss)]

This should be fixed in lucid. Thanks for the bug report.