Windows code page




Windows code pages are sets of characters or code pages (known as character encodings in other operating systems) used in Microsoft Windows from the 1980s and 1990s. Windows code pages were gradually superseded when Unicode was implemented in Windows, although they are still supported both within Windows and other platforms.


There are two groups of code pages in Windows systems: OEM and ANSI code pages. Code pages in both of these groups are extended ASCII code pages.




Contents






  • 1 ANSI code page


  • 2 OEM code page


  • 3 History


  • 4 List


  • 5 Problems arising from the use of code pages


  • 6 See also


  • 7 References


  • 8 External links





ANSI code page



























Windows-125x series
Alias(es) ANSI (misnomer)
Standard WHATWG Encoding Standard
Extends US-ASCII
Preceded by ISO 8859
Succeeded by
Unicode
UTF-16 (in Win32 API)

  • v

  • t

  • e

ANSI code pages (officially called "Windows code pages"[1] after Microsoft accepted the former term being a misnomer[2]) are used for native non-Unicode (say, byte oriented) applications using a graphical user interface on Windows systems.


ANSI is a bit of a misnomer as the behavior does not exactly match the ANSI standards and other codepages can be selected, most recently UTF-8 Unicode.


ANSI Windows code pages, and especially the code page 1252, were so-called since they were purportedly based on drafts submitted or intended for ANSI. However, ANSI and ISO have not standardized any of these code pages. Instead they are either supersets of the standard sets such as those of ISO 8859 and the various national standards (like Windows-1252 vs. ISO-8859-1), major modifications of these (making them incompatible to various degrees, like Windows-1250 vs. ISO-8859-2) or having no parallel encoding (like Windows-1257 vs. ISO-8859-4; ISO-8859-13 was introduced much later).[2] About twelve of the typography and business characters from CP1252 at code points 0x80–0x9F (in ISO 8859 occupied by C1 control codes, which are useless in Windows) are present in many other ANSI/Windows code pages at the same codes. These code pages are labelled by Internet Assigned Numbers Authority (IANA) as "Windows-number".[3]



OEM code page


The OEM code pages (original equipment manufacturer) are used by Win32 console applications, and by virtual DOS, and can be considered a holdover from DOS and the original IBM PC architecture. A separate suite of code pages was implemented not only due to compatibility, but also because the fonts of VGA (and descendant) hardware suggest encoding of line drawing characters to be compatible with code page 437. Most OEM code pages share many code points, particularly for non-letter characters, with the second (non-ASCII) half of CP437.


A typical OEM code page, in its second half, does not resemble any ANSI/Windows code page even roughly. Nevertheless, two single-byte, fixed-width code pages (874 for Thai and 1258 for Vietnamese) and four multibyte CJK code pages (932, 936, 949, 950) are used as both OEM and ANSI code pages. Code page 1258 uses combining diacritics, as Vietnamese requires more than 128 letter-diacritic combinations. This is in contrast to VISCII, which replaces some of the C0 (i.e. ASCII) control codes.



History


Initially, computer systems and system programming languages did not make a distinction between characters and bytes. This led to much confusion subsequently. Microsoft software and systems previous to the Windows NT line are examples of this, using the OEM and ANSI code pages, which do not make the distinction.


Since the late 1990s, software and systems are increasingly adopting more direct encodings of Unicode, in particular UTF-8 and UTF-16; this trend has been improved by the widespread adoption of XML, which provides a more adequate mechanism for labelling the encoding used.[4] Recent Microsoft products and application program interfaces use Unicode internally, but many applications and APIs continue to use the default encoding of the computer's locale when reading and writing text data to files or standard output. Therefore, though Unicode is the accepted standard, there is still backwards compatibility with the older Windows code pages.


The euro sign was added relatively recently[when?] to ANSI and OEM code pages (1998 in the case of Code page 858) and therefore obsolete versions of Windows are unable to use it with code pages.[citation needed]


Since version 1803, Windows machines can be configured to allow UTF-8 as the "ANSI" and OEM codepage.[5]



List


This list is incomplete; you can help by expanding it.

The following Windows code pages exist:































































































































































ID Names Description Type Base Encoding Standard Support DOS- based Windows Support Windows NT family Support Windows CE family Comments

37
 CP037, IBM037 IBM EBCDIC US-Canada Other
