From owner-freebsd-hackers Thu Aug 27 15:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12360 for freebsd-hackers-outgoing; Thu, 27 Aug 1998 15:12:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12288 for ; Thu, 27 Aug 1998 15:11:43 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA25475; Thu, 27 Aug 1998 15:10:48 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd025433; Thu Aug 27 15:10:42 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id PAA27928; Thu, 27 Aug 1998 15:10:33 -0700 (MST) From: Terry Lambert Message-Id: <199808272210.PAA27928@usr02.primenet.com> Subject: Re: Warning: Change to netatalk's file name handling To: stb@hanse.de (Stefan Bethke) Date: Thu, 27 Aug 1998 22:10:33 +0000 (GMT) Cc: archie@whistle.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Stefan Bethke" at Aug 27, 98 00:56:38 am X-Mailer: ELM [version 2.4 PL25] 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 > > 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? ISO 8859? > 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). Per interoperability: This presumes, incorrectly, that Mac's support the same idiotic idea of code pages as SAMBA must. > It won't change anything to the worse; the only problem is that existing > files with file names containing control characters (custom icons on folders > being the single source of such name probably) will stop working and will > need manual assistance from an operator. It will break a number of things. It already breaks the file name length limitation in SAMBA. Duplicating this break into Appletalk is, IMO, a bad idea. If you are going to push this hard, you should consider Internataional representation ofile names by client locale, and how it is already handled. Novell servers are another case where the server assumes all clients exist in a given locale; this would be a mistake to buy into... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message