>Received: by krypton.rain.com (rnr)
       via rnr; Sun, 8 Sep 2002 00:25:29 -0800
To: opendos AT delorie DOT com
X-Original-Message-From: "Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su>
Subject: Re: NLS and lowercase
From: shadow AT krypton DOT rain DOT com (Leonard Erickson)
Message-ID: <20020908.002529.7C6.rnr.w165w@krypton.rain.com>
Date: Sun, 8 Sep 2002 00:25:29 -0800
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <2.7.9.4NWT.H1XJQG@belous.munic.msk.su>
Organization: Shadownet
User-Agent: rnr/2.50
Received: from krypton by qiclab.scn.rain.com; Sun,  8 Sep 2002 03:07 PDT
Content-Type: text/plain; charset=iso-8859-1
Reply-To: opendos AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: opendos AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

In mail (last Thursday) you write:

>      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?

Because there are some characters allowed in documents that aren't
allowed in filenames.

>      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?

Because they need to convert to uppercase sometimes, but never do the
reverse operation (and, in fact, I seem to vaguely recall that there is
no way to determine what the proper lowercase is for some uppercase
characters with a table. only by knowing the language)

-- 
Leonard Erickson (aka shadow{G})
 shadow AT krypton DOT rain DOT com        <--preferred
leonard AT qiclab DOT scn DOT rain DOT com     <--last resort