Editing Character encoding

{{Short description|Using numbers to represent text characters}}
{{Use dmy dates|date=January 2018}}
[[File:Papertape-Wikipedia-example-dark1-2000px.png|thumb|[[Punched tape]] with the word "Wikipedia" encoded in [[ASCII]]. Presence and absence of a hole represents 1 and 0, respectively; for example, W is encoded as {{code|1010111}}.]]

'''Character encoding''' is the process of assigning numbers to graphical [[character (computing)|characters]], especially the written characters of human language, allowing them to be stored, transmitted, and transformed using computers.<ref>{{cite web|title = Character Encoding Definition|date = September 24, 2010 |url= http://techterms.com/definition/characterencoding |website=The Tech Terms Dictionary}}</ref> The numerical values that make up a character encoding are known as [[code point]]s and collectively comprise a code space or a [[code page]].

Early character encodings that originated with optical or electrical [[telegraphy]] and in early computers could only represent a subset of the characters used in [[written language]]s, sometimes restricted to [[Letter case|upper case letter]]s, [[Numeral system|numeral]]s and some [[punctuation]] only.  Over time, character encodings capable of representing more characters were created, such as [[ASCII]], the [[ISO/IEC 8859]] encodings, various computer vendor encodings, and [[Unicode]] encodings such as [[UTF-8]] and [[UTF-16]].

The [[Popularity of text encodings|most popular character encoding]] on the [[World Wide Web]] is UTF-8, which is used in 98.2% of surveyed web sites, as of May 2024.<ref name="W3TechsWebEncoding">{{Cite web |title=Usage Survey of Character Encodings broken down by Ranking |url=https://w3techs.com/technologies/cross/character_encoding/ranking |access-date=2024-04-29 |website=W3Techs}}</ref> In [[Application software|application programs]] and [[operating system]] tasks, both UTF-8 and UTF-16 are popular options.<ref name=":0">{{Cite web |title=Charset |url=https://developer.android.com/reference/java/nio/charset/Charset |access-date=2021-01-02 |website=Android Developers |quote=Android note: The Android platform default is always UTF-8.}}</ref>

== History ==
The history of character codes illustrates the evolving need for machine-mediated character-based symbolic information over a distance, using once-novel electrical means. The earliest codes were based upon manual and hand-written encoding and cyphering systems, such as [[Bacon's cipher]], [[Braille]], [[international maritime signal flags]], and the 4-digit encoding of Chinese characters for a [[Chinese telegraph code]] ([[Hans Schjellerup]], 1869). With the adoption of electrical and electro-mechanical techniques these earliest codes were adapted to the new capabilities and limitations of the early machines. The earliest well-known electrically transmitted character code, [[Morse code]], introduced in the 1840s, used a system of four "symbols" (short signal, long signal, short space, long space) to generate codes of variable length. Though some commercial use of Morse code was via machinery, it was often used as a manual code, generated by hand on a [[telegraph key]] and decipherable by ear, and persists in [[amateur radio]] and [[Non-directional beacon|aeronautical]] use.  Most codes are of fixed per-character length or variable-length sequences of fixed-length codes (e.g. [[Unicode]]).<ref>{{cite web | url=http://blog.smartbear.com/development/ancient-computer-character-code-tables-and-why-theyre-still-relevant/ | title=Ancient Computer Character Code Tables – and Why They're Still Relevant | publisher=Smartbear | date=17 April 2014 | access-date=29 April 2014 | author=Tom Henderson |url-status=dead |archive-url=https://web.archive.org/web/20140430000312/http://blog.smartbear.com/development/ancient-computer-character-code-tables-and-why-theyre-still-relevant/ |archive-date= Apr 30, 2014 }}</ref>

Common examples of character encoding systems include Morse code, the [[Baudot code]], the [[American Standard Code for Information Interchange]] (ASCII) and Unicode. Unicode, a well-defined and extensible encoding system, has replaced most earlier character encodings, but the path of code development to the present is fairly well known.

The Baudot code, a five-[[bit]] encoding, was created by [[Émile Baudot]] in 1870, patented in 1874, modified by Donald Murray in 1901, and standardized by CCITT as International Telegraph Alphabet No.&nbsp;2 (ITA2) in 1930. The name ''baudot'' has been erroneously applied to ITA2 and its many variants. ITA2 suffered from many shortcomings and was often improved by many equipment manufacturers, sometimes creating compatibility issues.

[[File:Blue-punch-card-front-horiz.png|thumb|Hollerith 80-column punch card with EBCDIC character set]]
[[Herman Hollerith]] invented punch card data encoding in the late 19th century to analyze census data. Initially, each hole position represented a different data element, but later, numeric information was encoded by numbering the lower rows 0 to 9, with a punch in a column representing its row number. Later alphabetic data was encoded by allowing more than one punch per column. Electromechanical [[tabulating machine]]s represented date internally by the timing of pulses relative to the motion of the cards through the machine.

When [[IBM]] went to electronic processing, starting with the [[IBM 603]] Electronic Multiplier, it used a variety of binary encoding schemes that were tied to the punch card code. IBM used several [[BCD (character encoding)|binary-coded decimal]] (BCD) six-bit character encoding schemes, starting as early as 1953 in its [[IBM 702|702]]<ref>{{cite web|url=http://www.bitsavers.org/pdf/ibm/702/22-6173-1_702prelim_Feb56.pdf |via=bitsavers.org  |archive-url=https://ghostarchive.org/archive/20221009/http://www.bitsavers.org/pdf/ibm/702/22-6173-1_702prelim_Feb56.pdf |archive-date=2022-10-09 |url-status=live|title=IBM Electronic Data-Processing Machines Type 702 Preliminary Manual of Information|date=1954|id=22-6173-1|page=80}}</ref> and [[IBM 704|704]] computers, and in its later [[IBM 700/7000 series|7000 Series]] and [[IBM 1400 series|1400 series]], as well as in associated peripherals. Since the punched card code then in use was limited to digits, upper-case English letters and a few special characters, six bits were sufficient. These BCD encodings extended existing simple four-bit numeric encoding to include alphabetic and special characters, mapping them easily to punch-card encoding which was already in widespread use. IBM's codes were used primarily with IBM equipment. Other computer vendors of the era had their own character codes, often six-bit, such as the encoding used by the {{nobreak|[[UNIVAC I]]}}.<ref>{{cite web|url=http://www.bitsavers.org/pdf/univac/univac1/UnivacI_RefCard.pdf|title=UNIVAC System|type=reference card}}</ref> They usually had the ability to read tapes produced on IBM equipment. IBM's BCD encodings were the precursors of their [[Extended Binary-Coded Decimal Interchange Code]] (usually abbreviated as EBCDIC), an eight-bit encoding scheme developed in 1963 for the [[IBM System/360]] that featured a larger character set, including lower case letters.

In 1959 the U.S. military defined its [[Fieldata]] code, a six-or seven-bit code, introduced by the U.S. Army Signal Corps. While Fieldata addressed many of the then-modern issues (e.g. letter and digit codes arranged for machine collation), it fell short of its goals and was short-lived. In 1963 the first ASCII code was released (X3.4-1963) by the ASCII committee (which contained at least one member of the Fieldata committee, W. F. Leubbert), which addressed most of the shortcomings of Fieldata, using a simpler seven-bit code. Many of the changes were subtle, such as collatable character sets within certain numeric ranges. ASCII63 was a success, widely adopted by industry, and with the follow-up issue of the 1967 ASCII code (which added lower-case letters and fixed some "control code" issues) ASCII67 was adopted fairly widely. ASCII67's American-centric nature was somewhat addressed in the European [[ECMA-6]] standard.<ref>{{cite web | url=https://www.sr-ix.com/Archive/CharCodeHist/index.html | title=An annotated history of some character codes | date= 20 April 2016 |website=Sensitive Research | access-date=1 November 2018 | author=Tom Jennings}}</ref> Eight-bit [[extended ASCII]] encodings, such as various vendor extensions and the [[ISO/IEC 8859]] series, supported all ASCII characters as well as additional non-ASCII characters.

While trying to develop universally interchangeable character encodings, researchers in the 1980s faced the dilemma that, on the one hand, it seemed necessary to add more bits to accommodate additional characters, but on the other hand, for the users of the relatively small character set of the Latin alphabet (who still constituted the majority of computer users), those additional bits were a colossal waste of then-scarce and expensive computing resources (as they would always be zeroed out for such users).  In 1985, the average personal computer user's [[hard disk drive]] could store only about 10 megabytes, and it cost approximately US$250 on the wholesale market (and much higher if purchased separately at retail),<ref name="Strelho">{{cite news |last1=Strelho |first1=Kevin |title=IBM Drives Hard Disks to New Standards |url=https://books.google.com/books?id=zC4EAAAAMBAJ&pg=PA29 |access-date=November 10, 2020 |work=InfoWorld |publisher=Popular Computing Inc. |date=April 15, 1985 |pages=29–33}}</ref> so it was very important at the time to make every bit count.

The compromise solution that was eventually found and {{vague|text=developed into Unicode|reason=Became Unicode or was added to Unicode?  See talk page.|date=April 2023}} was to break the assumption (dating back to telegraph codes) that each character should always directly correspond to a particular sequence of bits. Instead, characters would first be mapped to a universal intermediate representation in the form of abstract numbers called [[code point]]s. Code points would then be represented in a variety of ways and with various default numbers of bits per character (code units) depending on context. To encode code points higher than the length of the code unit, such as above 256 for eight-bit units, the solution was to implement [[variable-width encoding|variable-length encodings]] where an escape sequence would signal that subsequent bits should be parsed as a higher code point.

== Terminology ==
Informally, the terms "character encoding", "character map", "character set" and "code page" are often used interchangeably.<ref name="SteeleMSDN">{{cite web|url=https://docs.microsoft.com/en-us/archive/blogs/shawnste/whats-the-difference-between-an-encoding-code-page-character-set-and-unicode|author=Shawn Steele|title=What's the difference between an Encoding, Code Page, Character Set and Unicode?|date=15 March 2005|website=Microsoft Docs}}</ref> Historically, the same standard would specify a repertoire of characters and how they were to be encoded into a stream of code units — usually with a single character per code unit. However, due to the emergence of more sophisticated character encodings, the distinction between these terms has become important.

* A ''[[Character (computing)|character]]'' is a minimal unit of text that has semantic value.<ref name="SteeleMSDN"/><ref name="Unicode glossary">{{cite web |title=Glossary of Unicode Terms |url=https://unicode.org/glossary/ |publisher=Unicode Consortium}}</ref>
* A ''character set'' is a collection of elements used to represent text.<ref name="SteeleMSDN"/><ref name="Unicode glossary"/> For example, the [[Latin alphabet]] and [[Greek alphabet]] are both character sets.
* {{anchor|CCS}}A ''coded character set'' is a character set mapped to a set of unique numbers.<ref name="Unicode glossary"/> For historical reasons, this is also often referred to as a [[code page]].<ref name="SteeleMSDN"/>
* {{anchor|repertoire}}A ''character repertoire'' is the set of characters that can be represented by a particular coded character set.<ref name="Unicode glossary"/><ref name="unicode15">{{cite book |title=The Unicode Standard Version 15.0 – Core Specification |date=September 2022 |publisher=Unicode Consortium |isbn=978-1-936213-32-0 |chapter=Chapter 3: Conformance |url=https://www.unicode.org/versions/Unicode15.0.0/ch03.pdf}}</ref> The repertoire may be closed, meaning that no additions are allowed without creating a new standard (as is the case with ASCII and most of the ISO-8859 series); or it may be open, allowing additions (as is the case with Unicode and to a limited extent [[Windows code page]]s).<ref name="unicode15"/>
* A ''code point'' is a value or position of a character in a coded character set.<ref name="Unicode glossary"/>
* A ''code space'' is the range of numerical values spanned by a coded character set.<ref name="Unicode glossary"/><ref name="utr17"/>
* A ''code unit'' is the minimum bit combination that can represent a character in a character encoding (in [[computer science]] terms, it is the [[Word (computer architecture)|word]] size of the character encoding).<ref name="Unicode glossary"/><ref name="utr17"/> For example, common code units include 7-bit, 8-bit, 16-bit, and 32-bit. In some encodings, some characters are encoded using multiple code units; such an encoding is referred to as a [[variable-width encoding]].

===Code pages===
{{main|Code page}}
"Code page" is a historical name for a coded character set.

Originally, a code page referred to a specific [[page number]] in the IBM standard character set manual, which would define a particular character encoding.<ref name="DEC_VT510">{{cite web |title=VT510 Video Terminal Programmer Information |at=7.1. Character Sets - Overview |publisher=[[Digital Equipment Corporation]] (DEC) |url=http://www.vt100.net/docs/vt510-rm/chapter7.html#S7.1 |access-date=2017-02-15 |quote=In addition to traditional [[Digital Equipment Corporation|DEC]] and [[ISO]] character sets, which conform to the structure and rules of [[ISO 2022]], the [[VT510]] supports a number of IBM PC code pages ([[page number]]s in IBM's standard character set manual) in [[PCTerm]] mode to emulate the [[console terminal]] of industry-standard PCs. |archive-date=2016-01-26  |archive-url=https://web.archive.org/web/20160126192029/http://www.vt100.net/docs/vt510-rm/chapter7.html#S7.1 |url-status=live }}</ref> Other vendors, including [[Microsoft]], [[SAP AG|SAP]], and [[Oracle Corporation]], also published their own sets of code pages; the most well-known code page suites are "[[Windows code page|Windows]]" (based on Windows-1252) and "IBM"/"DOS" (based on [[code page 437]]).

Despite no longer referring to specific page numbers in a standard, many character encodings are still referred to by their code page number; likewise, the term "code page" is often still used to refer to character encodings in general.

The term "code page" is not used in Unix or Linux, where "charmap" is preferred, usually in the larger context of locales. IBM's Character Data Representation Architecture (CDRA) designates entities with coded character set identifiers ([[CCSID]]s), each of which is variously called a "charset", "character set", "code page", or "CHARMAP".<ref name=utr17/>

===Code units===
The code unit size is equivalent to the bit measurement for the particular encoding:
* A code unit in [[ASCII]] consists of 7 bits;
* A code unit in [[UTF-8]], [[EBCDIC]] and [[GB 18030]] consists of 8 bits;
* A code unit in [[UTF-16]] consists of 16 bits;
* A code unit in [[UTF-32]] consists of 32 bits.

===Code points===
A code point is represented by a sequence of code units. The mapping is defined by the encoding. Thus, the number of code units required to represent a code point depends on the encoding:
* UTF-8: code points map to a sequence of one, two, three or four code units.
* UTF-16: code units are twice as long as 8-bit code units. Therefore, any code point with a scalar value less than U+10000 is encoded with a single code unit. Code points with a value U+10000 or higher require two code units each. These pairs of code units have a unique term in UTF-16: [[UTF-16#Code points from U+010000 to U+10FFFF|"Unicode surrogate pairs".]]
* UTF-32: the 32-bit code unit is large enough that every code point is represented as a single code unit.
* GB 18030: multiple code units per code point are common, because of the small code units. Code points are mapped to one, two, or four code units.<ref>{{cite web | url=https://docs.oracle.com/javase/tutorial/i18n/text/terminology.html | title=Terminology (The Java Tutorials) | publisher=Oracle | access-date=25 March 2018 }}</ref>

===Characters===
{{main|Character (computing)}}
Exactly what constitutes a character varies between character encodings.

For example, for letters with [[diacritic]]s, there are two distinct approaches that can be taken to encode them: they can be encoded either as a single unified character (known as a precomposed character), or as separate characters that combine into a single [[glyph]]. The former simplifies the text handling system, but the latter allows any letter/diacritic combination to be used in text. [[Typographic ligature|Ligatures]] pose similar problems.

Exactly how to handle [[glyph]] variants is a choice that must be made when constructing a particular character encoding. Some writing systems, such as Arabic and Hebrew, need to accommodate things like [[grapheme]]s that are joined in different ways in different contexts, but represent the same semantic character.

==Unicode encoding model==
[[Unicode]] and its parallel standard, the ISO/IEC 10646 [[Universal Character Set]], together constitute a unified standard for character encoding. Rather than mapping characters directly to [[byte]]s, Unicode separately defines a coded character set that maps characters to unique natural numbers ([[code point]]s), how those code points are mapped to a series of fixed-size natural numbers (code units), and finally how those units are encoded as a stream of octets (bytes). The purpose of this decomposition is to establish a universal set of characters that can be encoded in a variety of ways. To describe this model precisely, Unicode uses its own set of terminology to describe its process:<ref name="utr17">{{cite web |last1=Whistler |first1=Ken |last2=Freytag |first2=Asmus |title=UTR#17: Unicode Character Encoding Model |url=https://www.unicode.org/reports/tr17/ |publisher=Unicode Consortium |access-date=12 August 2023 |date=2022-11-11}}</ref>

An '''abstract character repertoire''' (ACR) is the full set of abstract characters that a system supports. Unicode has an open repertoire, meaning that new characters will be added to the repertoire over time.

A '''coded character set''' (CCS) is a [[function (mathematics)|function]] that maps characters to ''[[code point]]s'' (each code point represents one character). For example, in a given repertoire, the capital letter "A" in the Latin alphabet might be represented by the code point 65, the character "B" by 66, and so on. Multiple coded character sets may share the same character repertoire; for example [[ISO/IEC 8859-1]] and IBM code pages 037 and [[Code page 500|500]] all cover the same repertoire but map them to different code points.

A '''character encoding form''' (CEF) is the mapping of code points to ''code units'' to facilitate storage in a system that represents numbers as bit sequences of fixed length (i.e. practically any computer system). For example, a system that stores numeric information in 16-bit units can only directly represent code points 0 to 65,535 in each unit, but larger code points (say, 65,536 to 1.4&nbsp;million) could be represented by using multiple 16-bit units. This correspondence is defined by a CEF.

A '''character encoding scheme''' (CES) is the mapping of code units to a sequence of octets to facilitate storage on an octet-based file system or transmission over an octet-based network. Simple character encoding schemes include [[UTF-8]], [[UTF-16BE]], [[UTF-32BE]], [[UTF-16LE]], and [[UTF-32LE]]; compound character encoding schemes, such as [[UTF-16]], [[UTF-32]] and [[ISO/IEC 2022]], switch between several simple schemes by using a [[byte order mark]] or [[escape sequence]]s; compressing schemes try to minimize the number of bytes used per code unit (such as [[Standard Compression Scheme for Unicode|SCSU]] and [[Binary Ordered Compression for Unicode|BOCU]]).

Although [[UTF-32BE]] and [[UTF-32LE]] are simpler CESes, most systems working with Unicode use either [[UTF-8]], which is [[backward compatibility|backward compatible]] with fixed-length ASCII and maps Unicode code points to variable-length sequences of octets, or [[UTF-16BE]],{{cn|date=August 2023}} which is [[backward compatibility|backward compatible]] with fixed-length UCS-2BE and maps Unicode code points to variable-length sequences of 16-bit words. See [[comparison of Unicode encodings]] for a detailed discussion.

Finally, there may be a '''higher-level protocol''' which supplies additional information to select the particular variant of a [[Unicode]] character, particularly where there are regional variants that have been 'unified' in Unicode as the same character. An example is the [[XML]] attribute xml:lang.

The Unicode model uses the term "character map" for other systems which directly assign a sequence of characters to a sequence of bytes, covering all of the CCS, CEF and CES layers.<ref name="utr17" />

===Unicode code points===
In Unicode, a character can be referred to as 'U+' followed by its codepoint value in hexadecimal. The range of valid code points (the codespace) for the Unicode standard is U+0000 to U+10FFFF, inclusive, divided in 17 [[Plane (Unicode)|planes]], identified by the numbers 0 to 16. Characters in the range U+0000 to U+FFFF are in plane 0, called the [[Plane (Unicode)#Basic Multilingual Plane|Basic Multilingual Plane]] (BMP). This plane contains the most commonly-used characters. Characters in the range U+10000 to U+10FFFF in the other planes are called [[supplementary characters]].

The following table shows examples of code point values:
{| class="wikitable MsoNormalTable"
! Character
! Unicode code point
! Glyph
|-
| Latin A
| U+0041
| Α
|-
| Latin sharp S
| U+00DF
| ß
|-
| Han for East
| U+6771
| 東
|-
| Ampersand
| U+0026
| &
|-
| Inverted exclamation mark
| U+00A1
| ¡
|-
| Section sign
| U+00A7
| §
|}

===Example===
Consider a [[String (computer science)|string]] of the letters "ab̲c𐐀"—that is, a string containing a Unicode combining character ({{unichar|0332}}) as well as a supplementary character ({{unichar|10400}}). This string has several Unicode representations which are logically equivalent, yet while each is suited to a diverse set of circumstances or range of requirements:
* Four [[Character (computing)|composed characters]]:
*:{{code|a}}, {{code|b̲}}, {{code|c}}, {{code|𐐀}}
* Five [[grapheme]]s:
*:{{code|a}}, {{code|b}}, {{code|_}}, {{code|c}}, {{code|𐐀}}
* Five Unicode [[code point]]s:
*:{{code|U+0061}}, {{code|U+0062}}, {{code|U+0332}}, {{code|U+0063}}, {{code|U+10400}}
* Five UTF-32 code units (32-bit integer values):
*:{{code|0x00000061}}, {{code|0x00000062}}, {{code|0x00000332}}, {{code|0x00000063}}, {{code|0x00010400}}
* Six UTF-16 code units (16-bit integers)
*:{{code|0x0061}}, {{code|0x0062}}, {{code|0x0332}}, {{code|0x0063}}, {{code|0xD801}}, {{code|0xDC00}}
* Nine UTF-8 code units (8-bit values, or [[byte]]s)
*:{{code|0x61}}, {{code|0x62}}, {{code|0xCC}}, {{code|0xB2}}, {{code|0x63}}, {{code|0xF0}}, {{code|0x90}}, {{code|0x90}}, {{code|0x80}}

Note in particular that 𐐀 is represented with either one 32-bit value (UTF-32), two 16-bit values (UTF-16), or four 8-bit values (UTF-8). Although each of those forms uses the same total number of bits (32) to represent the glyph, it is not obvious how the actual numeric byte values are related.

== Transcoding ==
As a result of having many character encoding methods in use (and the need for backward compatibility with archived data), many computer programs have been developed to translate data between character encoding schemes, a process known as [[transcoding]]. Some of these are cited below.

[[Cross-platform]]:
* [[Web browser]]s – most modern web browsers feature automatic [[character encoding detection]]. On Firefox 3, for example, see the View/Character Encoding submenu.
* [[iconv]] – a program and standardized API to convert encodings
* [[luit]] – a program that converts encoding of input and output to programs running interactively
* [[International Components for Unicode]] – A set of C and Java libraries to perform charset conversion. uconv can be used from ICU4C.

[[Microsoft Windows|Windows]]:
* Encoding.Convert – .NET API<ref>{{cite web|url=https://docs.microsoft.com/en-us/dotnet/api/system.text.encoding.convert?redirectedfrom=MSDN&view=net-6.0#overloads|work=Microsoft .NET Framework Class Library|title=Encoding.Convert Method}}</ref>
* MultiByteToWideChar/WideCharToMultiByte – to convert from ANSI to Unicode & Unicode to ANSI<ref>{{cite web|url=https://learn.microsoft.com/en-us/windows/win32/api/stringapiset/nf-stringapiset-multibytetowidechar|title=MultiByteToWideChar function (stringapiset.h)|website=Microsoft Docs|date=13 October 2021 }}</ref><ref>{{cite web|url=https://learn.microsoft.com/en-us/windows/win32/api/stringapiset/nf-stringapiset-widechartomultibyte|title=WideCharToMultiByte function (stringapiset.h)|website=Microsoft Docs|date=9 August 2022 }}</ref>

== Common character encodings ==
{{Main|Popularity of text encodings}}
{{Expand section|Popularity and comparison:
* Statistics on popularity
* Especially, a comparison of the advantages and disadvantages of the few 3-5 most common character encodings (e.g. UTF-8, UTF-16 and UTF-32)|date=June 2024}}
The [[Popularity of text encodings|most used character encoding]] on the [[World Wide Web|web]] is [[UTF-8]], used in 98.2% of surveyed web sites, as of May 2024.<ref name="W3TechsWebEncoding" /> In [[Application software|application programs]] and [[operating system]] tasks, both UTF-8 and [[UTF-16]] are popular options.<ref name=":0" /><ref name=":1">{{Cite web |last=Galloway |first=Matt |date=9 October 2012 |title=Character encoding for iOS developers. Or UTF-8 what now? |url=https://www.galloway.me.uk/2012/10/character-encoding-for-ios-developers-utf8/ |access-date=2021-01-02 |website=Matt Galloway |language=en |quote=in reality, you usually just assume UTF-8 since that is by far the most common encoding. }}</ref>
{{Div col|colwidth=30em}}
* [[ISO/IEC 646|ISO 646]]
** [[ASCII]]
* [[EBCDIC]]
* [[ISO/IEC 8859|ISO 8859]]:
** [[ISO/IEC 8859-1|ISO 8859-1]] Western Europe
** [[ISO/IEC 8859-2|ISO 8859-2]] Western and Central Europe
** [[ISO/IEC 8859-3|ISO 8859-3]] Western Europe and South European (Turkish, Maltese plus Esperanto)
** [[ISO/IEC 8859-4|ISO 8859-4]] Western Europe and Baltic countries (Lithuania, Estonia, Latvia and Lapp)
** [[ISO/IEC 8859-5|ISO 8859-5]] Cyrillic alphabet
** [[ISO/IEC 8859-6|ISO 8859-6]] Arabic
** [[ISO/IEC 8859-7|ISO 8859-7]] Greek
** [[ISO/IEC 8859-8|ISO 8859-8]] Hebrew
** [[ISO/IEC 8859-9|ISO 8859-9]] Western Europe with amended Turkish character set
** [[ISO/IEC 8859-10|ISO 8859-10]] Western Europe with rationalised character set for Nordic languages, including complete Icelandic set
** [[ISO/IEC 8859-11|ISO 8859-11]] Thai
** [[ISO/IEC 8859-13|ISO 8859-13]] Baltic languages plus Polish
** [[ISO/IEC 8859-14|ISO 8859-14]] Celtic languages (Irish Gaelic, Scottish, Welsh)
** [[ISO/IEC 8859-15|ISO 8859-15]] Added the Euro sign and other rationalisations to ISO 8859-1
** [[ISO/IEC 8859-16|ISO 8859-16]] Central, Eastern and Southern European languages (Albanian, Bosnian, Croatian, Hungarian, Polish, Romanian, Serbian and Slovenian, but also French, German, Italian and Irish Gaelic)
* [[Code page 437|CP437]], CP720, [[Code page 737|CP737]], [[Code page 850|CP850]], CP852, CP855, CP857, [[Code page 858|CP858]], CP860, [[Code page 861|CP861]], [[Code page 862|CP862]], [[Code page 863|CP863]], [[Code page 865|CP865]], [[Code page 866|CP866]], [[Code page 869|CP869]], [[Code page 872|CP872]]
* [[Windows code page|MS-Windows character sets]]:
** [[Windows-1250]] for Central European languages that use Latin script, (Polish, Czech, Slovak, Hungarian, Slovene, Serbian, Croatian, Bosnian, Romanian and Albanian)
** [[Windows-1251]] for Cyrillic alphabets
** [[Windows-1252]] for Western languages
** [[Windows-1253]] for Greek
** [[Windows-1254]] for Turkish
** [[Windows-1255]] for Hebrew
** [[Windows-1256]] for Arabic
** [[Windows-1257]] for Baltic languages
** [[Windows-1258]] for Vietnamese
* [[Mac OS Roman]]
* [[KOI8-R]], [[KOI8-U]], [[KOI7]]
* [[MIK Code page|MIK]]
* [[Indian Script Code for Information Interchange|ISCII]]
* [[Tamil Script Code for Information Interchange|TSCII]]
* [[Vietnamese Standard Code for Information Interchange|VISCII]]
* [[JIS X 0208]] is a widely deployed standard for Japanese character encoding that has several encoding forms.
** [[Shift JIS]] (Microsoft [[Code page 932 (Microsoft Windows)|Code page 932]] is a dialect of Shift_JIS)
** [[Extended Unix Code|EUC-JP]]
** [[ISO/IEC 2022|ISO-2022-JP]]
* [[JIS X 0213]] is an extended version of JIS X 0208.
** [[Shift JIS|Shift_JIS-2004]]
** [[Extended Unix Code|EUC-JIS-2004]]
** [[ISO/IEC 2022|ISO-2022-JP-2004]]
* Chinese [[List of GB standards|Guobiao]]
** [[GB 2312]]
** [[GBK (character encoding)|GBK]] (Microsoft Code page 936)
** [[GB 18030]]
* Taiwan [[Big5]] (a more famous variant is Microsoft [[Code page 950]])
** Hong Kong [[HKSCS]]
* Korean
** [[KS X 1001]] is a Korean double-byte character encoding standard
** [[Extended Unix Code#EUC-KR|EUC-KR]]
** [[ISO/IEC 2022|ISO-2022-KR]]
* [[Unicode]] (and subsets thereof, such as the 16-bit 'Basic Multilingual Plane')
** [[UTF-8]]
** [[UTF-16]]
** [[UTF-32]]
* [[ANSEL]] or [[ISO/IEC 6937]]
{{Div col end}}

== See also ==
* [[Percent-encoding]]
* [[Alt code]]
* [[Character encodings in HTML]]
* [[:Category:Character encoding]] – articles related to character encoding in general
* [[:Category:Character sets]] – articles detailing specific character encodings
* [[Hexadecimal#Representing hexadecimal|Hexadecimal representations]]
* ''[[Mojibake]]'' – character set mismap
* [[Mojikyō]] – a system ("glyph set") that includes over 100,000 Chinese character drawings, modern and ancient, popular and obscure
* [[Presentation layer]]
* [[TRON (encoding)|TRON]], part of the TRON project, is an encoding system that does not use Han Unification; instead, it uses "control codes" to switch between 16-bit "planes" of characters.
* [[Universal Character Set characters]]
* [[Charset sniffing]] – used in some applications when character encoding metadata is not available

== References ==
{{Reflist|30em}}

== Further reading ==
* {{cite book |url=https://textfiles.meulie.net/bitsaved/Books/Mackenzie_CodedCharSets.pdf |title=Coded Character Sets, History and Development |series=The Systems Programming Series |author-last=Mackenzie |author-first=Charles E. |date=1980 |edition=1 |publisher=[[Addison-Wesley Publishing Company, Inc.]] |isbn=978-0-201-14460-4 |lccn=77-90165 |access-date=2019-08-25 |archive-url=https://web.archive.org/web/20160526172151/https://textfiles.meulie.net/bitsaved/Books/Mackenzie_CodedCharSets.pdf |archive-date=May 26, 2016 |url-status=live |df=mdy-all }}

== External links ==
{{Commons category|Encodings}}
{{Wikiversity|Character encoding}}
*[https://www.iana.org/assignments/character-sets Character sets registered by Internet Assigned Numbers Authority (IANA)]
*[https://jkorpela.fi/chars/ Characters and encodings], by Jukka Korpela
*[https://www.unicode.org/unicode/reports/tr17/ Unicode Technical Report #17: Character Encoding Model]
*[http://code.cside.com/3rdpage/us/unicode/converter.html Decimal, Hexadecimal Character Codes in HTML Unicode – Encoding converter]
*[https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/ The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)] by Joel Spolsky (Oct 10, 2003)

{{Character encoding|state=collapsed}}

{{DEFAULTSORT:Character Encoding}}
[[Category:Character encoding| ]]
[[Category:Digital typography]]
[[Category:Natural language and computing|Encoding]]