Re: MS Command Prompt
At 09:31 AM 3/8/02 -0500, Patrick Rourke wrote: Don't know if this will help any with NT. I am using Lucida console on all my command prompt windows, so that's the reason I could never see the problem. You can set properties like font and color for the command prompt and have that information be associated with the shortcut you use to launch the window, or for windows that have the same title. That seems to work well for many kinds of command prompts. A./
MS Command Prompt
From: Doug Ewell [EMAIL PROTECTED] 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. In Windows XP, if I type the Alt+0248 in the command prompt with the font set to raster fonts, I get an o. If I type it in a command prompt with the font set to Lucida Console, I get the ø. However, it only works if I change the font before I type the character. So I am guessing that in XP, whatever code page you have selected, if the default font for the command line doesn't have the character you want, you're stuck with the closest approximation in that font. Don't know if this will help any with NT. Patrick Rourke [EMAIL PROTECTED]
Re: MS Command Prompt
Patrick Rourke [EMAIL PROTECTED] wrote: In Windows XP, if I type the Alt+0248 in the command prompt with the font set to raster fonts, I get an o. If I type it in a command prompt with the font set to Lucida Console, I get the ø. However, it only works if I change the font before I type the character. So I am guessing that in XP, whatever code page you have selected, if the default font for the command line doesn't have the character you want, you're stuck with the closest approximation in that font. I hadn't thought of that. In Windows 2000 I am using Lucida Console, while my colleague's NT 4 computer on which I conducted the test was using the Terminal bitmap font. I didn't know the NT 4 system was doing substitutions based on what was available in the font, but it seems that's what's happening. Thanks for the info. -Doug Ewell Fullerton, California
MS Command Prompt
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 [EMAIL PROTECTED] NT Desktop Support European Central Bank -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- (End of Report)
Re: MS Command Prompt
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 Ã. 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 [EMAIL PROTECTED] NT Desktop Support European Central Bank -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- (End of Report)
Re: MS Command Prompt
At 11:45 PM 3/7/02 +, 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-0248 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 [EMAIL PROTECTED] NT Desktop Support European Central Bank -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- (End of Report)
Re: MS Command Prompt
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 [EMAIL PROTECTED] To: Martin Kochanski [EMAIL PROTECTED]; Magda Danish (Unicode) [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, March 07, 2002 4:28 pm Subject: Re: MS Command Prompt At 11:45 PM 3/7/02 +, 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-0248 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 [EMAIL PROTECTED] NT Desktop Support European Central Bank -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- (End of Report)
