From owner-freebsd-hackers Wed Aug 26 16:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13755 for freebsd-hackers-outgoing; Wed, 26 Aug 1998 16:16:14 -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 QAA13713 for ; Wed, 26 Aug 1998 16:15:57 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA13989; Wed, 26 Aug 1998 16:15:07 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma013985; Wed Aug 26 16:15:04 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id QAA08454; Wed, 26 Aug 1998 16:15:04 -0700 (PDT) From: Archie Cobbs Message-Id: <199808262315.QAA08454@bubba.whistle.com> Subject: Re: Warning: Change to netatalk's file name handling In-Reply-To: from Stefan Bethke at "Aug 27, 98 00:56:38 am" To: stb@hanse.de (Stefan Bethke) Date: Wed, 26 Aug 1998 16:15:04 -0700 (PDT) Cc: freebsd-hackers@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: > > 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. > > Where is the encoding defined for character values in the ranges between > \0x01 to \0x1f, and \0x7f to \0xff in terms of UFS, POSIX, whatever? > > If you were right, it would be OK for afpd to store all chars literally. > While this does work, it is definitly awkward to work with in the shell, > and possibly so together with other applications as Samba as well. Its not > merely an display issue; its an interoperability issue. I feel that too > many things expect file names to confine to printable ascii, and unless > this changes, I opt to fix what in my eyes is an obvious bug in afpd (that > is, escaping \0x80 to \0xff, but leaving \0x01 to \0x1f and \0x7f > untouched). I guess that makes sense, if netatalk is already escaping 0x80-0xff in the same way.. This goes deeper of course... ie, a byte is not the same thing as a character, and the question is, what is the character set and what is the encoding between a character and one or more bytes? Julian's right, in that you should query Jeremy about this for more complete info (but probably only for amusement value :-) [ On the InterJet, for example, you can have it set to Japanese mode, and shared files appear with the same name under AppleTalk and Windows, ie, Samba and Netatalk use the same character encoding. ] -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