Subject: [netatalk-admins] SAMBA + netatalk [funky character set interchanges] more data
From: PayPC System Mail Subscriber (spammail@quanta.paypc.com)
Date: Wed Jun 16 1999 - 00:04:58 EDT
> Using the latest release netatalk+asun (2.1.3 I think), Linux 2.0.36, and
> Samba 2.0.4b.... I get strange mojo when using any of the Macintosh "high"
> ASCII characters in file names.
>
> UNIX Name Macintosh Name SAMBA Name
> --------------- -------------- ----------
> MindExpander:aa MindExpanderª Minde~cn
I was able to test some changes [hooray! the "root" afpd doesn't need to be
restarted when you change AppleVolumes.default.
My tests with altering the NLS via the AppleVolumes.default proved
disastrous. All of the files with special "high-ascii" characters could not
be renamed once I tried the various NLS codepages. OUCH. Bad. The Finder
would let me try to rename the file, but the name would just "pop back" to
what it was. Only reverting the NLS page to the original (in my case, NO
specified NLS page) would let my Macintosh clients rename the files with
high-ascii. [the ones I'm referring to are the common ª and Ä [the TM symbol
and the cursive f used to often refer to Folders].
On the samba-side, I've had more luck with:
[removed the character set directive]
client code page = 437
codingsystem = CAP
At least the files are 1) accessible, and 2) show alot more like the real
filenames. Of course, the high-ascii are always WRONG on the Windows
machines, but at least I can rename them and open them.
Sheesh.
1) Shouldn't a Macintosh client be able to change and access files with
high-ascii created by a different NLS codepage? Sure, I expect the filename
to be "wrong" - but whatever it is, it should still be renameable!
2) Who is "mistranslating" the high-ascii? Is there some concordance for
translating the Macintosh high-ASCII to some "interlingua" format so that
Windows and UNIX/X folks see the desired character? I checked the Windows
character set maps, and they have both the Ä and ª [cursive f and TM
trademark], for example. What is involved to ensure that all three platforms
"see" the correct character. I'm not so worried about the UNIX-side, per se.
[I'm used to seeing :XX and the like].
Yow. I *cannot* be the first person to have stumbled over this. What are
peoples' solutions?
=R=
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:16:50 EST