HOME
The Info List - Unicode


--- Advertisement ---



Unicode
Unicode
is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The latest version contains a repertoire of 136,755 characters covering 139 modern and historic scripts, as well as multiple symbol sets. The Unicode
Unicode
Standard is maintained in conjunction with ISO/IEC 10646, and both are code-for-code identical. The Unicode
Unicode
Standard consists of a set of code charts for visual reference, an encoding method and set of standard character encodings, a set of reference data files, and a number of related items, such as character properties, rules for normalization, decomposition, collation, rendering, and bidirectional display order (for the correct display of text containing both right-to-left scripts, such as Arabic and Hebrew, and left-to-right scripts).[1] As of June 2017[update], the most recent version is Unicode
Unicode
10.0. The standard is maintained by the Unicode
Unicode
Consortium. Unicode's success at unifying character sets has led to its widespread and predominant use in the internationalization and localization of computer software. The standard has been implemented in many recent technologies, including modern operating systems, XML, Java (and other programming languages), and the .NET Framework. Unicode
Unicode
can be implemented by different character encodings. The Unicode
Unicode
standard defines UTF-8, UTF-16, and UTF-32, and several other encodings are in use. The most commonly used encodings are UTF-8, UTF-16
UTF-16
and UCS-2, a precursor of UTF-16. UTF-8, dominantly used by websites (over 90%), uses one byte for the first 128 code points, and up to 4 bytes for other characters. The first 128 Unicode
Unicode
code points are the ASCII
ASCII
characters, which means that any ASCII
ASCII
text is also a UTF-8
UTF-8
text. UCS-2 uses two bytes (16 bits) for each character but can only encode the first 65,536 code points, the so-called Basic Multilingual Plane (BMP). With 1,114,112 code points on 17 planes being possible, and with over 137,000 code points defined so far, many Unicode characters are beyond the reach of UCS-2. Therefore, UCS-2 is obsolete, though still widely used in software. UTF-16
UTF-16
extends UCS-2, by using the same 16-bit encoding as UCS-2 for the Basic Multilingual Plane, and a 4-byte encoding for the other planes. As long as it contains no code points in the reserved range U+0D800-U+0DFFF, a UCS-2 text is a valid UTF-16
UTF-16
text. UTF-32 (also referred to as UCS-4) uses four bytes for each character. Like UCS-2, the number of bytes per character is fixed, facilitating character indexing; but unlike UCS-2, UTF-32 is able to encode all Unicode
Unicode
code points. However, because each character uses four bytes, UTF-32 takes significantly more space than other encodings, and is not widely used.

Contents

1 Origin and development

1.1 History 1.2 Architecture and terminology

1.2.1 Code point planes and blocks 1.2.2 General Category property 1.2.3 Abstract characters

1.3 Unicode
Unicode
Consortium 1.4 Versions 1.5 Scripts covered

2 Mapping and encodings

2.1 Unicode
Unicode
Transformation Format and Universal Coded Character Set 2.2 Ready-made versus composite characters 2.3 Ligatures 2.4 Standardized subsets 2.5 Code point lookup

3 Adoption

3.1 Operating systems 3.2 Input methods 3.3 Email 3.4 Web 3.5 Fonts 3.6 Newlines

4 Issues

4.1 Philosophical and completeness criticisms 4.2 Mapping to legacy character sets 4.3 Indic scripts 4.4 Combining characters 4.5 Anomalies

5 See also 6 References 7 Further reading 8 External links

Origin and development[edit] Unicode
Unicode
has the explicit aim of transcending the limitations of traditional character encodings, such as those defined by the ISO 8859 standard, which find wide usage in various countries of the world but remain largely incompatible with each other. Many traditional character encodings share a common problem in that they allow bilingual computer processing (usually using Latin characters and the local script), but not multilingual computer processing (computer processing of arbitrary scripts mixed with each other). Unicode, in intent, encodes the underlying characters—graphemes and grapheme-like units—rather than the variant glyphs (renderings) for such characters. In the case of Chinese characters, this sometimes leads to controversies over distinguishing the underlying character from its variant glyphs (see Han unification). In text processing, Unicode
Unicode
takes the role of providing a unique code point—a number, not a glyph—for each character. In other words, Unicode
Unicode
represents a character in an abstract way and leaves the visual rendering (size, shape, font, or style) to other software, such as a web browser or word processor. This simple aim becomes complicated, however, because of concessions made by Unicode's designers in the hope of encouraging a more rapid adoption of Unicode. The first 256 code points were made identical to the content of ISO-8859-1
ISO-8859-1
so as to make it trivial to convert existing western text. Many essentially identical characters were encoded multiple times at different code points to preserve distinctions used by legacy encodings and therefore, allow conversion from those encodings to Unicode
Unicode
(and back) without losing any information. For example, the "fullwidth forms" section of code points encompasses a full Latin alphabet that is separate from the main Latin alphabet section because in Chinese, Japanese, and Korean (CJK) fonts, these Latin characters are rendered at the same width as CJK ideographs, rather than at half the width. For other examples, see duplicate characters in Unicode. History[edit] Based on experiences with the Xerox Character Code Standard (XCCS) since 1980,[2] the origins of Unicode
Unicode
date to 1987, when Joe Becker from Xerox
Xerox
and Lee Collins and Mark Davis from Apple started investigating the practicalities of creating a universal character set.[3] With additional input from Peter Fenwick and Dave Opstad,[2] Joe Becker published a draft proposal for an "international/multilingual text character encoding system in August 1988, tentatively called Unicode". He explained that "[t]he name 'Unicode' is intended to suggest a unique, unified, universal encoding".[2] In this document, entitled Unicode
Unicode
88, Becker outlined a 16-bit character model:[2]

Unicode
Unicode
is intended to address the need for a workable, reliable world text encoding. Unicode
Unicode
could be roughly described as "wide-body ASCII" that has been stretched to 16 bits to encompass the characters of all the world's living languages. In a properly engineered design, 16 bits per character are more than sufficient for this purpose.

His original 16-bit design was based on the assumption that only those scripts and characters in modern use would need to be encoded:[2]

Unicode
Unicode
gives higher priority to ensuring utility for the future than to preserving past antiquities. Unicode
Unicode
aims in the first instance at the characters published in modern text (e.g. in the union of all newspapers and magazines printed in the world in 1988), whose number is undoubtedly far below 214 = 16,384. Beyond those modern-use characters, all others may be defined to be obsolete or rare; these are better candidates for private-use registration than for congesting the public list of generally useful Unicodes.

In early 1989, the Unicode
Unicode
working group expanded to include Ken Whistler and Mike Kernaghan of Metaphor, Karen Smith-Yoshimura and Joan Aliprand of RLG, and Glenn Wright of Sun Microsystems, and in 1990, Michel Suignard and Asmus Freytag from Microsoft
Microsoft
and Rick McGowan of NeXT
NeXT
joined the group. By the end of 1990, most of the work on mapping existing character encoding standards had been completed, and a final review draft of Unicode
Unicode
was ready. The Unicode Consortium
Unicode Consortium
was incorporated in California on January 3, 1991,[4] and in October 1991, the first volume of the Unicode
Unicode
standard was published. The second volume, covering Han ideographs, was published in June 1992. In 1996, a surrogate character mechanism was implemented in Unicode 2.0, so that Unicode
Unicode
was no longer restricted to 16 bits. This increased the Unicode
Unicode
codespace to over a million code points, which allowed for the encoding of many historic scripts (e.g., Egyptian Hieroglyphs) and thousands of rarely used or obsolete characters that had not been anticipated as needing encoding. Among the characters not originally intended for Unicode
Unicode
are rarely used Kanji
Kanji
or Chinese characters, many of which are part of personal and place names, making them rarely used, but much more essential than envisioned in the original architecture of Unicode.[5] The Microsoft
Microsoft
TrueType
TrueType
specification version 1.0 from 1992 used the name Apple Unicode
Unicode
instead of Unicode
Unicode
for the Platform ID in the naming table. Architecture and terminology[edit] Unicode
Unicode
defines a codespace of 1,114,112 code points in the range 0hex to 10FFFFhex.[6] Normally a Unicode
Unicode
code point is referred to by writing "U+" followed by its hexadecimal number. For code points in the Basic Multilingual Plane
Basic Multilingual Plane
(BMP), four digits are used (e.g., U+0058 for the character LATIN CAPITAL LETTER X); for code points outside the BMP, five or six digits are used, as required (e.g., U+E0001 for the character LANGUAGE TAG and U+10FFFD for the character PRIVATE USE CHARACTER-10FFFD).[7] Code point planes and blocks[edit] Main article: Plane (Unicode) The Unicode
Unicode
codespace is divided into seventeen planes, numbered 0 to 16:

v t e

Unicode
Unicode
planes and used code point ranges

Basic Supplementary

Plane 0 Plane 1 Plane 2 Planes 3–13 Plane 14 Planes 15–16

0000–​FFFF 10000–​1FFFF 20000–​2FFFF 30000–​DFFFF E0000–​EFFFF F0000–​10FFFF

Basic Multilingual Plane Supplementary Multilingual Plane Supplementary Ideographic Plane unassigned Supplement­ary Special-purpose Plane Supplement­ary Private Use Area planes

BMP SMP SIP — SSP SPUA-A/B

0000–​0FFF 1000–​1FFF 2000–​2FFF 3000–​3FFF 4000–​4FFF 5000–​5FFF 6000–​6FFF 7000–​7FFF