EBCDIC derivation		 8-bit SBCS
 IBM CP037[6]
 ? Yes

437
 CP437, IBM437 IBM PC US OEM
ASCII derivation		 8-bit SBCS
 IBM CP437[7]
1.00-4.90
 Yes

1250
 CP1250, Windows-1250
Latin 2 / Central European
 ANSI ASCII derivation 8-bit SBCS Microsoft CP1250[8][9]
 ? Yes

1251
 CP1251, Windows-1251 Cyrillic ANSI ASCII derivation 8-bit SBCS Microsoft CP1251[10][11]
 ? Yes

1252
 CP1252, Windows-1252 Latin 1 / Western European
 ANSI ASCII derivation 8-bit SBCS Microsoft CP1252[12][13]
 ? Yes letter repertoire similar to CP850

1253
 CP1253, Windows-1253 Greek ANSI ASCII derivation 8-bit SBCS Microsoft CP1253[14][15]
 ? Yes

1254
 CP1254, Windows-1254 Turkish ANSI ASCII derivation 8-bit SBCS Microsoft CP1254[16][17]
 ? Yes

1255
 CP1255, Windows-1255 Hebrew ANSI ASCII derivation 8-bit SBCS Microsoft CP1255[18][19]
 ? Yes

1256
 CP1256, Windows-1256 Arabic ANSI ASCII derivation 8-bit SBCS Microsoft CP1256[20][21]
 ? Yes

1257
 CP1257, Windows-1257 Baltic ANSI ASCII derivation 8-bit SBCS Microsoft CP1257[22][23]
 ? Yes

1258
 CP1258, Windows-1258 Vietnamese
