From owner-freebsd-hackers Wed Jul 31 16:28:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA12627 for hackers-outgoing; Wed, 31 Jul 1996 16:28:09 -0700 (PDT) Received: from eac.iafrica.com (196-7-192-148.iafrica.com [196.7.192.148]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA12610 for ; Wed, 31 Jul 1996 16:28:03 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id BAA00549; Thu, 1 Aug 1996 01:25:59 +0200 From: Robert Nordier Message-Id: <199607312325.BAA00549@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@lambert.org (Terry Lambert) Date: Thu, 1 Aug 1996 01:25:57 -2200 (SAT) Cc: hackers@freebsd.org In-Reply-To: <199607311829.LAA02458@phaeton.artisoft.com> from "Terry Lambert" at Jul 31, 96 11:29:44 am X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: [...] (Still digesting other comments. :) > I can't help with the Unicode stuff given the current state of the BSD > VFS; my suggestion is to punt, and treat the high byte as zero in all > cases, converting it to ISO-8859-1 (Latin 1). This will damage utility > for anyone outside the Latin 1 scope, but that can't be helped without > the underlying VFS changes (appologies to non-Latin 1 using countries > up front). Agreed. 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. -- Robert Nordier