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=-0.5 required=5.0 tests=BAYES_00,INVALID_MSGID,
	PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: 103376,3accd44abeec75ee
X-Google-Attributes: gid103376,public
From: "Pascal Obry" <p.obry@der.edf.fr>
Subject: Re: DOS/Win95 file names
Date: 1999/06/11
Message-ID: <7jqfkg$nfu$1@clnews.edf.fr>#1/1
X-Deja-AN: 488297411
References: <375fd4b4.608956077@news.dsuper.net>
 <3760B4CC.6E84F2F6@Maths.UniNe.CH>
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Organization: EDF
X-MSMail-Priority: Normal
Newsgroups: comp.lang.ada
Date: 1999-06-11T00:00:00+00:00
List-Id: <comp.lang.ada>


Gautier <Gautier.deMontmollin@Maths.UniNe.CH> a �crit dans le message :
3760B4CC.6E84F2F6@Maths.UniNe.CH...
> 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.
>

Well that's not so bad for a Microsoft product :-)

Pascal.