OEM+ANSI
 ? 8-bit SBCS Microsoft CP1258[24][25]
 ? Yes



  • 500 - Latin 1

  • 708

  • 720

  • 737

  • 775

  • 850

  • 852

  • 855

  • 857

  • 858

  • 860

  • 861

  • 862

  • 863

  • 864

  • 865


  • 866 - cp866 - Greek


  • 869 - IBM869


  • 870 - IBM870


  • 874 - Thai


  • 875 - cp875


  • 932 - Japanese


  • 936 - Chinese (simplified) (PRC, Singapore)


  • 949 - Korean


  • 950 - Chinese (traditional) (Taiwan, Hong Kong)


  • 1026 - EBCDIC Turkish


  • 1047 - IBM01047 - Latin 1


  • 1140 - IBM01141


  • 1141 - IBM01141


  • 1142 - IBM01142


  • 1143 - IBM01143


  • 1144 - IBM01144


  • 1145 - IBM01145


  • 1146 - IBM01146


  • 1147 - IBM01147


  • 1148 - IBM01148


  • 1149 - IBM01149


  • 1200 - Unicode (BMP of ISO 10646, UTF-16LE)


  • 1201 - Unicode (BMP of ISO 10646, UTF-16BE). Available only to managed applications [26]


  • 1361 - Korean (KS C 5601-1992)


  • 10000 - Apple Macintosh Roman


  • 10001 - Apple Macintosh Japanese


  • 10002 - Apple Macintosh Chinese (traditional) (BIG-5)


  • 10003 - Apple Macintosh Korean


  • 10004 - Apple Macintosh Arabic


  • 10005 - Apple Macintosh Hebrew


  • 10006 - Apple Macintosh Greek


  • 10007 - Apple Macintosh Cyrillic


  • 10008 - Apple Macintosh Chinese (simplified) (GB 2312)


  • 10010 - Apple Macintosh Romanian


  • 10017 - Apple Macintosh Ukrainian


  • 10021 - Apple Macintosh Thai


  • 10029 - Apple Macintosh Roman II / Central Europe


  • 10079 - Apple Macintosh Icelandic


  • 10081 - Apple Macintosh Turkish


  • 10082 - Apple Macintosh Croatian


  • 12000 - utf-32


  • 12001 - utf-32 Big endian


  • 20000 - x-Chinese-CNS


  • 20001 - x-cp20001


  • 20002 - x-x-Chinese-Eten


  • 20003 - x-cp20003


  • 20004 - x-cp20004


  • 20005 - x-cp20005


  • 20105 - 7-bit IA5 IRV (Western European)[27][28][29]


  • 20106 - 7-bit IA5 German (DIN 66003)[27][28][30]


  • 20107 - 7-bit IA5 Swedish (SEN 850200 C)[27][28][31]


  • 20108 - 7-bit IA5 Norwegian (NS 4551-2)[27][28][32]


  • 20127 - 7-bit US-ASCII[27][28][33]


  • 20261 - T.61 (T.61-8bit)


  • 20269 - ISO-6937


  • 20273 - EBCDIC Germany


  • 20277 - EBCDIC Denmark/Norway


  • 20278 - EBCDIC Finland/Sweden


  • 20280 - EBCDIC Italy


  • 20284 - EBCDIC Latin America/Spain


  • 20285 - EBCDIC United Kingdom


  • 20290 - EBCDIC Japanese


  • 20297 - EBCDIC France


  • 20420 - EBCDIC Arabic


  • 20423 - EBCDIC Greek


  • 20424 - x-EBCDIC-KoreanExtended


  • 20833 - Korean


  • 20838 - EBCDIC Thai


  • 20866 - Russian - KOI8-R


  • 20871 - EBCDIC Icelandic


  • 20880 - EBCDIC Cyrillic


  • 20905 - EBCDIC Turkish


  • 20924 - IBM00924


  • 20932 - EUC-JP


  • 20936 - x-cp20936


  • 20949 - x-cp20949


  • 21025 - EBCDIC Cyrillic


  • 21027 - Japanese


  • 21866 - Ukrainian - KOI8-RU


  • 28591 - ISO-8859-1 - latin1 or IBM819


  • 28592 - ISO-8859-2 - Latin-2


  • 28593 - ISO-8859-3 - Latin-3 or South European


  • 28594 - ISO-8859-4 - Latin-4 or North European


  • 28595 - ISO-8859-5 - Latin/Cyrillic


  • 28596 - ISO-8859-6 - Latin/Arabic


  • 28597 - ISO-8859-7 - Latin/Greek


  • 28598 - ISO-8859-8 - Latin/Hebrew


  • 28599 - ISO-8859-9 - Latin-5 or Turkish


  • 28600 - ISO-8859-10 - Latin-6


  • 28601 - ISO-8859-11 - Latin/Thai


  • 28602 - ISO-8859-12 - Latin/Devanagari (not support by Windows)


  • 28603 - ISO-8859-13 - Latin-7 or Baltic Rim


  • 28604 - ISO-8859-14 - Latin-8 or Celtic


  • 28605 - ISO-8859-15 - Latin-9


  • 28606 - ISO-8859-16 - Latin-10 or South-Eastern European


  • 38596 - ISO-8859-6


  • 38598 - ISO-8859-8


  • 65000 - Unicode (BMP of ISO 10646, UTF-7)


  • 65001 - Unicode (BMP of ISO 10646, UTF-8)



Problems arising from the use of code pages


Microsoft strongly recommends using Unicode in modern applications, but many applications or data files still depend on the legacy code pages.



  • Programs need to know what code page to use in order to display the contents of files correctly. If a program uses the wrong code page it may show text as mojibake.

  • The code page in use may differ between machines, so files created on one machine may be unreadable on another.

  • Data is often improperly tagged with the code page, or not tagged at all, making determination of the correct code page to read the data difficult.

  • These Microsoft code pages differ to various degrees from some of the standards and other vendors' implementations. This isn't a Microsoft issue per se, as it happens to all vendors, but the lack of consistency makes interoperability with other systems unreliable in some cases.

  • The use of code pages limits the set of characters that may be used.

  • Characters expressed in an unsupported code page may be converted to question marks (?) or other replacement characters, or to a simpler version (such as removing accents from a letter). In either case, the original character may be lost.



See also



  • AppLocale — a utility to run non-Unicode (code page-based) applications in a locale of the user's choice.