8000–​8FFF 9000–​9FFF A000–​AFFF B000–​BFFF C000–​CFFF D000–​DFFF E000–​EFFF F000–​FFFF

10000–​10FFF 11000–​11FFF 12000–​12FFF 13000–​13FFF 14000–​14FFF

16000–​16FFF 17000–​17FFF

18000–​18FFF

1B000–​1BFFF

1D000–​1DFFF 1E000–​1EFFF 1F000–​1FFFF

20000–​20FFF 21000–​21FFF 22000–​22FFF 23000–​23FFF 24000–​24FFF 25000–​25FFF 26000–​26FFF 27000–​27FFF

28000–​28FFF 29000–​29FFF 2A000–​2AFFF 2B000–​2BFFF 2C000–​2CFFF 2D000–​2DFFF 2E000–​2EFFF 2F000–​2FFFF

E0000–​E0FFF

15: SPUA-A F0000–​FFFFF

16: SPUA-B 100000–​10FFFF

All code points in the BMP are accessed as a single code unit in UTF-16
UTF-16
encoding and can be encoded in one, two or three bytes in UTF-8. Code points in Planes 1 through 16 (supplementary planes) are accessed as surrogate pairs in UTF-16
UTF-16
and encoded in four bytes in UTF-8. Within each plane, characters are allocated within named blocks of related characters. Although blocks are an arbitrary size, they are always a multiple of 16 code points and often a multiple of 128 code points. Characters required for a given script may be spread out over several different blocks. General Category property[edit] Each code point has a single General Category property. The major categories are denoted: Letter, Mark, Number, Punctuation, Symbol, Separator and Other. Within these categories, there are subdivisions. In most cases other properties must be used to sufficiently specify the characteristics of a code point. The possible General Categories are:

General Category ( Unicode
Unicode
Character Property)[a]

v t e

Value Category Major, minor Basic type[b] Character assigned[b] Count (as of 10.0) Remarks

 

Letter

Lu Letter, uppercase Graphic Character 1,702

Ll Letter, lowercase Graphic Character 2,063

Lt Letter, titlecase Graphic Character 31 Ligatures containing uppercase followed by lowercase letters (e.g., Dž, Lj, Nj, and Dz)

Lm Letter, modifier Graphic Character 250

Lo Letter, other Graphic Character 121,047

Mark

Mn Mark, nonspacing Graphic Character 1,763

Mc Mark, spacing combining Graphic Character 401

Me Mark, enclosing Graphic Character 13

Number

Nd Number, decimal digit Graphic Character 590 All these, and only these, have Numeric Type = De[c]

Nl Number, letter Graphic Character 236 Numerals composed of letters or letterlike symbols (e.g., Roman numerals)

No Number, other Graphic Character 676 E.g., vulgar fractions, superscript and subscript digits

Punctuation

Pc Punctuation, connector Graphic Character 10 Includes "_" underscore

Pd Punctuation, dash Graphic Character 24 Includes several hyphen characters

Ps Punctuation, open Graphic Character 75 Opening bracket characters

Pe Punctuation, close Graphic Character 73 Closing bracket characters

Pi Punctuation, initial quote Graphic Character 12 Opening quotation mark. Does not include the ASCII
ASCII
"neutral" quotation mark. May behave like Ps or Pe depending on usage

Pf Punctuation, final quote Graphic Character 10 Closing quotation mark. May behave like Ps or Pe depending on usage

Po Punctuation, other Graphic Character 566

Symbol

Sm Symbol, math Graphic Character 948 Mathematical symbols (e.g., +, =, ×, ÷, √, ∊). Does not include parentheses and brackets, which are in categories Ps and Pe. Also does not include !, *, -, or /, which despite frequent use as mathematical operators, are primarily considered to be "punctuation".

Sc Symbol, currency Graphic Character 54 Currency symbols

Sk Symbol, modifier Graphic Character 121

So Symbol, other Graphic Character 5,855

Separator

Zs Separator, space Graphic Character 17 Includes the space, but not TAB, CR, or LF, which are Cc

Zl Separator, line Format Character 1 Only U+2028 LINE SEPARATOR (LSEP)

Zp Separator, paragraph Format Character 1 Only U+2029 PARAGRAPH SEPARATOR (PSEP)

Other

Cc Other, control Control Character 65 (will never change)[c] No name[d], <control>

Cf Other, format Format Character 151 Includes the soft hyphen, control characters to support bi-directional text, and language tag characters

Cs Other, surrogate Surrogate Not (but abstract) 2,048 (will never change)[c] No name[d], <surrogate>

Co Other, private use Private-use Not (but abstract) 137,468 total (will never change)[c] (6,400 in BMP, 131,068 in Planes 15–16) No name[d], <private-use>

Cn Other, not assigned Noncharacter Not 66 (will never change)[c] No name[d], <noncharacter>

Reserved Not 837,775 No name[d], <reserved>

^ "Table 4-4: General Category" (PDF). The Unicode
Unicode
Standard. Unicode Consortium. July 2017.  ^ a b "Table 2-3: Types of code points" (PDF). The Unicode
Unicode
Standard. Unicode
Unicode
Consortium. July 2017.  ^ a b c d e Unicode
Unicode
Character Encoding Stability Policies: Property Value Stability Stability policy: Some gc groups will never change. gc=Nd corresponds with Numeric Type=De (decimal). ^ a b c d e "Table 4-13: Construction of Code Point Labels" (PDF). The Unicode
Unicode
Standard. Unicode
Unicode
Consortium. July 2017.  A Code Point Label may be used to identify a nameless code point. E.g. <control-hhhh>, <control-0088>. The Name remains blank, which can prevent inadvertently replacing, in documentation, a Control Name with a true Control code. Unicode
Unicode
also uses <not a character> for <noncharacter>.

Code points in the range U+D800–U+DBFF (1,024 code points) are known as high-surrogate code points, and code points in the range U+DC00–U+DFFF (1,024 code points) are known as low-surrogate code points. A high-surrogate code point followed by a low-surrogate code point form a surrogate pair in UTF-16
UTF-16
to represent code points greater than U+FFFF. These code points otherwise cannot be used (this rule is ignored often in practice especially when not using UTF-16). A small set of code points are guaranteed never to be used for encoding characters, although applications may make use of these code points internally if they wish. There are sixty-six of these noncharacters: U+FDD0–U+FDEF and any code point ending in the value FFFE or FFFF (i.e., U+FFFE, U+FFFF, U+1FFFE, U+1FFFF, … U+10FFFE, U+10FFFF). The set of noncharacters is stable, and no new noncharacters will ever be defined.[12] Like surrogates, the rule that these cannot be used is often ignored, although the operation of the byte order mark assumes that U+FFFE will never be the first code point in a text. Excluding surrogates and noncharacters leaves 1,111,998 code points available for use. Private-use code points are considered to be assigned characters, but they have no interpretation specified by the Unicode
Unicode
standard[13] so any interchange of such characters requires an agreement between sender and receiver on their interpretation. There are three private-use areas in the Unicode
Unicode
codespace:

Private Use Area: U+E000–U+F8FF (6,400 characters) Supplementary Private Use Area-A: U+F0000–U+FFFFD (65,534 characters) Supplementary Private Use Area-B: U+100000–U+10FFFD (65,534 characters).

