Content deleted Content added
m Typography |
m Typography |
||
Line 2:
'''Windows code pages''' are sets of characters or [[code pages]] (known as [[character encoding]]s in other operating systems) used in [[Microsoft Windows]] from the 1980s and 1990s. Windows code pages were gradually superseded when [[Unicode in Microsoft Windows|Unicode was implemented in Windows]],{{cn|date=October 2020}} although they are still supported both within Windows and other platforms, and still apply when [[Alt code]] shortcuts are used.
There are two groups of system code pages in Windows systems: OEM and Windows-native ("ANSI") code pages.
(ANSI is the [[American National Standards Institute]].) Code pages in both of these groups are [[extended ASCII]] code pages. Additional code pages are supported by standard Windows conversion routines, but not used as either type of system code page.
==ANSI code page<span class="anchor" id="ANSI"></span>==
{{Infobox character encoding
|name
|alias
|mime
|image
|caption
|standard
|extends
|prev
|next
|otherrelated
}}
'''ANSI code pages''' (officially called "Windows code pages"<ref>{{Cite web
|date=2016-03-07 |title=Code Pages |url=https://msdn.microsoft.com/en-us/goglobal/bb964653.aspx |access-date=2021-05-26 |archive-url=https://web.archive.org/web/20160307222735/https://msdn.microsoft.com/en-us/goglobal/bb964653.aspx |archive-date=2016-03-07}}</ref> |url=https://msdn.microsoft.com/en-us/goglobal/bb964658.aspx#a |title=Glossary of Terms Used on this Site |date=December 8, 2018 |archive-url=https://web.archive.org/web/20181208141313/https://msdn.microsoft.com/en-us/goglobal/bb964658.aspx#a
|quote=The term "ANSI" as used to signify Windows code pages is a historical reference, but is nowadays a misnomer that continues to persist in the Windows community. The source of this comes from the fact that the Windows code page 1252 was originally based on an ANSI draft—which became International Organization for Standardization (ISO) Standard 8859-1. “ANSI applications” are usually a reference to non-Unicode or code page–based applications.}}</ref>) are used for native non-Unicode (say, [[byte oriented]]) applications using a [[graphical user interface]] on Windows systems. The term "ANSI" is a misnomer because these Windows code pages do not comply with any [[American National Standards Institute|ANSI (American National Standards Institute)]] standard; [[Code Page 1252|code page 1252]] was based on an early ANSI draft that became the international standard [[ISO 8859-1]], <ref name="ms glossary" /><!-- --> which adds a further 32 control codes and space for 96 printable characters. Among other differences, Windows code-pages allocate printable characters to the supplementary control code space, making them at best illegible to standards-compliant operating systems.)▼
|archive-date=2018-12-08
▲|quote=The term "ANSI" as used to signify Windows code pages is a historical reference, but is nowadays a misnomer that continues to persist in the Windows community. The source of this comes from the fact that the Windows code page 1252 was originally based on an ANSI draft—which became International Organization for Standardization (ISO) Standard 8859-1. “ANSI applications” are usually a reference to non-Unicode or code page–based applications.}}</ref>) are used for native non-Unicode (say, [[byte oriented]]) applications using a [[graphical user interface]] on Windows systems. The term "ANSI" is a misnomer because these Windows code pages do not comply with any [[American National Standards Institute|ANSI (American National Standards Institute)]] standard; [[Code Page 1252|code page 1252]] was based on an early ANSI draft that became the international standard [[ISO 8859-1]],
Most legacy "ANSI" code pages have code page numbers in the pattern 125x. However, [[windows-874|874]] (Thai) and the East Asian multi-byte "ANSI" code pages ([[Windows-31J|932]], [[windows-936|936]], [[Unified Hangul Code|949]], [[Code page 950|950]]), all of which are also used as OEM code pages, are numbered to match IBM encodings, none of which are identical to the Windows encodings (although most are similar). While [[windows-1258|code page 1258]] is also used as an OEM code page, it is original to Microsoft rather than an extension to an existing encoding. IBM have assigned their own, different numbers for Microsoft's variants, these are given for reference in the lists below where applicable.
All of the 125x Windows code pages, as well as 874 and 936, are labelled by [[Internet Assigned Numbers Authority]] (IANA) as "Windows-''number''", although "Windows-936" is treated as a synonym for "[[GBK (character encoding)|GBK]]". Windows code page 932 is instead labelled as "Windows-31J".<ref>{{Cite web
|title=Character Sets |url=http://www.iana.org/assignments/character-sets/character-sets.xhtml |access-date=2021-05-26 |website=www.iana.org |archive-date=2021-05-25 |archive-url=https://web.archive.org/web/20210525003138/https://www.iana.org/assignments/character-sets/character-sets.xhtml |url-status=live}}</ref> ANSI Windows code pages, and especially the code page [[Windows-1252|1252]], were so called since they were purportedly based on drafts submitted or intended for ANSI. However, ANSI and [[International Organization for Standardization|ISO]] have not standardized any of these code pages. Instead they are either:<ref name="ms glossary"/>
Line 41 ⟶ 59:
Initially, computer systems and system programming languages did not make a distinction between [[character (computing)|character]]s and [[byte]]s: for the [[List of writing systems#Segmental script|segmental scripts]] used in most of Africa, the Americas, southern and south-east Asia, the Middle East and Europe, a character needs just one byte, but two or more bytes are needed for the [[ideographic]] sets used in the rest of the world. This subsequently led to much confusion. Microsoft software and systems prior to the [[Windows NT]] line are examples of this, because they use the OEM and ANSI code pages that do not make the distinction.
Since the late 1990s, software and systems have adopted [[Unicode]] as their preferred storage format; this trend has been improved by the widespread adoption of [[XML]] which default to [[UTF-8]] but also provides a mechanism for labelling the encoding used.<ref>{{cite web
| | | | | | | | === UTF-8, UTF-16 ===
Microsoft adopted a Unicode encoding (first the now-obsolete [[UCS-2]], which was then Unicode's only encoding), i.e. [[UTF-16]] for all its [[operating system]]s from Windows NT onwards, but additionally supports [[UTF-8]] (aka <code>CP_UTF8</code>) since [[Windows 10 version history#Version 1803 (April 2018 Update)|Windows 10 version 1803]].<ref>{{cite web
|url=https://srad.jp/story/17/11/14/0640253/ |title=Windows 10のInsider PreviewでシステムロケールをUTF-8にするオプションが追加される |trans-title=The option to make UTF-8 the system locale added in Windows 10 Insider Preview |author=hylom |website=スラド |language=ja |date=2017-11-14 |access-date=2018-05-10 |archive-date=2018-05-11 |archive-url=https://web.archive.org/web/20180511012606/https://srad.jp/story/17/11/14/0640253/
|url-status=live}}</ref>
UTF-16 uniquely encodes all Unicode characters in the [[Basic Multilingual Plane]] (BMP) using 16 bits but the remaining Unicode (e.g. [[emoji]]s) is encoded with a 32-bit (four byte) code{{snd}} while the rest of the industry ([[Unix-like]] systems and the web), and now Microsoft chose [[UTF-8]] (which uses one byte for the 7-bit [[ASCII]] character set, two or three bytes for other characters in the BMP, and four bytes for the remainder).
Line 53 ⟶ 90:
=== Windows-125x series ===
These nine code pages are all [[extended ASCII]] 8-bit [[SBCS]] encodings, and were designed by [[Microsoft]] for use as ANSI codepages on Windows. They are commonly known by their IANA-registered<ref name="iana31j">{{cite web
| | | | | | | The Windows-125x series includes nine of the ANSI code pages, and mostly covers scripts from [[Europe]] and [[West Asia]] with the addition of [[Vietnam]]. System encodings for [[Thai script|Thai]] and for [[East Asia]]n languages were numbered to match similar IBM code pages and are used as both ANSI and OEM code pages; these are covered in following sections.
Line 113 ⟶ 157:
!ID!!Language!!Encoding!! data-sort-type="number" |IBM Equivalent!!Difference from IBM CCSID of same number!!Use
|-
|[[Code page 932 (Microsoft Windows)|932]]||[[Japanese writing system|Japanese]]||[[Shift JIS]] (Microsoft variant)||943<ref name="ibm932v943">{{cite web
|-
|[[Code page 936 (Microsoft Windows)|936]]||[[Simplified Chinese characters|Chinese (simplified)]]||[[GBK (character encoding)|GBK]]||1386||[[Code page 936 (IBM)|IBM-936]] is a different Simplified Chinese encoding with a different encoding method, which has been deprecated since 1993.||ANSI/OEM (PRC, Singapore)<!-- Windows 7 Ultimate -->
Line 146 ⟶ 190:
|[[Code page 20936|20936]]||5479||Chinese (simplified)||[[GB 2312]]||Conversion
|-
|[[Code page 20949|20949]], 51949||970||Korean||Wansung (8-bit with ASCII, i.e. [[EUC-KR]])<ref>{{cite web
|url=https://source.winehq.org/git/wine.git/blob/6f68543692a7588daa581d00c475715395036b15:/tools/make_unicode#l946 |title=dump_krwansung_codepage: build Korean Wansung table from the KSX1001 file |work=make_unicode: Generate code page .c files from ftp.unicode.org descriptions |first=Alexandre |last=Julliard |publisher=[[Wine (software)|Wine Project]] |access-date=2021-03-14 |archive-date=2021-05-26 |archive-url=https://web.archive.org/web/20210526173718/https://source.winehq.org/git/wine.git/blob/6f68543692a7588daa581d00c475715395036b15:/tools/make_unicode#l946 |url-status=live}}</ref>||Conversion
|}
| |||