References




  1. ^ Code Pages, MSDN


  2. ^ ab MSDN: Glossary of Terms


  3. ^ IANA list of Character Sets


  4. ^ http://www.w3.org/TR/xml11/#charencoding


  5. ^ hylom (2017-11-14). "Windows 10のInsider PreviewでシステムロケールをUTF-8にするオプションが追加される" [The option to make UTF-8 the system locale added in Windows 10 Insider Preview]. スラド (in Japanese). Retrieved 2018-05-10..mw-parser-output cite.citation{font-style:inherit}.mw-parser-output q{quotes:"""""""'""'"}.mw-parser-output code.cs1-code{color:inherit;background:inherit;border:inherit;padding:inherit}.mw-parser-output .cs1-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/6/65/Lock-green.svg/9px-Lock-green.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-lock-limited a,.mw-parser-output .cs1-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/d/d6/Lock-gray-alt-2.svg/9px-Lock-gray-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/a/aa/Lock-red-alt-2.svg/9px-Lock-red-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration{color:#555}.mw-parser-output .cs1-subscription span,.mw-parser-output .cs1-registration span{border-bottom:1px dotted;cursor:help}.mw-parser-output .cs1-hidden-error{display:none;font-size:100%}.mw-parser-output .cs1-visible-error{font-size:100%}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration,.mw-parser-output .cs1-format{font-size:95%}.mw-parser-output .cs1-kern-left,.mw-parser-output .cs1-kern-wl-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right,.mw-parser-output .cs1-kern-wl-right{padding-right:0.2em}


  6. ^ IBM. "SBCS code page information document - CPGID 00037". Retrieved 2014-07-04.


  7. ^ IBM. "SBCS code page information document - CPGID 00437". Retrieved 2014-07-04.


  8. ^ Microsoft. "Windows 1250". Retrieved 2014-07-06.


  9. ^ IBM. "SBCS code page information document CPGID 01250". Retrieved 2014-07-06.


  10. ^ Microsoft. "Windows 1251". Retrieved 2014-07-06.


  11. ^ IBM. "SBCS code page information document CPGID 01251". Retrieved 2014-07-06.


  12. ^ Microsoft. "Windows 1252". Retrieved 2014-07-06.


  13. ^ IBM. "SBCS code page information document CPGID 01252". Retrieved 2014-07-06.


  14. ^ Microsoft. "Windows 1253". Retrieved 2014-07-06.


  15. ^ IBM. "SBCS code page information document CPGID 01253". Retrieved 2014-07-06.


  16. ^ Microsoft. "Windows 1254". Retrieved 2014-07-06.


  17. ^ IBM. "SBCS code page information document CPGID 01254". Retrieved 2014-07-06.


  18. ^ Microsoft. "Windows 1255". Retrieved 2014-07-06.


  19. ^ IBM. "SBCS code page information document CPGID 01255". Retrieved 2014-07-06.


  20. ^ Microsoft. "Windows 1256". Retrieved 2014-07-06.


  21. ^ IBM. "SBCS code page information document CPGID 01256". Retrieved 2014-07-06.


  22. ^ Microsoft. "Windows 1257". Retrieved 2014-07-06.


  23. ^ IBM. "SBCS code page information document CPGID 01257". Retrieved 2014-07-06.


  24. ^ Microsoft. "Windows 1258". Retrieved 2014-07-06.


  25. ^ IBM. "SBCS code page information document CPGID 01258". Retrieved 2014-07-06.


  26. ^ Code page identifier list [1]


  27. ^ abcde "Code Page Identifiers". Microsoft Developer Network. Microsoft. 2014. Archived from the original on 2016-06-19. Retrieved 2016-06-19.


  28. ^ abcde "Web Encodings - Internet Explorer - Encodings". WHATWG Wiki. 2012-10-23. Archived from the original on 2016-06-20. Retrieved 2016-06-20.


  29. ^ Foller, Antonin (2014) [2011]. "Western European (IA5) encoding - Windows charsets". WUtils.com - Online web utility and help. Motobit Software. Archived from the original on 2016-06-20. Retrieved 2016-06-20.


  30. ^ Foller, Antonin (2014) [2011]. "German (IA5) encoding - Windows charsets". WUtils.com - Online web utility and help. Motobit Software. Archived from the original on 2016-06-20. Retrieved 2016-06-20.


  31. ^ Foller, Antonin (2014) [2011]. "Swedish (IA5) encoding - Windows charsets". WUtils.com - Online web utility and help. Motobit Software. Archived from the original on 2016-06-20. Retrieved 2016-06-20.


  32. ^ Foller, Antonin (2014) [2011]. "Norwegian (IA5) encoding - Windows charsets". WUtils.com - Online web utility and help. Motobit Software. Archived from the original on 2016-06-20. Retrieved 2016-06-20.


  33. ^ Foller, Antonin (2014) [2011]. "US-ASCII encoding - Windows charsets". WUtils.com - Online web utility and help. Motobit Software. Archived from the original on 2016-06-20. Retrieved 2016-06-20.



External links




  • National Language Support (NLS) API Reference. Table showing ANSI and OEM codepages per language (from web-archive since Microsoft removed the original page)


  • Blog about Microsoft code pages.

  • IANA Charset Name Registrations

  • Unicode mapping table for Windows code pages

  • Unicode mappings of windows code pages with "best fit"









-

Popular posts from this blog

Lambaréné

Image
Place in Moyen-Ogooué, Gabon Lambaréné Street in Lambaréné Lambaréné Location in Gabon Coordinates: 0°41′18″S 10°13′55″E  /  0.68833°S 10.23194°E  / -0.68833; 10.23194 Coordinates: 0°41′18″S 10°13′55″E  /  0.68833°S 10.23194°E  / -0.68833; 10.23194 Country   Gabon Province Moyen-Ogooué Population (2013 census)  • Total 38,775 Lambaréné is a town and the capital of Moyen-Ogooué in Gabon. With a population of 38,775 as of 2013, it is located 75 kilometres south of the equator. Lambaréné is based in the Central African Rainforest at the river Ogooué. This river divides the city into 3 districts: Rive Gauche, Ile Lambaréné and Rive Droite. The Albert Schweitzer Hospital and the districts Adouma and Abongo are located on Rive Droite. The districts Atongowanga, Sahoty, Dakar, Grand Village, Château, Lalala and Bordamur build the Ile Lambaréné. The majority of the people in Lambaréné live in the district Isaac located on Rive Gauche. This distr
Read more

維納斯堡 (華盛頓州)

Image
body.skin-minerva .mw-parser-output table.infobox caption{text-align:center} 維納斯堡 Venersborg （英文） CDP Venersborg, Washington 維納斯堡位置圖 坐标： 45°46′58″N 122°27′43″W  /  45.7828°N 122.462°W  / 45.7828; -122.462 國家   美國 州 華盛頓州 郡 克拉克县 面积  •  总计 27.8 平方公里（10.7 平方英里）  • 陸地 27.8 平方公里（10.7 平方英里）  • 水域 0.0 平方公里（0.0 平方英里） 海拔 155 米（509 英尺） 人口 （2000年）  • 總計 3,274  • 密度 118.0/平方公里（305.6/平方英里） 时区 PST （UTC-8）  • 夏时制 PDT（UTC-7） FIPS碼 53-74585 [1] GNIS編號 1527695 [2] 維納斯堡 （ 英语： Venersborg ）是美国华盛顿州克拉克县的一個普查规定居民点（CDP），2000年美國人口普查時人口為2,085人。 最初為瑞典人聚居地。 參見 維納什堡 参考資料 ^ American FactFinder. United States Census Bureau. [ 2008-01-31 ] .   ^ US Board on Geographic Names. United States Geological Survey. 2007-10-25 [ 2008-01-31 ] .   查 论 编 克拉克县 行政區劃 郡治 ： 溫哥華 市 巴特爾格朗德 | 卡默斯 | 拉申特 | 里奇菲尔德 | 溫哥華 | 瓦休戈 | 林地市‡ 鎮 亞科爾特 CDP 安波伊 | 巴伯頓 | 布拉什普雷里 | 櫻桃樹叢區 |
Read more

Mononymous person

Image
Plato, the Greek philosopher, is universally known by a single name. A mononymous person is an individual who is known and addressed by a single name, or mononym. [a] [b] In some cases, that name has been selected by the individual, who may have originally been given a polynym ("multiple name"). In other cases, it has been determined by the custom of the country [c] or by some interested segment. In the case of historical figures, it may be the only one of the individual's names that has survived and is still known today. Contents 1 Antiquity 2 Medieval uses 2.1 Europe 2.2 The Americas 3 Post-medieval uses 3.1 France 3.2 Other Europe 3.3 North America 4 Royalty 5 Modern times 5.1 Mononym-normal 5.2 Asia 5.3 The West 6 Gallery 7 See also 8 Notes 9 References 10 Bibliography 11 External links Antiquity Narmer The structure of persons' names has varied across ti
Read more