Graphic characters are characters defined by Unicode
Unicode
to have a particular semantic, and either have a visible glyph shape or represent a visible space. As of Unicode
Unicode
10.0 there are 136,537 graphic characters. Format characters are characters that do not have a visible appearance, but may have an effect on the appearance or behavior of neighboring characters. For example, U+200C Zero width non-joiner
Zero width non-joiner
and U+200D Zero width joiner may be used to change the default shaping behavior of adjacent characters (e.g., to inhibit ligatures or request ligature formation). There are 153 format characters in Unicode
Unicode
10.0. Sixty-five code points (U+0000–U+001F and U+007F–U+009F) are reserved as control codes, and correspond to the C0 and C1 control codes defined in ISO/IEC 6429. U+0009 (Tab), U+000A (Line Feed), and U+000D (Carriage Return) are widely used in Unicode-encoded texts. In practice the C1 code points are more often used by improperly-translated CP-1252
CP-1252
characters. Graphic characters, format characters, control code characters, and private use characters are known collectively as assigned characters. Reserved code points are those code points which are available for use, but are not yet assigned. As of Unicode
Unicode
10.0 there are 873,775 reserved code points. Abstract characters[edit] The set of graphic and format characters defined by Unicode
Unicode
does not correspond directly to the repertoire of abstract characters that is representable under Unicode. Unicode
Unicode
encodes characters by associating an abstract character with a particular code point.[14] However, not all abstract characters are encoded as a single Unicode
Unicode
character, and some abstract characters may be represented in Unicode
Unicode
by a sequence of two or more characters. For example, a Latin small letter "i" with an ogonek, a dot above, and an acute accent, which is required in Lithuanian, is represented by the character sequence U+012F, U+0307, U+0301. Unicode
Unicode
maintains a list of uniquely named character sequences for abstract characters that are not directly encoded in Unicode.[15] All graphic, format, and private use characters have a unique and immutable name by which they may be identified. This immutability has been guaranteed since Unicode
Unicode
version 2.0 by the Name Stability policy.[12] In cases where the name is seriously defective and misleading, or has a serious typographical error, a formal alias may be defined, and applications are encouraged to use the formal alias in place of the official character name. For example, U+A015 ꀕ YI SYLLABLE WU has the formal alias yi syllable iteration mark, and U+FE18 ︘ PRESENTATION FORM FOR VERTICAL RIGHT WHITE LENTICULAR BRAKCET (sic) has the formal alias presentation form for vertical right white lenticular bracket.[16] Unicode
Unicode
Consortium[edit] Main article: Unicode
Unicode
Consortium The Unicode Consortium
Unicode Consortium
is a nonprofit organization that coordinates Unicode's development. Full members include most of the main computer software and hardware companies with any interest in text-processing standards, including Adobe Systems, Apple, Google, IBM, Microsoft, Oracle Corporation, and Yahoo!.[17] The Consortium has the ambitious goal of eventually replacing existing character encoding schemes with Unicode
Unicode
and its standard Unicode Transformation Format (UTF) schemes, as many of the existing schemes are limited in size and scope and are incompatible with multilingual environments. Versions[edit] Unicode
Unicode
is developed in conjunction with the International Organization for Standardization and shares the character repertoire with ISO/IEC 10646: the Universal Character Set. Unicode
Unicode
and ISO/IEC 10646 function equivalently as character encodings, but The Unicode Standard contains much more information for implementers, covering—in depth—topics such as bitwise encoding, collation and rendering. The Unicode
Unicode
Standard enumerates a multitude of character properties, including those needed for supporting bidirectional text. The two standards do use slightly different terminology. The Consortium first published The Unicode
Unicode
Standard (ISBN 0-321-18578-1) in 1991 and continues to develop standards based on that original work. The latest version of the standard, Unicode
Unicode
10.0, was released in June 2017 and is available from the consortium's website. The last of the major versions (versions x.0) to be published in book form was Unicode
Unicode
5.0 (ISBN 0-321-48091-0), but since Unicode
Unicode
6.0 the full text of the standard is no longer being published in book form. In 2012, however, it was announced that only the core specification for Unicode
Unicode
version 6.1 would be made available as a 692-page print-on-demand paperback.[18] Unlike the previous major version printings of the Standard, the print-on-demand core specification does not include any code charts or standard annexes, but the entire standard, including the core specification, will still remain freely available on the Unicode
Unicode
website. Thus far, the following major and minor versions of the Unicode standard have been published. Update versions, which do not include any changes to character repertoire, are signified by the third number (e.g., "version 4.0.1") and are omitted in the table below.[19]

Unicode
Unicode
versions

Version Date Book Corresponding ISO/IEC 10646 edition Scripts Characters

Total[tablenote 1] Notable additions

1.0.0 October 1991 ISBN 0-201-56788-1 (Vol. 1)

24 7,161 Initial repertoire covers these scripts: Arabic, Armenian, Bengali, Bopomofo, Cyrillic, Devanagari, Georgian, Greek and Coptic, Gujarati, Gurmukhi, Hangul, Hebrew, Hiragana, Kannada, Katakana, Lao, Latin, Malayalam, Oriya, Tamil, Telugu, Thai, and Tibetan.[20]

1.0.1 June 1992 ISBN 0-201-60845-6 (Vol. 2)

25 28,359 The initial set of 20,902 CJK Unified Ideographs is defined.[21]

1.1 June 1993

ISO/IEC 10646-1:1993 24 34,233 4,306 more Hangul
Hangul
syllables added to original set of 2,350 characters. Tibetan removed.[22]

2.0 July 1996 ISBN 0-201-48345-9 ISO/IEC 10646-1:1993 plus Amendments 5, 6 and 7 25 38,950 Original set of Hangul
Hangul
syllables removed, and a new set of 11,172 Hangul
Hangul
syllables added at a new location. Tibetan added back in a new location and with a different character repertoire. Surrogate character mechanism defined, and Plane 15 and Plane 16 Private Use Areas allocated.[23]

2.1 May 1998

ISO/IEC 10646-1:1993 plus Amendments 5, 6 and 7, as well as two characters from Amendment 18 25 38,952 Euro sign
Euro sign
and Object Replacement Character added.[24]

3.0 September 1999 ISBN 0-201-61633-5 ISO/IEC 10646-1:2000 38 49,259 Cherokee, Ethiopic, Khmer, Mongolian, Burmese, Ogham, Runic, Sinhala, Syriac, Thaana, Unified Canadian Aboriginal Syllabics, and Yi Syllables added, as well as a set of Braille
Braille
patterns.[25]

3.1 March 2001

ISO/IEC 10646-1:2000 ISO/IEC 10646-2:2001

41 94,205 Deseret, Gothic and Old Italic added, as well as sets of symbols for Western music and Byzantine music, and 42,711 additional CJK Unified Ideographs.[26]

3.2 March 2002

ISO/IEC 10646-1:2000 plus Amendment 1 ISO/IEC 10646-2:2001

45 95,221 Philippine scripts Buhid, Hanunó'o, Tagalog, and Tagbanwa added.[27]

4.0 April 2003 ISBN 0-321-18578-1 ISO/IEC 10646:2003 52 96,447 Cypriot syllabary, Limbu, Linear B, Osmanya, Shavian, Tai Le, and Ugaritic added, as well as Hexagram symbols.[28]

4.1 March 2005

ISO/IEC 10646:2003 plus Amendment 1 59 97,720 Buginese, Glagolitic, Kharoshthi, New Tai Lue, Old Persian, Syloti Nagri, and Tifinagh
Tifinagh
added, and Coptic was disunified from Greek. Ancient Greek numbers and musical symbols were also added.[29]

5.0 July 2006 ISBN 0-321-48091-0 ISO/IEC 10646:2003 plus Amendments 1 and 2, as well as four characters from Amendment 3 64 99,089 Balinese, Cuneiform, N'Ko, Phags-pa, and Phoenician added.[30]

5.1 April 2008

ISO/IEC 10646:2003 plus Amendments 1, 2, 3 and 4 75 100,713 Carian, Cham, Kayah Li, Lepcha, Lycian, Lydian, Ol Chiki, Rejang, Saurashtra, Sundanese, and Vai added, as well as sets of symbols for the Phaistos Disc, Mahjong
Mahjong
tiles, and Domino tiles. There were also important additions for Burmese, additions of letters and Scribal abbreviations used in medieval manuscripts, and the addition of Capital ẞ.[31]

5.2 October 2009

ISO/IEC 10646:2003 plus Amendments 1, 2, 3, 4, 5 and 6 90 107,361 Avestan, Bamum, Egyptian hieroglyphs
Egyptian hieroglyphs
(the Gardiner Set, comprising 1,071 characters), Imperial Aramaic, Inscriptional Pahlavi, Inscriptional Parthian, Javanese, Kaithi, Lisu, Meetei Mayek, Old South Arabian, Old Turkic, Samaritan, Tai Tham and Tai Viet added. 4,149 additional CJK Unified Ideographs (CJK-C), as well as extended Jamo for Old Hangul, and characters for Vedic Sanskrit.[32]

6.0 October 2010

ISO/IEC 10646:2010 plus the Indian rupee sign 93 109,449 Batak, Brahmi, Mandaic, playing card symbols, transport and map symbols, alchemical symbols, emoticons and emoji. 222 additional CJK Unified Ideographs (CJK-D) added.[33]

6.1 January 2012

ISO/IEC 10646:2012 100 110,181 Chakma, Meroitic cursive, Meroitic hieroglyphs, Miao, Sharada, Sora Sompeng, and Takri.[34]

6.2 September 2012

ISO/IEC 10646:2012 plus the Turkish lira sign 100 110,182 Turkish lira sign.[35]

6.3 September 2013

ISO/IEC 10646:2012 plus six characters 100 110,187 5 bidirectional formatting characters.[36]

7.0 June 2014

ISO/IEC 10646:2012 plus Amendments 1 and 2, as well as the Ruble sign 123 113,021 Bassa Vah, Caucasian Albanian, Duployan, Elbasan, Grantha, Khojki, Khudawadi, Linear A, Mahajani, Manichaean, Mende Kikakui, Modi, Mro, Nabataean, Old North Arabian, Old Permic, Pahawh Hmong, Palmyrene, Pau Cin Hau, Psalter Pahlavi, Siddham, Tirhuta, Warang Citi, and Dingbats.[37]

8.0 June 2015

ISO/IEC 10646:2014 plus Amendment 1, as well as the Lari sign, nine CJK unified ideographs, and 41 emoji characters[38] 129 120,737 Ahom, Anatolian hieroglyphs, Hatran, Multani, Old Hungarian, SignWriting, 5,771 CJK unified ideographs, a set of lowercase letters for Cherokee, and five emoji skin tone modifiers[39]

9.0 June 2016

ISO/IEC 10646:2014 plus Amendments 1 and 2, as well as Adlam, Newa, Japanese TV symbols, and 74 emoji and symbols[40] 135 128,237 Adlam, Bhaiksuki, Marchen, Newa, Osage, Tangut, and 72 emoji[41][42]

10.0 June 2017

ISO/IEC 10646:2017 plus 56 emoji characters, 285 hentaigana characters, and 3 Zanabazar Square characters[43] 139 136,755 Zanabazar Square, Soyombo, Masaram Gondi, Nüshu, hentaigana (non-standard hiragana), 7,494 CJK unified ideographs, and 56 emoji

^ The number of characters listed for each version of Unicode
Unicode
is the total number of graphic, format and control characters (i.e., excluding private-use characters, noncharacters and surrogate code points).

Scripts covered[edit] Main article: Script (Unicode)

