Actually, other character sets also exists:
>
> This allows a smbd to map incoming filenames from a DOS Code page (see
> the client code page parameter) to several built in UNIX character
> sets. The built in code page translations are:
>
>
>
> ISO8859-1 Western European UNIX character set.
It's fixed.
I added, in my smb.conf, the folowwing parameters:
character set = ISO8859-1
client code page = 850
Thanks a lot for that feedback!
--
Michael
---
Help translate SlimServer by using the
SlimString Translation Helper (http://w
It's fixed.
I added, in my smb.conf, the folowwing parameters:
character set = ISO8859-1
client code page = 850
See below the informations coming from Samba2 helpfile:
>
> character set (G)
> This allows a smbd to map incoming filenames from a DOS Code page (see
> the client code page parameter
Did you experience that kind of problem with your files ?
I guess you have files with umlaut and it should not appear correctly
looking from a windows computer.
I'm not using samba, but rsync to keep the server up to date (the main
server is a linux box, too). And I'm not enough into samba to
Did you experience that kind of problem with your files ?
I guess you have files with umlaut and it should not appear correctly
looking from a windows computer.
I will search with "codepages" of samba 2.
--
Mathiou
Do you know Viaduc: http://www.viaduc.com/invitation/00219a2skr26usth
