>Received:	from belous by muhost.munic.msk.su id aa15761; 8 Sep 2002 15:33 MSD
To:	opendos AT delorie DOT com
X-Comment-To:	shadow AT krypton DOT rain DOT com
References:	<20020908 DOT 002529 DOT 7C6 DOT rnr DOT w165w AT krypton DOT rain DOT com>
Message-Id:	<2.7.9.MXES.H24A6M@belous.munic.msk.su>
From:	"Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su>
Date:	Sun, 8 Sep 2002 15:20:46 +0400 (MSD)
Organization:	Locus
X-Mailer:	dMail [Demos Mail for DOS v2.7.9]
Subject:	Re: NLS and lowercase
MIME-Version:	1.0
X-MIME-Autoconverted:	from 8bit to quoted-printable by postbox.mos.ru id g88BXdC04254
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g88BXiw29408
Reply-To:	opendos AT delorie DOT com

X-Comment-To: shadow AT krypton DOT rain DOT com

Hi!

8-σΕΞ-2002 00:25 shadow AT krypton DOT rain DOT com (shadow AT krypton DOT rain DOT com) wrote to
opendos AT delorie DOT com:

>>      Are someone know why MS gives in its API two different upcase tables -
>> "uppercase table" (INT 21/6502) and "filename uppercase table" (6504) and
>> what there may differ?
src> Because there are some characters allowed in documents that aren't
src> allowed in filenames.

     Hm, very good point. (I know $E5, at least).

>>      Also, why they usually not contains "lowercase table" (6503) and not
>> provide "make lower case" (similar to 6520-6522) nor "filename lowercase
>> table" at all?
src> Because they need to convert to uppercase sometimes, but never do the
src> reverse operation

     ...but there is (?) 6503 function!

src> (and, in fact, I seem to vaguely recall that there is
src> no way to determine what the proper lowercase is for some uppercase
src> characters with a table. only by knowing the language)

     Not for all languages. Fortunately, in Cyrillic maping is unambiguite
in both directions.

- Raw text -