Many modern applications can render a substantial subset of the many scripts in Unicode, as demonstrated by this screenshot from the OpenOffice.org
OpenOffice.org
application.

Unicode
Unicode
covers almost all scripts (writing systems) in current use today.[44][not in citation given] A total of 139 scripts are included in the latest version of Unicode (covering alphabets, abugidas and syllabaries), although there are still scripts that are not yet encoded, particularly those mainly used in historical, liturgical, and academic contexts. Further additions of characters to the already encoded scripts, as well as symbols, in particular for mathematics and music (in the form of notes and rhythmic symbols), also occur. The Unicode
Unicode
Roadmap Committee (Michael Everson, Rick McGowan, and Ken Whistler) maintain the list of scripts that are candidates or potential candidates for encoding and their tentative code block assignments on the Unicode
Unicode
Roadmap page of the Unicode Consortium
Unicode Consortium
Web site. For some scripts on the Roadmap, such as Jurchen and Khitan small script, encoding proposals have been made and they are working their way through the approval process. For others scripts, such as Mayan and Rongorongo, no proposal has yet been made, and they await agreement on character repertoire and other details from the user communities involved. Some modern invented scripts which have not yet been included in Unicode
Unicode
(e.g., Tengwar) or which do not qualify for inclusion in Unicode
Unicode
due to lack of real-world use (e.g., Klingon) are listed in the ConScript Unicode
Unicode
Registry, along with unofficial but widely used Private Use Area code assignments. There is also a Medieval Unicode
Unicode
Font
Font
Initiative focused on special Latin medieval characters. Part of these proposals have been already included into Unicode. The Script Encoding Initiative, a project run by Deborah Anderson at the University of California, Berkeley
University of California, Berkeley
was founded in 2002 with the goal of funding proposals for scripts not yet encoded in the standard. The project has become a major source of proposed additions to the standard in recent years.[45] Mapping and encodings[edit] See also: Universal Character Set characters Several mechanisms have been specified for implementing Unicode. The choice depends on available storage space, source code compatibility, and interoperability with other systems. Unicode
Unicode
Transformation Format and Universal Coded Character Set[edit] Unicode
Unicode
defines two mapping methods: the Unicode
Unicode
Transformation Format (UTF) encodings, and the Universal Coded Character Set (UCS) encodings. An encoding maps (possibly a subset of) the range of Unicode
Unicode
code points to sequences of values in some fixed-size range, termed code values. All UTF encodings map all code points (except surrogates) to a unique sequence of bytes.[46] The numbers in the names of the encodings indicate the number of bits per code value (for UTF encodings) or the number of bytes per code value (for UCS encodings). UTF-8
UTF-8
and UTF-16
UTF-16
are probably the most commonly used encodings. UCS-2 is an obsolete subset of UTF-16; UCS-4 and UTF-32 are functionally equivalent. UTF encodings include:

UTF-1, a retired predecessor of UTF-8, maximizes compatibility with ISO 2022, no longer part of The Unicode
Unicode
Standard; UTF-7, a 7-bit encoding sometimes used in e-mail, often considered obsolete (not part of The Unicode
Unicode
Standard, but only documented as an informational RFC, i.e., not on the Internet Standards Track either); UTF-8, an 8-bit variable-width encoding which maximizes compatibility with ASCII; UTF-EBCDIC, an 8-bit variable-width encoding similar to UTF-8, but designed for compatibility with EBCDIC
EBCDIC
(not part of The Unicode Standard); UTF-16, a 16-bit, variable-width encoding; UTF-32, a 32-bit, fixed-width encoding.

UTF-8
UTF-8
uses one to four bytes per code point and, being compact for Latin scripts and ASCII-compatible, provides the de facto standard encoding for interchange of Unicode
Unicode
text. It is used by FreeBSD
FreeBSD
and most recent Linux distributions
Linux distributions
as a direct replacement for legacy encodings in general text handling. The UCS-2 and UTF-16
UTF-16
encodings specify the Unicode
Unicode
Byte
Byte
Order Mark (BOM) for use at the beginnings of text files, which may be used for byte ordering detection (or byte endianness detection). The BOM, code point U+FEFF has the important property of unambiguity on byte reorder, regardless of the Unicode
Unicode
encoding used; U+FFFE (the result of byte-swapping U+FEFF) does not equate to a legal character, and U+FEFF in other places, other than the beginning of text, conveys the zero-width non-break space (a character with no appearance and no effect other than preventing the formation of ligatures). The same character converted to UTF-8
UTF-8
becomes the byte sequence EF BB BF. The Unicode
Unicode
Standard allows that the BOM "can serve as signature for UTF-8
UTF-8
encoded text where the character set is unmarked".[47] Some software developers have adopted it for other encodings, including UTF-8, in an attempt to distinguish UTF-8
UTF-8
from local 8-bit code pages. However RFC 3629, the UTF-8
UTF-8
standard, recommends that byte order marks be forbidden in protocols using UTF-8, but discusses the cases where this may not be possible. In addition, the large restriction on possible patterns in UTF-8
UTF-8
(for instance there cannot be any lone bytes with the high bit set) means that it should be possible to distinguish UTF-8
UTF-8
from other character encodings without relying on the BOM. In UTF-32 and UCS-4, one 32-bit
32-bit
code value serves as a fairly direct representation of any character's code point (although the endianness, which varies across different platforms, affects how the code value manifests as an octet sequence). In the other encodings, each code point may be represented by a variable number of code values. UTF-32 is widely used as an internal representation of text in programs (as opposed to stored or transmitted text), since every Unix operating system that uses the gcc compilers to generate software uses it as the standard "wide character" encoding. Some programming languages, such as Seed7, use UTF-32 as internal representation for strings and characters. Recent versions of the Python programming language (beginning with 2.2) may also be configured to use UTF-32 as the representation for Unicode
Unicode
strings, effectively disseminating such encoding in high-level coded software. Punycode, another encoding form, enables the encoding of Unicode strings into the limited character set supported by the ASCII-based Domain Name System
Domain Name System
(DNS). The encoding is used as part of IDNA, which is a system enabling the use of Internationalized Domain Names
Internationalized Domain Names
in all scripts that are supported by Unicode. Earlier and now historical proposals include UTF-5 and UTF-6. GB18030
GB18030
is another encoding form for Unicode, from the Standardization Administration of China. It is the official character set of the People's Republic of China
People's Republic of China
(PRC). BOCU-1 and SCSU are Unicode compression schemes. The April Fools' Day RFC of 2005 specified two parody UTF encodings, UTF-9 and UTF-18. Ready-made versus composite characters[edit] Unicode
Unicode
includes a mechanism for modifying character shape that greatly extends the supported glyph repertoire. This covers the use of combining diacritical marks. They are inserted after the main character. Multiple combining diacritics may be stacked over the same character. Unicode
Unicode
also contains precomposed versions of most letter/diacritic combinations in normal use. These make conversion to and from legacy encodings simpler, and allow applications to use Unicode
Unicode
as an internal text format without having to implement combining characters. For example, é can be represented in Unicode
Unicode
as U+0065 (LATIN SMALL LETTER E) followed by U+0301 (COMBINING ACUTE ACCENT), but it can also be represented as the precomposed character U+00E9 (LATIN SMALL LETTER E WITH ACUTE). Thus, in many cases, users have multiple ways of encoding the same character. To deal with this, Unicode
Unicode
provides the mechanism of canonical equivalence. An example of this arises with Hangul, the Korean alphabet. Unicode provides a mechanism for composing Hangul
Hangul
syllables with their individual subcomponents, known as Hangul
Hangul
Jamo. However, it also provides 11,172 combinations of precomposed syllables made from the most common jamo. The CJK ideographs currently have codes only for their precomposed form. Still, most of those ideographs comprise simpler elements (often called radicals in English), so in principle, Unicode
Unicode
could have decomposed them, as it did with Hangul. This would have greatly reduced the number of required code points, while allowing the display of virtually every conceivable ideograph (which might do away with some of the problems caused by Han unification). A similar idea is used by some input methods, such as Cangjie and Wubi. However, attempts to do this for character encoding have stumbled over the fact that ideographs do not decompose as simply or as regularly as Hangul does. A set of radicals was provided in Unicode
Unicode
3.0 ( CJK radicals between U+2E80 and U+2EFF, KangXi radicals in U+2F00 to U+2FDF, and ideographic description characters from U+2FF0 to U+2FFB), but the Unicode
Unicode
standard (ch. 12.2 of Unicode
Unicode
5.2) warns against using ideographic description sequences as an alternate representation for previously encoded characters:

This process is different from a formal encoding of an ideograph. There is no canonical description of unencoded ideographs; there is no semantic assigned to described ideographs; there is no equivalence defined for described ideographs. Conceptually, ideographic descriptions are more akin to the English phrase "an 'e' with an acute accent on it" than to the character sequence <U+0065, U+0301>.

