Hi.

I'm using Linux and sometimes also Windows XP to access a Linkstation
HD-HLAN250 NAS device and found, that filenames with "special 
characters" like ä, ö, ü, ß, € etc.pp. get messed up "on the other 
OS" when I transfer those files to the SMB share on the NAS device.

What I mean with this is, that I can copy/create a file from Linux
on the LS called "blöder name" just fine. But when I access the share
with XP, that filename is shown as "blöder name" instead. And when I
create a file with such a name from Windows, it shows up in Linux as 
"bl?der name" (that's what "ls" shows - I suppose that's not a real
question mark (?) though).

On my Linux boxes, I use Unicode everywhere. Hence the "special" (ie.
non-ASCII) characters are two chars wide (ie. ö instead of ö). To
mount the share on the HD-HLAN, I've got the following in my fstab:

//HD/share /HD/TEST smbfs noauto,credentials=/local/conf/hd-credentials,uid=guest,gid=users,fmask=0775,dmask=0775,workgroup=EU ROPE,rw,lfs,iocharset=unicode,codepage=iso8859-15 0 0

In the Basic Setup of the LS, I set ISO8859-15 as the character code.
I can only chose between some cp codepages (cp850, cp437, ...) and
iso8859-1, iso8859-15 and some other ISOs. cp850, iso-8859-1 and
iso-8859-15 are the only options relevant for me (ie. I don't care
about eg. japanese characters).

How do I have to setup everything, so that I can use non-ASCII
characters from every OS?

The HD-HLAN only offers SMB and FTP access; ie. no NFS :( Oh,
when I copy the file "blöder name" with ftp (lftp) to the NAS
device, the file name also get's messed up...

Thanks,

Alexander Skwar

PS: NOT using special characters is not an option :)
-- 
This was a Golden Age, a time of high adventure, rich living, and hard
dying... but nobody thought so.  This was a future of fortune and theft,
pillage and rapine, culture and vice... but nobody admitted it.
                -- Alfred Bester, "The Stars My Destination"

· me:

> What I mean with this is, that I can copy/create a file from Linux
> on the LS called "blöder name" just fine. But when I access the share
> with XP, that filename is shown as "blöder name" instead. And when I
> create a file with such a name from Windows, it shows up in Linux as 
> "bl?der name" (that's what "ls" shows - I suppose that's not a real
> question mark (?) though).

Hm.

Thanks to OpenLink firmware from http://linkstationwiki.org/, I've
now got root access via ssh/telnet to the box. In the smb.conf
of the NAS device, I find:

    client code page = 850
    character set = ISO8859-15

It is running:

root@HD:~# /usr/sbin/smbd -V
Version 2.2.8a-ja-1.1

To what values should I change that?

Thanks again,

Alexander Skwar
-- 
Bad Cockroach: Man, I'm going to cut you up so bad, that you... you gonna wish I
didn't cut you up so bad.

On Sun, 06 Nov 2005 10:03:38 +0100, Alexander Skwar
  <alexander@skwar.name> wrote:
>
> On my Linux boxes, I use Unicode everywhere. Hence the "special" (ie.
> non-ASCII) characters are two chars wide (ie. ö instead of �). To
> mount the share on the HD-HLAN, I've got the following in my fstab:
>
> //HD/share /HD/TEST smbfs noauto,credentials=/local/conf/hd-credentials,uid=guest,gid=users,fmask=0775,dmask=0775,workgroup=EU ROPE,rw,lfs,iocharset=unicode,codepage=iso8859-15 0 0
>
Try "iocharset=utf-8".


-- 
The first myth of management is that it exists.  The second myth of
management is that success equals skill.
		-- Robert Heller

Alexander Skwar schrieb:

> Thanks to OpenLink firmware from http://linkstationwiki.org/, I've
> now got root access via ssh/telnet to the box.

And this allowed me to finally install NFS on it. With
NFS, I can now easily and successfully create filenames
with non-ASCII characters, like "blöder name". But
when I access the share from Windows (or rather: via
SMB), the filenames are still mangled :(

What I'm after is a way for Samba to transform filenames
from the stored (on disk) UTF-8 name to cp850 (or
whatever).

The NAS box is running Samba 2.2.8a.

Can Samba 2.2.8a do this? With Samba 3, this would be
possible, wouldn't it?

If Samba 2 could do this, how/what would I configure?
I suppose "client code page" and "character set" are
the relevant settings? What are the allowed values for
"character set"?

Are the "nftable" files in /usr/share/codepage the allowed
values? If so, then Samba 2 (or at least that installation)
doesn't handle UTF-8; only iso-8859-x and some cpX values.

Or would "find /lib/modules/$(uname -r) -name nls*.o" reveal
me the allowed values? If so, "UTF8" would be a good value -
but even with "character set = UTF8", I can't get a good
translation. "blöder name" translates to "bl├Âder name"
on Windows :(

Can Samba 2 do UTF-8 filename translation?

Thanks,

Alexander Skwar