This issue is not about 16-bit vs. 32-bit applications, but specifically
the command prompt (a.k.a. MS-DOS prompt).
Indie was doing the right thing by typing Alt+0248 to get the Latin-1
character, instead of Alt+248 to get the MS-DOS character. That isn't
the problem.
In Windows 95, 98, and NT 4, everything that happens in the command
prompt goes through the MS-DOS code page -- 437, 850 or whatever. Since
Indie's code page is set to 437, and U+00F8 LATIN SMALL LETTER O WITH
STROKE is not in code page 437, the internal conversion tables in NT 4
converted 'ø' to 'o', a reasonable if imperfect fallback. Note that
Alt+0243 works just fine, because U+00F3 is in code page 437. Also note
that if Indie had been using 850 instead of 437, there would have been
no problem, since 850 does include U+00F8.
Windows 2000 is different. You can set your command prompt code page to
437 and type Alt+0248, and you will still get the 'ø' you want. The
Alt+0xxx logic has been decoupled from the active code page issue, which
is nice.
Martin is right, you can change the code page; but I don't know if that
will help Indie. What's kind of fun is that in Windows 2000, you can
change your code page to 65001 and do all your command-prompt work in
UTF-8.
-Doug Ewell
Fullerton, California
Command Prompt Junkie
----- Original Message -----
From: "Asmus Freytag" <asmusf@ix.netcom.com>
To: "Martin Kochanski" <unicode@cardbox.net>; "Magda Danish (Unicode)"
<v-magdad@microsoft.com>; <unicode@unicode.org>
Sent: Thursday, March 07, 2002 4:28 pm
Subject: Re: MS Command Prompt
At 11:45 PM 3/7/02 +0000, Martin Kochanski wrote:
>This is because the MSDOS Prompt is using Code Page 850 rather than
Code
>Page 1252.
>
>248 in CP 850 is ° and in CP1252 is ø.
>195 in CP 850 is a line-drawing character and in CP1252 is Ã.
But typing ALT-"0"248 does generate the correct character when I try it.
ALT-248 without the 0 would generate the MS-DOS character. I've tried it
on
NT4 and could not reproduce the problem (*unless* it's not in the
command
prompt itself, but in another *application* that's run under the command
prompt, and then who knows what they do to the character.)
A./
PS: I tried to answer Indie.Toor directly, but got an error message
back.
>You may be able to use the CHCP command to change the code page you are
>using, but I don't know very much about this.
>
>At 10:00 07/03/02 -0800, Magda Danish (Unicode) wrote:
> >
> >I have MS Windows NT 4 installed with Service Pack 6a on several PCs.
> The keyboard is set to English (United States). Within all 32-bit
> applications ALT-0248 "ø" is working fine. However, within a MS
Command
> Prompt the above ALT does not work and I get a "o" instead. The keyb
in
> MS DOS is set to "us 437". This means that the ALT-0248 does not work
in
> 16-bit applications.
> >
> >Any help would be much appreciated.
> >
> >Indie Toor
> >Indie.Toor@ecb.int
> >NT Desktop Support
> >European Central Bank
> >
> >-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> >(End of Report)
> >
> >
> >
> >
This archive was generated by hypermail 2.1.2 : Fri Mar 08 2002 - 00:09:59 EST