Ligatures[edit] Many scripts, including Arabic and Devanagari, have special orthographic rules that require certain combinations of letterforms to be combined into special ligature forms. The rules governing ligature formation can be quite complex, requiring special script-shaping technologies such as ACE (Arabic Calligraphic Engine by DecoType in the 1980s and used to generate all the Arabic examples in the printed editions of the Unicode
Unicode
Standard), which became the proof of concept for OpenType
OpenType
(by Adobe and Microsoft), Graphite (by SIL International), or AAT (by Apple). Instructions are also embedded in fonts to tell the operating system how to properly output different character sequences. A simple solution to the placement of combining marks or diacritics is assigning the marks a width of zero and placing the glyph itself to the left or right of the left sidebearing (depending on the direction of the script they are intended to be used with). A mark handled this way will appear over whatever character precedes it, but will not adjust its position relative to the width or height of the base glyph; it may be visually awkward and it may overlap some glyphs. Real stacking is impossible, but can be approximated in limited cases (for example, Thai top-combining vowels and tone marks can just be at different heights to start with). Generally this approach is only effective in monospaced fonts, but may be used as a fallback rendering method when more complex methods fail. Standardized subsets[edit] Several subsets of Unicode
Unicode
are standardized: Microsoft
Microsoft
Windows since Windows NT 4.0
Windows NT 4.0
supports WGL-4 with 656 characters, which is considered to support all contemporary European languages using the Latin, Greek, or Cyrillic
Cyrillic
script. Other standardized subsets of Unicode
Unicode
include the Multilingual European Subsets:[48] MES-1 (Latin scripts only, 335 characters), MES-2 (Latin, Greek and Cyrillic
Cyrillic
1062 characters)[49] and MES-3A & MES-3B (two larger subsets, not shown here). Note that MES-2 includes every character in MES-1 and WGL-4.

WGL-4, MES-1 and MES-2

Row Cells Range(s)

00 20–7E Basic Latin (00–7F)

A0–FF Latin-1 Supplement (80–FF)

01 00–13, 14–15, 16–2B, 2C–2D, 2E–4D, 4E–4F, 50–7E, 7F Latin Extended-A (00–7F)

8F, 92, B7, DE-EF, FA–FF Latin Extended-B (80–FF ...)

02 18–1B, 1E–1F Latin Extended-B (... 00–4F)

59, 7C, 92 IPA Extensions (50–AF)

BB–BD, C6, C7, C9, D6, D8–DB, DC, DD, DF, EE Spacing Modifier Letters (B0–FF)

03 74–75, 7A, 7E, 84–8A, 8C, 8E–A1, A3–CE, D7, DA–E1 Greek (70–FF)

04 00–5F, 90–91, 92–C4, C7–C8, CB–CC, D0–EB, EE–F5, F8–F9 Cyrillic
Cyrillic
(00–FF)

1E 02–03, 0A–0B, 1E–1F, 40–41, 56–57, 60–61, 6A–6B, 80–85, 9B, F2–F3 Latin Extended Additional (00–FF)

1F 00–15, 18–1D, 20–45, 48–4D, 50–57, 59, 5B, 5D, 5F–7D, 80–B4, B6–C4, C6–D3, D6–DB, DD–EF, F2–F4, F6–FE Greek Extended (00–FF)

20 13–14, 15, 17, 18–19, 1A–1B, 1C–1D, 1E, 20–22, 26, 30, 32–33, 39–3A, 3C, 3E, 44, 4A General Punctuation (00–6F)

7F, 82 Superscripts and Subscripts (70–9F)

A3–A4, A7, AC, AF Currency Symbols (A0–CF)

21 05, 13, 16, 22, 26, 2E Letterlike Symbols (00–4F)

5B–5E Number
Number
Forms (50–8F)

90–93, 94–95, A8 Arrows (90–FF)

22 00, 02, 03, 06, 08–09, 0F, 11–12, 15, 19–1A, 1E–1F, 27–28, 29, 2A, 2B, 48, 59, 60–61, 64–65, 82–83, 95, 97 Mathematical Operators (00–FF)

23 02, 0A, 20–21, 29–2A Miscellaneous Technical (00–FF)

25 00, 02, 0C, 10, 14, 18, 1C, 24, 2C, 34, 3C, 50–6C Box Drawing (00–7F)

80, 84, 88, 8C, 90–93 Block Elements (80–9F)

A0–A1, AA–AC, B2, BA, BC, C4, CA–CB, CF, D8–D9, E6 Geometric Shapes (A0–FF)

26 3A–3C, 40, 42, 60, 63, 65–66, 6A, 6B Miscellaneous Symbols (00–FF)

F0 (01–02) Private Use Area (00–FF ...)

FB 01–02 Alphabetic Presentation Forms (00–4F)

FF FD Specials

Rendering software which cannot process a Unicode
Unicode
character appropriately often displays it as an open rectangle, or the Unicode "replacement character" (U+FFFD, �), to indicate the position of the unrecognized character. Some systems have made attempts to provide more information about such characters. Apple's Last Resort font
Last Resort font
will display a substitute glyph indicating the Unicode
Unicode
range of the character, and the SIL International's Unicode
Unicode
Fallback font will display a box showing the hexadecimal scalar value of the character. Code point lookup[edit] Online tools for finding the code point for a known character include Unicode
Unicode
Lookup[50] by Jonathan Hedley and Shapecatcher[51] by Benjamin Milde. In Unicode
Unicode
Lookup, one enters a search key (e.g. "fractions"), and a list of corresponding characters with their code points is returned. In Shapecatcher, based on Shape context, one draws the character in a box and a list of characters approximating the drawing, with their code points, is returned. Adoption[edit] Operating systems[edit] Unicode
Unicode
has become the dominant scheme for internal processing and storage of text. Although a great deal of text is still stored in legacy encodings, Unicode
Unicode
is used almost exclusively for building new information processing systems. Early adopters tended to use UCS-2 (the fixed-width two-byte precursor to UTF-16) and later moved to UTF-16
UTF-16
(the variable-width current standard), as this was the least disruptive way to add support for non-BMP characters. The best known such system is Windows NT
Windows NT
(and its descendants, Windows 2000, Windows XP, Windows Vista, Windows 7, Windows 8
Windows 8
and Windows 10), which uses UTF-16
UTF-16
as the sole internal character encoding. The Java and .NET bytecode environments, macOS, and KDE
KDE
also use it for internal representation. Unicode
Unicode
is available on Windows 95
Windows 95
through Microsoft Layer for Unicode, as well as on its descendants, Windows 98
Windows 98
and Windows ME. UTF-8
UTF-8
(originally developed for Plan 9)[52] has become the main storage encoding on most Unix-like
Unix-like
operating systems (though others are also used by some libraries) because it is a relatively easy replacement for traditional extended ASCII
ASCII
character sets. UTF-8
UTF-8
is also the most common Unicode
Unicode
encoding used in HTML
HTML
documents on the World Wide Web. Multilingual text-rendering engines which use Unicode
Unicode
include Uniscribe and DirectWrite for Microsoft
Microsoft
Windows, ATSUI
ATSUI
and Core Text for macOS, and Pango
Pango
for GTK + and the GNOME
GNOME
desktop. Input methods[edit] Main article: Unicode
Unicode
input Because keyboard layouts cannot have simple key combinations for all characters, several operating systems provide alternative input methods that allow access to the entire repertoire. ISO/IEC 14755,[53] which standardises methods for entering Unicode characters from their code points, specifies several methods. There is the Basic method, where a beginning sequence is followed by the hexadecimal representation of the code point and the ending sequence. There is also a screen-selection entry method specified, where the characters are listed in a table in a screen, such as with a character map program. Email[edit] Main article: Unicode
Unicode
and email MIME defines two different mechanisms for encoding non-ASCII characters in email, depending on whether the characters are in email headers (such as the "Subject:"), or in the text body of the message; in both cases, the original character set is identified as well as a transfer encoding. For email transmission of Unicode, the UTF-8 character set and the Base64
Base64
or the Quoted-printable transfer encoding are recommended, depending on whether much of the message consists of ASCII
ASCII
characters. The details of the two different mechanisms are specified in the MIME standards and generally are hidden from users of email software. The adoption of Unicode
Unicode
in email has been very slow. Some East Asian text is still encoded in encodings such as ISO-2022, and some devices, such as mobile phones, still cannot correctly handle Unicode
Unicode
data. Support has been improving, however. Many major free mail providers such as Yahoo, Google
Google
(Gmail), and Microsoft
Microsoft
(Outlook.com) support it. Web[edit] Main article: Unicode
Unicode
and HTML All W3C
W3C
recommendations have used Unicode
Unicode
as their document character set since HTML
HTML
4.0. Web browsers have supported Unicode, especially UTF-8, for many years. There used to be display problems resulting primarily from font related issues; e.g. v 6 and older of Microsoft Internet Explorer
Internet Explorer
did not render many code points unless explicitly told to use a font that contains them.[54] Although syntax rules may affect the order in which characters are allowed to appear, XML
XML
(including XHTML) documents, by definition,[55] comprise characters from most of the Unicode
Unicode
code points, with the exception of:

most of the C0 control codes the permanently unassigned code points D800–DFFF FFFE or FFFF

