Content deleted Content added
Undid revision 1296400116 by Spitzak (talk). You're not right. Each keyboard layout have a associated codepage (TranslateCharsetInfo() call with TCI_SRCLOCALE flag is used under the hood to get it). And it is used for hex input with Alt+0### combinations. Not "system locale". |
Undid revision 1297175778 by Dimitriy Ryazantcev (talk)Correct it is not called the "system locale" |
||
Line 19:
* The familiar Alt+### combination (where ### is from 0 to 255) retains the old [[MS-DOS]] behavior, i.e., generates characters from the legacy code pages now called "[[Windows code page#OEM code page|OEM code pages]]." For instance, the combination {{key press|Alt}}+{{key press|1}}{{key press|6}}{{key press|3}} would result in {{char|ú}} (Latin letter u with [[acute accent]]) which is at 163 in the OEM code page of CP437 or CP850.<ref name="WindowsAltAlgo" /> This did not work for characters not in the Windows Code Page (such as box-drawing characters).
* The new Alt+0### combination (which prefixes a zero to each Alt code), produces characters from the newer [[Windows code page#ANSI code page|Windows code pages]].{{efn|Microsoft initially referred to them as "ANSI" code pages, but later acknowledged that this as a misnomer.}}
* Users could change either or both of these code pages, in which case the numbers produced different characters. For instance if the Windows Code Page [[CP1251]] (Cyrillic) is active, {{key press|Alt}}+{{key press|0}}{{key press|1}}{{key press|6}}{{key press|3}} produces [[Je (Cyrillic)]] (Ј).
==Unicode==
|