Date: Wed, 26 Aug 1998 15:56:59 -0700 (PDT) From: Archie Cobbs <archie@whistle.com> To: stb@hanse.de Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Warning: Change to netatalk's file name handling Message-ID: <199808262256.PAA28628@bubba.whistle.com> In-Reply-To: <199808261942.MAA23260@bubba.whistle.com> from Archie Cobbs at "Aug 26, 98 12:42:29 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
I wrote: > > As you might be aware, Mac's tend to use characters in file names usually > > not used on UN*X systems, namely in the range \0x01-\0x1F and \0x7f-\0xff. > > > > Especially annoing is the "Icon\0x0D" for Custom Icons on Folders or > > Volumes. > > > > I will put a patch in the netatalk port that maps all characters outside > > of \0x20 to \0x7E (aka isprint()) to the equivalent hex ":xx" sequence. > > I don't quite understand the motivation for changing netatalk. UNIX > supports arbitrary characters in file names, so why not use it? > > If you want file names decoded in a directory listing, use "ls -B". > > Netatalk seems like the wrong place to modify behavior to solve this > problem, which is a display problem, not an encoding problem. Or, at least make it controlled by a optional command line option... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808262256.PAA28628>