From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,3accd44abeec75ee
X-Google-Attributes: gid103376,public
From: Gautier <Gautier.deMontmollin@Maths.UniNe.CH>
Subject: Re: DOS/Win95 file names
Date: 1999/06/11
Message-ID: <3760B4CC.6E84F2F6@Maths.UniNe.CH>#1/1
X-Deja-AN: 488266645
Content-Transfer-Encoding: 7bit
References: <375fd4b4.608956077@news.dsuper.net>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-06-11T00:00:00+00:00
List-Id: <comp.lang.ada>

It's Windows in all its glory: the console has one
character set (437, 850 or so); Windows itself uses
another one... There is a DOS upper case function
that upcases the filenames but with which character
set, the same way or not under plain DOS or under
Windows... A possibility is to have an explicit
translation table; the best one is to forbid
accents in filenames: you could add to your exception
handling such a warning.

-- 
Gautier

--------
http://members.xoom.com/gdemont/