From owner-freebsd-hackers Wed Jul 31 17:53:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17404 for hackers-outgoing; Wed, 31 Jul 1996 17:53:39 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA17399 for ; Wed, 31 Jul 1996 17:53:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA03097; Wed, 31 Jul 1996 17:51:58 -0700 From: Terry Lambert Message-Id: <199608010051.RAA03097@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@phaeton.artisoft.com (Terry Lambert) Date: Wed, 31 Jul 1996 17:51:58 +1700 (MST) Cc: rnordier@iafrica.com, terry@lambert.org, hackers@freebsd.org In-Reply-To: <199608010044.RAA03051@phaeton.artisoft.com> from "Terry Lambert" at Jul 31, 96 05:44:08 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 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. > > 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). Bad news: SFN LFN ASOLUTE asolute On Win95 ( is Greek Beta). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.