Doug Lytle writes:
> So, Samba is converting the weird characters to normal ASCII values.
> The Arched a is converted to an Upper case A and the same with the
> arched lower case a.
> Hence, the file not found error.
> Still trying to work out whats going on, if it's a client end issue or a
> Samba issue.
> Anybody have suggestion?
This is from the docs, based on input from GFK.
Also, to make sure that file names with 8-bit characters are
correctly transferred by smbclient you should add this to
samba's smb.conf file for samba 2.x:
# Accept the windows charset
client code page = 850
character set = ISO8859-1
For samba 3.x this should instead be:
unix charset = ISO8859-1
This setting should work for western europe. See
for more information about settings for other languages.
I don't know anything about charsets and i18n setup for smb.
Hence the reported problems people have with either backing
up or CGI rendering of international charsets.
This would be a great area for someone who knows what they are
doing to submit improvements.