HTML
HTML
characters manifest either directly as bytes according to document's encoding, if the encoding supports them, or users may write them as numeric character references based on the character's Unicode code point. For example, the references &#916;, &#1049;, &#1511;, &#1605;, &#3671;, &#12354;, &#21494;, &#33865;, and &#47568; (or the same numeric values expressed in hexadecimal, with &#x as the prefix) should display on all browsers as Δ, Й, ק ,م, ๗, あ, 叶, 葉, and 말. When specifying URIs, for example as URLs in HTTP
HTTP
requests, non-ASCII characters must be percent-encoded. Fonts[edit] Main article: Unicode
Unicode
typeface Free and retail fonts based on Unicode
Unicode
are widely available, since TrueType
TrueType
and OpenType
OpenType
support Unicode. These font formats map Unicode code points to glyphs. Thousands of fonts exist on the market, but fewer than a dozen fonts—sometimes described as "pan-Unicode" fonts—attempt to support the majority of Unicode's character repertoire. Instead, Unicode-based fonts typically focus on supporting only basic ASCII
ASCII
and particular scripts or sets of characters or symbols. Several reasons justify this approach: applications and documents rarely need to render characters from more than one or two writing systems; fonts tend to demand resources in computing environments; and operating systems and applications show increasing intelligence in regard to obtaining glyph information from separate font files as needed, i.e., font substitution. Furthermore, designing a consistent set of rendering instructions for tens of thousands of glyphs constitutes a monumental task; such a venture passes the point of diminishing returns for most typefaces. Newlines[edit] Unicode
Unicode
partially addresses the newline problem that occurs when trying to read a text file on different platforms. Unicode
Unicode
defines a large number of characters that conforming applications should recognize as line terminators. In terms of the newline, Unicode
Unicode
introduced U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR. This was an attempt to provide a Unicode solution to encoding paragraphs and lines semantically, potentially replacing all of the various platform solutions. In doing so, Unicode does provide a way around the historical platform dependent solutions. Nonetheless, few if any Unicode
Unicode
solutions have adopted these Unicode line and paragraph separators as the sole canonical line ending characters. However, a common approach to solving this issue is through newline normalization. This is achieved with the Cocoa text system in Mac OS X and also with W3C
W3C
XML
XML
and HTML
HTML
recommendations. In this approach every possible newline character is converted internally to a common newline (which one does not really matter since it is an internal operation just for rendering). In other words, the text system can correctly treat the character as a newline, regardless of the input's actual encoding. Issues[edit] Philosophical and completeness criticisms[edit] Han unification
Han unification
(the identification of forms in the East Asian languages which one can treat as stylistic variations of the same historical character) has become one of the most controversial aspects of Unicode, despite the presence of a majority of experts from all three regions in the Ideographic Rapporteur Group (IRG), which advises the Consortium and ISO on additions to the repertoire and on Han unification.[56] Unicode
Unicode
has been criticized for failing to separately encode older and alternative forms of kanji which, critics argue, complicates the processing of ancient Japanese and uncommon Japanese names. This is often due to the fact that Unicode
Unicode
encodes characters rather than glyphs (the visual representations of the basic character that often vary from one language to another). Unification of glyphs leads to the perception that the languages themselves, not just the basic character representation, are being merged.[57][clarification needed] There have been several attempts to create alternative encodings that preserve the stylistic differences between Chinese, Japanese, and Korean characters in opposition to Unicode's policy of Han unification. An example of one is TRON (although it is not widely adopted in Japan, there are some users who need to handle historical Japanese text and favor it). Although the repertoire of fewer than 21,000 Han characters in the earliest version of Unicode
Unicode
was largely limited to characters in common modern usage, Unicode
Unicode
now includes more than 87,000 Han characters, and work is continuing to add thousands more historic and dialectal characters used in China, Japan, Korea, Taiwan, and Vietnam. Modern font technology provides a means to address the practical issue of needing to depict a unified Han character in terms of a collection of alternative glyph representations, in the form of Unicode
Unicode
variation sequences. For example, the Advanced Typographic tables of OpenType permit one of a number of alternative glyph representations to be selected when performing the character to glyph mapping process. In this case, information can be provided within plain text to designate which alternate character form to select.

Various Cyrillic
Cyrillic
characters shown with and without italics.

If the difference in the appropriate glyphs for two characters in the same script differ only in the italic, Unicode
Unicode
has generally unified them, as can be seen in the comparison between Russian (labeled standard) and Serbian characters at right, meaning that the differences are displayed through smart font technology or manually changing fonts. Mapping to legacy character sets[edit] Unicode
Unicode
was designed to provide code-point-by-code-point round-trip format conversion to and from any preexisting character encodings, so that text files in older character sets can be converted to Unicode and then back and get back the same file, without employing context-dependent interpretation. That has meant that inconsistent legacy architectures, such as combining diacritics and precomposed characters, both exist in Unicode, giving more than one method of representing some text. This is most pronounced in the three different encoding forms for Korean Hangul. Since version 3.0, any precomposed characters that can be represented by a combining sequence of already existing characters can no longer be added to the standard in order to preserve interoperability between software using different versions of Unicode. Injective
Injective
mappings must be provided between characters in existing legacy character sets and characters in Unicode
Unicode
to facilitate conversion to Unicode
Unicode
and allow interoperability with legacy software. Lack of consistency in various mappings between earlier Japanese encodings such as Shift-JIS
Shift-JIS
or EUC-JP
EUC-JP
and Unicode
Unicode
led to round-trip format conversion mismatches, particularly the mapping of the character JIS X 0208 '~' (1-33, WAVE DASH), heavily used in legacy database data, to either U+FF5E ~ FULLWIDTH TILDE (in Microsoft Windows) or U+301C 〜 WAVE DASH (other vendors).[58] Some Japanese computer programmers objected to Unicode
Unicode
because it requires them to separate the use of U+005C REVERSE SOLIDUS (backslash) and U+00A5 ¥ YEN SIGN, which was mapped to 0x5C in JIS X 0201, and a lot of legacy code exists with this usage.[59] (This encoding also replaces tilde '~' 0x7E with macron '¯', now 0xAF.) The separation of these characters exists in ISO 8859-1, from long before Unicode. Indic scripts[edit] Indic scripts such as Tamil and Devanagari
Devanagari
are each allocated only 128 code points, matching the ISCII standard. The correct rendering of Unicode
Unicode
Indic text requires transforming the stored logical order characters into visual order and the forming of ligatures (aka conjuncts) out of components. Some local scholars argued in favor of assignments of Unicode
Unicode
code points to these ligatures, going against the practice for other writing systems, though Unicode
Unicode
contains some Arabic and other ligatures for backward compatibility purposes only.[60][61][62] Encoding of any new ligatures in Unicode
Unicode
will not happen, in part because the set of ligatures is font-dependent, and Unicode
Unicode
is an encoding independent of font variations. The same kind of issue arose for the Tibetan script
Tibetan script
in 2003 when the Standardization Administration of China proposed encoding 956 precomposed Tibetan syllables,[63] but these were rejected for encoding by the relevant ISO committee (ISO/IEC JTC 1/SC 2).[64] Thai alphabet
Thai alphabet
support has been criticized for its ordering of Thai characters. The vowels เ, แ, โ, ใ, ไ that are written to the left of the preceding consonant are in visual order instead of phonetic order, unlike the Unicode
Unicode
representations of other Indic scripts. This complication is due to Unicode
Unicode
inheriting the Thai Industrial Standard 620, which worked in the same way, and was the way in which Thai had always been written on keyboards. This ordering problem complicates the Unicode
Unicode
collation process slightly, requiring table lookups to reorder Thai characters for collation.[57] Even if Unicode
Unicode
had adopted encoding according to spoken order, it would still be problematic to collate words in dictionary order. E.g., the word แสดง  [sa dɛːŋ] "perform" starts with a consonant cluster "สด" (with an inherent vowel for the consonant "ส"), the vowel แ-, in spoken order would come after the ด, but in a dictionary, the word is collated as it is written, with the vowel following the ส. Combining characters[edit] Main article: Combining character See also: Unicode normalization § Normalization Characters with diacritical marks can generally be represented either as a single precomposed character or as a decomposed sequence of a base letter plus one or more non-spacing marks. For example, ḗ (precomposed e with macron and acute above) and ḗ (e followed by the combining macron above and combining acute above) should be rendered identically, both appearing as an e with a macron and acute accent, but in practice, their appearance may vary depending upon what rendering engine and fonts are being used to display the characters. Similarly, underdots, as needed in the romanization of Indic, will often be placed incorrectly[citation needed]. Unicode
Unicode
characters that map to precomposed glyphs can be used in many cases, thus avoiding the problem, but where no precomposed character has been encoded the problem can often be solved by using a specialist Unicode font such as Charis SIL
Charis SIL
that uses Graphite, OpenType, or AAT technologies for advanced rendering features. Anomalies[edit] The Unicode
Unicode
standard has imposed rules intended to guarantee stability.[65] Depending on the strictness of a rule, a change can be prohibited or allowed. For example, a "name" given to a code point can not and will not change. But a "script" property is more flexible, by Unicode's own rules. In version 2.0, Unicode
Unicode
changed many code point "names" from version 1. At the same moment, Unicode
Unicode
stated that from then on, an assigned name to a code point will never change anymore. This implies that when mistakes are published, these mistakes cannot be corrected, even if they are trivial (as happened in one instance with the spelling BRAKCET for BRACKET in a character name). In 2006 a list of anomalies in character names was first published, for example:[66]

