From owner-freebsd-hackers Wed Aug 26 12:43:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03170 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 12:43:34 -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 MAA03165; Wed, 26 Aug 1998 12:43:32 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA11518; Wed, 26 Aug 1998 12:42:41 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma011514; Wed Aug 26 12:42:29 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA23260; Wed, 26 Aug 1998 12:42:29 -0700 (PDT) From: Archie Cobbs Message-Id: <199808261942.MAA23260@bubba.whistle.com> Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: from Stefan Bethke at "Aug 25, 98 10:18:49 pm" To: stb@hanse.de (Stefan Bethke) Date: Wed, 26 Aug 1998 12:42:29 -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 Stefan Bethke writes: > 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. -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