From owner-freebsd-hackers Thu Aug 1 10:09:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25397 for hackers-outgoing; Thu, 1 Aug 1996 10:09:06 -0700 (PDT) Received: from eac.iafrica.com (196-7-101-138.iafrica.com [196.7.101.138]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA25391 for ; Thu, 1 Aug 1996 10:09:00 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id TAA00498; Thu, 1 Aug 1996 19:06:48 +0200 From: Robert Nordier Message-Id: <199608011706.TAA00498@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: hackers@freebsd.org Date: Thu, 1 Aug 1996 19:06:47 +0200 (SAT) Cc: terry@lambert.org, narvi@haldjas.folklore.ee, ache@nagual.ru X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > 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. Sander wrote: > 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. and Andrey A. Chernov wrote: > It isn't true, nationalized Win95 versions actively use it. > F.e. Win95 Russian Edition use Russian (CP866) names > for many folders/files. > There is yet one interesting thing: DOS national charset > used, not Windows one. For Russian Windows charset (CP1251) > is different with DOS one (CP866). So Win95 does special efforts > to convert between charsets. Thanks for this feedback. I was evidently completely wrong on this issue. -- Robert Nordier