From owner-freebsd-hackers Wed Aug 26 15:57:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09464 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 15:57:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09449; Wed, 26 Aug 1998 15:57:54 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA13715; Wed, 26 Aug 1998 15:57:05 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma013713; Wed Aug 26 15:56:59 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA28628; Wed, 26 Aug 1998 15:56:59 -0700 (PDT) From: Archie Cobbs Message-Id: <199808262256.PAA28628@bubba.whistle.com> Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: <199808261942.MAA23260@bubba.whistle.com> from Archie Cobbs at "Aug 26, 98 12:42:29 pm" To: stb@hanse.de Date: Wed, 26 Aug 1998 15:56:59 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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-hackers" in the body of the message