Subject: Re: [netatalk-admins] Hrm.... 8-bit character codes "file doesn't exist" problems...
From: Nicholas Riley (nriley@staff.feldberg.brandeis.edu)
Date: Thu Nov 12 1998 - 20:36:24 EST
On Fri, Nov 13, 1998 at 10:33:02AM +1000, PayPC System Mail Subscriber wrote:
> Maybe this is a "stupid" answered-in-a-FAQ question... but with 2.1.0a and
> 8.5 (3.8.1 ASIP clients).... does anyone else get "file doesn't
> exist" errors
Yes... it displays fine, it is manipulated very badly. I'm guessing
this is because netatalk encodes the character into colon-notation
(e.g. :b5 for a mu) and when confronted with the real 8-bit character,
afpd backward-translates and comes up with no file. (An easy way to
see this - make an alias of the errant file on the Mac; the operation
will fail, but take a look at the filename). I guess the best solution
would be a switch that turns off the colon-characters and just uses
straight 8-bit characters when the Mac sends them.
> So.... do I need a magic 8-bit filename flag to be enabled? Or am
> I hosed here? It's a major pain in the butt, between unix shells
> being very hostile to any filenames with spaces and magic characters
> in them, and netatalk not letting me at the files... etc. OY!
Hm. I don't have any trouble manipulating files named with 8-bit
characters with zsh, which is what I use. I just tried it with bash
and tcsh and they seemed much less friendly (didn't seem to let me
tab-complete a file like that, for example, if there was a file with a
similar name).
-- Nicholas Riley <nriley@staff.feldberg.brandeis.edu>
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:33:42 EST