From owner-freebsd-hackers Thu Aug 1 00:19:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02190 for hackers-outgoing; Thu, 1 Aug 1996 00:19:56 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA02185 for ; Thu, 1 Aug 1996 00:19:52 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id KAA14636; Thu, 1 Aug 1996 10:22:46 +0300 Date: Thu, 1 Aug 1996 10:22:45 +0300 (EET DST) From: Narvi To: Terry Lambert cc: Robert Nordier , terry@lambert.org, hackers@freebsd.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-Reply-To: <199608010044.RAA03051@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 31 Jul 1996, Terry Lambert wrote: > > For completeness, any thoughts on how to handle the following? > > > > Directory containing 3 single-character DOS filenames 0xc3..0xc5: > > > > SFN LFN > > c3 251c > > c4 2500 > > c5 253c > > > > AFAIK, DOS filenames containing characters >= 0x80 have never been > > much used, or had much practical value. So extensive special > > provision for them almost seems misplaced. Actually they have at least around here. People just like to have filenames with all those a", o", u" and even o~ (although that is one which indeed does make troubles). Nothing ever happened except that nczip refuses to pack them up. > > IBM Code page 819(?) is ISO 8859-1. > > I think you are allowed to have high bit characters in long file names > (I will check this at next opportunity). > You can at least have them there. Sander > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. >