Hi all,
Basically, we don't have anymore accented character support between windows &
linux, i.e. a file named "����.txt" from windows on a samba share will be
listed ".txt" in a terminal in the linux shared directory.
Tested on 8.1 with samba-2.2.3a(-5mdk): same problem with windows ME. The
samba team has not reacted yet, but the kernel hack seems to work.
Should it be integrated in cooker yet or should we wait for the samba team to
issue a patch?
cheers
Le Samedi 23 F�vrier 2002 18:16, vous avez �crit :
> Hello,
>
> Many people seems to experience the folowing problem :
>
> Since samba 2.2.3, on some system, one couldn't see accents in win2k share
> with smbmount but they can see them with smbclient.
>
> After a bit of work here's a working solution in the case of a french
> environment (checked on Debian testing):
>
> 1. use smbmount >= 2.2.3
> 2. your kernel must be compiled with:
>
> CONFIG_SMB_NLS_DEFAULT=y
> CONFIG_SMB_NLS_REMOTE="cp437"
> CONFIG_NLS_DEFAULT="iso8859-1"
> CONFIG_NLS_CODEPAGE_XX=m
>
> ---
>
> It seems that if there's no NLS_DEFAULT smbmount is unable to do the
> correct codepage->NLS translation even if playing with the "iocharset" and
> "codepage" options on the commandline.
>
> sbmclient (2.2.3) works well without CONFIG_SMB_NLS_DEFAULT and
> CONFIG_SMB_NLS_REMOTE nor it needs the CONFIG_NLS_DEFAULT="iso8859-1"
> ("cp437" works!).
>
> I hope this can help.
>
> Sebastien