U+2118 ℘ script capital p (HTML &#8472; · &weierp;): it is not a capital

The name says "capital", but it is a small letter. The true capital is U+1D4AB 𝒫 MATHEMATICAL SCRIPT CAPITAL P (HTML &#119979;)[67]

U+034F ͏ COMBINING GRAPHEME JOINER (HTML &#847;): Does not join graphemes.[66] U+A015 ꀕ YI SYLLABLE WU (HTML &#40981;): This is not a Yi syllable, but a Yi iteration mark. Its name, however, cannot be changed due to the policy of the Consortium. U+FE18 ︘ PRESENTATION FORM FOR VERTICAL RIGHT WHITE LENTICULAR BRAKCET (HTML &#65048;): bracket is spelled incorrectly. Since this is the fixed character name by policy, it cannot be changed.[68]

See also[edit]

Comparison of Unicode
Unicode
encodings Cultural, political, and religious symbols in Unicode International Components for Unicode (ICU), now as ICU-TC a part of Unicode List of binary codes List of Unicode
Unicode
characters List of XML
XML
and HTML
HTML
character entity references Open-source Unicode
Unicode
typefaces Standards related to Unicode Unicode
Unicode
symbols Universal Character Set Lotus Multi- Byte
Byte
Character Set (LMBCS), a parallel development with similar intentions

References[edit]

^ "The Unicode
Unicode
Standard: A Technical Introduction". Retrieved 2010-03-16.  ^ a b c d e Becker, Joseph D. (1998-09-10) [1988-08-29]. " Unicode
Unicode
88" (PDF). unicode.org (10th anniversary reprint ed.). Unicode
Unicode
Consortium. Archived (PDF) from the original on 2016-11-25. Retrieved 2016-10-25. In 1978, the initial proposal for a set of "Universal Signs" was made by Bob Belleville at Xerox
Xerox
PARC. Many persons contributed ideas to the development of a new encoding design. Beginning in 1980, these efforts evolved into the Xerox Character Code Standard (XCCS) by the present author, a multilingual encoding which has been maintained by Xerox
Xerox
as an internal corporate standard since 1982, through the efforts of Ed Smura, Ron Pellar, and others. Unicode
Unicode
arose as the result of eight years of working experience with XCCS. Its fundamental differences from XCCS were proposed by Peter Fenwick and Dave Opstad (pure 16-bit codes), and by Lee Collins (ideographic character unification). Unicode
Unicode
retains the many features of XCCS whose utility have been proved over the years in an international line of communication multilingual system products.  ^ "Summary Narrative". Retrieved 2010-03-15.  ^ History of Unicode
Unicode
Release and Publication Dates on unicode.org. Retrieved February 28, 2017. ^ Searle, Stephen J. " Unicode
Unicode
Revisited". Retrieved 2013-01-18.  ^ "Glossary of Unicode
Unicode
Terms". Retrieved 2010-03-16.  ^ "Appendix A: Notational Conventions" (PDF). The Unicode
Unicode
Standard. Unicode
Unicode
Consortium. June 2017.  ^ a b " Unicode
Unicode
Character Encoding Stability Policy". Retrieved 2010-03-16.  ^ "Properties" (PDF). Retrieved 2010-03-16.  ^ " Unicode
Unicode
Character Encoding Model". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Named Sequences". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Name Aliases". Retrieved 2010-03-16.  ^ "The Unicode Consortium
Unicode Consortium
Members". Retrieved 2010-03-16.  ^ " Unicode
Unicode
6.1 Paperback Available". announcements_at_unicode.org. Retrieved 2012-05-30.  ^ "Enumerated Versions of The Unicode
Unicode
Standard". Retrieved 2016-06-21.  ^ " Unicode
Unicode
Data 1.0.0". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data 1.0.1". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data 1995". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data-2.0.14". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data-2.1.2". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data-3.0.0". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data-3.1.0". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data-3.2.0". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data-4.0.0". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data". Retrieved 2010-03-16.  ^ " Unicode
Unicode
Data 5.0.0". Retrieved 2010-03-17.  ^ " Unicode
Unicode
Data 5.1.0". Retrieved 2010-03-17.  ^ " Unicode
Unicode
Data 5.2.0". Retrieved 2010-03-17.  ^ " Unicode
Unicode
Data 6.0.0". Retrieved 2010-10-11.  ^ " Unicode
Unicode
Data 6.1.0". Retrieved 2012-01-31.  ^ " Unicode
Unicode
Data 6.2.0". Retrieved 2012-09-26.  ^ " Unicode
Unicode
Data 6.3.0". Retrieved 2013-09-30.  ^ " Unicode
Unicode
Data 7.0.0". Retrieved 2014-06-15.  ^ " Unicode
Unicode
8.0.0". Unicode
Unicode
Consortium. Retrieved 2015-06-17.  ^ " Unicode
Unicode
Data 8.0.0". Retrieved 2015-06-17.  ^ " Unicode
Unicode
9.0.0". Unicode
Unicode
Consortium. Retrieved 2016-06-21.  ^ " Unicode
Unicode
Data 9.0.0". Retrieved 2016-06-21.  ^ Lobao, Martim (7 June 2016). "These Are The Two Emoji
Emoji
That Weren't Approved For Unicode
Unicode
9 But Which Google
Google
Added To Android Anyway". Android Police. Retrieved 4 September 2016.  ^ " Unicode
Unicode
10.0.0". Unicode
Unicode
Consortium. Retrieved 2017-06-20.  ^ "Character Code Charts". Retrieved 2010-03-17.  ^ "About The Script Encoding Initiative". The Unicode
Unicode
Consortium. Retrieved 2012-06-04.  ^ "UTF-8, UTF-16, UTF-32 & BOM". Unicode.org FAQ. Retrieved 12 December 2016.  ^ The Unicode
Unicode
Standard, Version 6.2. The Unicode
Unicode
Consortium. 2013. p. 561. ISBN 978-1-936213-08-5.  ^ CWA 13873:2000 – Multilingual European Subsets in ISO/IEC 10646-1 CEN Workshop Agreement 13873 ^ Multilingual European Character Set 2 (MES-2) Rationale, Markus Kuhn, 1998 ^ Hedley, Jonathan (2009). " Unicode
Unicode
Lookup".  ^ Milde, Benjamin (2011). " Unicode
Unicode
Character Recognition".  ^ Pike, Rob (2003-04-30). " UTF-8
UTF-8
history".  ^ "ISO/IEC JTC1/SC 18/WG 9 N" (PDF). Retrieved 2012-06-04.  ^ Wood, Alan. "Setting up Windows Internet Explorer
Internet Explorer
5, 5.5 and 6 for Multilingual and Unicode
Unicode
Support". Alan Wood. Retrieved 2012-06-04.  ^ "Extensible Markup Language (XML) 1.1 (Second Edition)". Retrieved 2013-11-01.  ^ A Brief History of Character Codes, Steven J. Searle, originally written 1999, last updated 2004 ^ a b The secret life of Unicode: A peek at Unicode's soft underbelly, Suzanne Topping, 1 May 2001 (Internet Archive) ^ AFII contribution about WAVE DASH, Unicode
Unicode
vendor-specific character table for Japanese ^ ISO 646-* Problem, Section 4.4.3.5 of Introduction to I18n, Tomohiro KUBOTA, 2001 ^ "Arabic Presentation Forms-A" (PDF). Retrieved 2010-03-20.  ^ "Arabic Presentation Forms-B" (PDF). Retrieved 2010-03-20.  ^ "Alphabetic Presentation Forms" (PDF). Retrieved 2010-03-20.  ^ China (2 December 2002). "Proposal on Tibetan BrdaRten Characters Encoding for ISO/IEC 10646 in BMP" (PDF).  ^ V. S. Umamaheswaran (7 November 2003). "Resolutions of WG 2 meeting 44" (PDF). Resolution M44.20.  ^ Unicode
Unicode
stability policy ^ a b " Unicode
Unicode
Technical Note #27: Known Anomalies in Unicode Character Names". unicode.org. 10 April 2017.  ^ Unicode
Unicode
chart: "actually this has the form of a lowercase calligraphic p, despite its name" ^ "Misspelling of BRACKET in character name is a known defect"

Further reading[edit]

The Unicode
Unicode
Standard, Version 3.0, The Unicode
Unicode
Consortium, Addison-Wesley Longman, Inc., April 2000. ISBN 0-201-61633-5 The Unicode
Unicode
Standard, Version 4.0, The Unicode
Unicode
Consortium, Addison-Wesley Professional, 27 August 2003. ISBN 0-321-18578-1 The Unicode
Unicode
Standard, Version 5.0, Fifth Edition, The Unicode Consortium, Addison-Wesley Professional, 27 October 2006. ISBN 0-321-48091-0 Julie D. Allen. The Unicode
Unicode
Standard, Version 6.0, The Unicode Consortium, Mountain View, 2011, ISBN 9781936213016, ([1]). The Complete Manual of Typography, James Felici, Adobe Press; 1st edition, 2002. ISBN 0-321-12730-7 Unicode: A Primer, Tony Graham, M&T books, 2000. ISBN 0-7645-4625-2. Unicode
Unicode
Demystified: A Practical Programmer's Guide to the Encoding Standard, Richard Gillam, Addison-Wesley Professional; 1st edition, 2002. ISBN 0-201-70052-2 Unicode
Unicode
Explained, Jukka K. Korpela, O'Reilly; 1st edition, 2006. ISBN 0-596-10121-X

External links[edit]

Find more aboutUnicodeat's sister projects

Definitions from Wiktionary Media from Wikimedia Commons Textbooks from Wikibooks Discussion from Meta-Wiki

Official website — The Unicode
Unicode
Consortium Unicode
Unicode
at Curlie (based on DMOZ) Alan Wood's Unicode
Unicode
Resources – Contains lists of word processors with Unicode
Unicode
capability; fonts and characters are grouped by type; characters are presented in lists, not grids.

v t e

Unicode

Unicode

Unicode
Unicode
Consortium ISO/IEC 10646 (Universal Character Set) Versions

Code points

Blocks Universal Character Set Character charts Character property Planes Private Use Areas

Characters

Special
Special
purpose

BOM Combining Grapheme
Grapheme
Joiner Left-to-right mark / Right-to-left mark Soft hyphen Word joiner Zero-width joiner Zero-width non-joiner Zero-width space

Lists

Characters CJK Unified Ideographs Combining character Duplicate characters Numerals Scripts Spaces Symbols Halfwidth and fullwidth

Processing

Algorithms

Bi-directional text Collation

ISO 14651

Equivalence Variation sequences International Ideographs Core

Comparison

BOCU-1 CESU-8 Punycode SCSU UTF-1 UTF-7 UTF-8 UTF-9/UTF-18 UTF-16/UCS-2 UTF-32/UCS-4 UTF-EBCDIC

On pairs of code points

Combining character Compatibility characters Duplicate characters Equivalence Homoglyph Precomposed character

list

Z-variant Variation sequences Regional Indicator Symbol Fitzpatrick modifiers

Usage

Domain names (IDN) Email Fonts HTML

entity references numeric references

Input International Ideographs Core

Related standards

Common Locale Data Repository (CLDR) GB 18030 ISO/IEC 8859 ISO 15924

Related topics

Anomalies ConScript Unicode
Unicode
Registry Ideographic Rapporteur Group International Components for Unicode People involved with Unicode Han unification

Scripts and symbols in Unicode

Common and inherited scripts

Combining marks Diacritics Punctuation Space Numbers

Modern scripts

Adlam Arabic

diacritics

Armenian Balinese Bamum Batak Bengali Bopomofo Braille Buhid Burmese Canadian Aboriginal Chakma Cham Cherokee CJK Unified Ideographs (Han) Cyrillic Deseret Devanagari Ge'ez Georgian Greek Gujarati Gurmukhī Hangul Hanja Hanunó'o Hebrew

diacritics

Hiragana Javanese Kanji Kannada Katakana Kayah Li Khmer Lao Latin Lepcha Limbu Lisu (Fraser) Lontara Malayalam Masaram Gondi Mende Kikakui Miao (Pollard) Mongolian Mro N'Ko New Tai Lue Newa Nushu Ol Chiki Oriya Osage Osmanya Pahawh Hmong Pau Cin Hau Rejang Samaritan Saurashtra Shavian Sinhala Sorang Sompeng Sundanese Sylheti Nagari Syriac Tagbanwa Tai Le Tai Tham Tai Viet Tamil Telugu Thaana Thai Tibetan Tifinagh Tirhuta Vai Warang Citi Yi

Ancient and historic scripts

Ahom Anatolian hieroglyphs Ancient North Arabian Avestan Bassa Vah Bhaiksuki Brāhmī Carian Caucasian Albanian Coptic Cuneiform Cypriot Egyptian hieroglyphs Elbasan Glagolitic Gothic Grantha Hatran Imperial Aramaic Inscriptional Pahlavi Inscriptional Parthian Kaithi Kharosthi Khojki Khudawadi Linear A Linear B Lycian Lydian Mahajani Mandaic Manichaean Marchen Meetei Mayek Meroitic Modi Multani Nabataean Ogham Old Hungarian Old Italic Old Permic Old Persian cuneiform Old Turkic Palmyrene 'Phags-pa Phoenician Psalter Pahlavi Runic Śāradā Siddham South Arabian Soyombo Tagalog (Baybayin) Takri Tangut Ugaritic Zanabazar Square

Notational scripts

Duployan SignWriting

Symbols

Cultural, political, and religious symbols Currency Mathematical operators and symbols Phonetic symbols (including IPA) Emoji

v t e

Character encodings

Early telecommunications

ASCII ISO/IEC 646 ISO/IEC 6937 T.61 BCDIC Baudot code Morse code

Telegraph code Wabun code

Special
Special
telegraphy codes

Non-Latin Chinese Cyrillic

Needle telegraph codes

ISO/IEC 8859

-1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16

Bibliographic use

ANSEL ISO 5426 / 5426-2 / 5427 / 5428 / 6438 / 6861 / 6862 / 10585 / 10586 / 10754 / 11822 MARC-8

National standards

ArmSCII BraSCII CNS 11643 ELOT 927 GOST 10859 GB 18030 HKSCS ISCII JIS X 0201 JIS X 0208 JIS X 0212 JIS X 0213 KOI-7 KPS 9566 KS X 1001 PASCII SI 960 TIS-620 TSCII VISCII YUSCII

EUC

CN JP KR TW

ISO/IEC 2022

CN JP KR CCCII

MacOS
MacOS
code pages ("scripts")

Arabic Celtic CentEuro ChineseSimp / EUC-CN ChineseTrad / Big5 Croatian Cyrillic Devanagari Dingbats Esperanto Farsi (Persian) Gaelic Greek Gujarati Gurmukhi Hebrew Iceland Japanese / ShiftJIS Korean / EUC-KR Latin-1 Roman Romanian Sámi Symbol Thai / TIS-620 Turkish Ukrainian

DOS code pages

100 111 112 113 151 152 161 162 163 164 165 166 210 220 301 437 449 489 620 667 668 707 708 709 710 711 714 715 720 721 737 768 770 771 772 773 774 775 776 777 778 790 850 851 852 853 854 855/872 856 857 858 859 860 861 862 863 864/17248 865 866/808 867 868 869 874/1161/1162 876 877 878 881 882 883 884 885 891 895 896 897 898 899 900 903 904 906 907 909 910 911 926 927 928 929 932 934 936 938 941 942 943 944 946 947 948 949 950/1370 951 966 991 1034 1039 1040 1041 1042 1043 1044 1046 1086 1088 1092 1093 1098 1108 1109 1114 1115 1116 1117 1118 1119 1125/848 1126 1127 1131/849 1139 1167 1168 1300 1351 1361 1362 1363 1372 1373 1374 1375 1380 1381 1385 1386 1391 1392 1393 1394 Kamenický Mazovia CWI-2 KOI8 MIK Iran System

IBM AIX
IBM AIX
code pages

367 371 806 813 819 895 896 912 913 914 915 916 919 920 921/901 922/902 923 952 953 954 955 956 957 958 959 960 961 963 964 965 970 971 1004 1006 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1029 1036 1089 1111 1124 1129/1163 1133 1350 1382 1383

IBM Apple MacIntosh emulations

1275 1280 1281 1282 1283 1284 1285 1286

IBM Adobe emulations

1038 1276 1277

IBM DEC emulations

1020 1021 1023 1090 1100 1101 1102 1103 1104 1105 1106 1107 1287 1288

IBM HP emulations

1050 1051 1052 1053 1054 1055 1056 1057 1058

Windows code pages

CER-GS 874/1162 (TIS-620) 932/943 (Shift JIS) 936/1386 (GBK) 950/1370 (Big5) 949/1363 (EUC-KR) 1169 1174 Extended Latin-8 1200 (UTF-16LE) 1201 (UTF-16BE) 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1261 1270 54936 (GB18030)

EBCDIC
EBCDIC
code pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37/1140 38 39 40 251 252 254 256 257 258 259 260 264 273/1141 274 275 276 277/1142 278/1143 279 280/1144 281 282 283 284/1145 285/1146 286 287 288 289 290 293 297/1147 298 300 310 320 321 322 330 351 352 353 355 357 358 359 360 361 363 382 383 384 385 386 387 388 389 390 391 392 393 394 395 410 420/16804 421 423 424/8616/12712 425 435 500/1148 803 829 833 834 835 836 837 838/838 839 870/1110/1153 871/1149 875/4971/9067 880 881 882 883 884 885 886 887 888 889 890 892 893 905 918 924 930/1390 931 933/1364 935/1388 937/1371 939/1399 1001 1002 1003 1005 1007 1024 1025/1154 1026/1155 1027 1028 1030 1031 1032 1033 1037 1047 1068 1069 1070 1071 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1087 1091 1097 1112/1156 1113 1122/1157 1123/1158 1130/1164 1132 1136 1137 1150 1151 1152 1159 1165 1166 1278 1279 1303 1364 1376 1377 JEF KEIS

Platform specific

Acorn Adobe Standard Adobe Latin 1 Apple II ATASCII Atari ST BICS Casio calculators CDC CPC DEC Radix-50 DEC MCS/NRCS DG International ELWRO-Junior FIELDATA GEM GEOS GSM 03.38 HP Roman Extension HP Roman-8 HP Roman-9 HP FOCAL HP RPL LICS LMBCS Mattel Aquarius MSX NEC APC NeXT PCW PETSCII Sharp calculators TI calculators TRS-80 Ventura International Ventura Symbol WISCII XCCS ZX80 ZX81 ZX Spectrum

Unicode / ISO/IEC 10646

UTF-1 UTF-7 UTF-8 UTF-16
UTF-16
(UTF-16LE/UTF-16BE) / UCS-2 UTF-32 (UTF-32LE/UTF-32BE) / UCS-4 UTF-EBCDIC GB 18030 BOCU-1 CESU-8 SCSU

Miscellaneous code pages

ABICOMP APL ARIB STD-B24 Cork HZ INIS INIS-8 ISO-IR-111 ISO-IR-182 ISO-IR-200 ISO-IR-201 ISO-IR-209 Johab LGR LY1 OML OMS OMX OT1 OT2 OT3 OT4 T2A T2B T2C T2D T3 T4 T5 TS1 TS3 U X2 SEASCII TACE16 TRON UTF-5 UTF-6 WTF-8

Related topics

Code page Control character (C0 C1) CCSID Character encodings in HTML Charset detection Han unification Hardware ISO 6429/IEC 6429/ANSI X3.64 Mojibake

Character sets

Authority control

.