Unicode equivalence

Short description: Aspect of the Unicode standard

Unicode equivalence is the specification by the Unicode character encoding standard that some sequences of code points represent essentially the same character. The feature was introduced in the standard to allow compatibility with pre-existing standard character set, which often included similar or identical characters.

Unicode provides two such notions, canonical equivalence and compatibility. Code point sequences that are defined as canonically equivalent are assumed to have the same appearance and meaning when printed or displayed. For example, the code point U+006E n LATIN SMALL LETTER N followed by U+0303 ◌̃ COMBINING TILDE is defined by Unicode to be canonically equivalent to the single code point U+00F1 ñ LATIN SMALL LETTER N WITH TILDE. Therefore, those sequences should be displayed in the same manner, should be treated in the same way by applications such as alphabetizing names or searching, and may be substituted for each other. Similarly, each Hangul syllable block that is encoded as a single character may be equivalently encoded as a combination of a leading conjoining jamo; a vowel conjoining jamo; and, if appropriate, a trailing conjoining jamo.

Sequences that are defined as compatible are assumed to have possibly distinct appearances but the same meaning in some contexts. Thus, for example, the code point U+FB00 (the typographic ligature "ﬀ") is defined to be compatible but not canonically equivalent to the sequence U+0066 U+0066 (two Latin "f" letters). Compatible sequences may be treated the same way in some applications (such as sorting and indexing) but not in others, and they may be substituted for each other in some situations, but not in others. Sequences that are canonically equivalent are also compatible, but the opposite is not necessarily true.

The standard also defines a text normalization procedure, called Unicode normalization, which replaces equivalent sequences of characters so that any two texts that are equivalent will be reduced to the same sequence of code points, called the normalization form or normal form of the original text. For both of the equivalence notions, Unicode defines two normal forms, one fully composed (where multiple code points are replaced by single points whenever possible) and one fully decomposed (where single points are split into multiple ones).

## Contents

* 1 Sources of equivalence
* 1.1 Character duplication
* 1.2 Combining and precomposed characters
* 1.2.1 Example
* 1.3 Typographical non-interaction
* 1.4 Typographic conventions
* 2 Encoding errors
* 3 Normalization
* 3.1 Algorithms
* 3.2 Normal forms
* 3.3 Canonical ordering
* 4 Errors from normalization differences
* 5 See also
* 6 Notes
* 7 References
* 8 External links

## Sources of equivalence

### Character duplication

Main article: Duplicate characters in Unicode

For compatibility or other reasons, Unicode sometimes assigns two different code points to entities that are essentially the same character. For example, the letter "A with a ring diacritic above" is encoded as U+00C5 Å (a letter of the alphabet in Swedish and several other languages) or as U+212B Å . However, the symbol for angstrom is defined to be that Swedish letter, and most other symbols that are letters (such as ⟨V⟩ for volt) do not have a separate code point for each usage. In general, the code points of truly identical characters are defined to be canonically equivalent.

### Combining and precomposed characters

For consistency with some older standards, Unicode provides single code points for many characters that could be viewed as modified forms of other characters (such as U+00F1 for "ñ" or U+00C5 for "Å") or as combinations of two or more characters (such as U+FB00 for the ligature "ﬀ" or U+0132 for the Dutch letter "ĳ")

For consistency with other standards and greater flexibility, Unicode also provides codes for many elements that are not used on their own but are meant instead to modify or combine with a preceding base character. Examples of those combining characters are U+0303 ◌̃ [[|]] and the Japanese diacritic dakuten (U+3099 ◌゙ ).

In the context of Unicode, character composition is the process of replacing the code points of a base letter followed by one or more combining characters into a single precomposed character; and character decomposition is the opposite process.

In general, precomposed characters are defined to be canonically equivalent to the sequence of their base letter and subsequent combining diacritic marks, whatever order they may occur.

#### Example

Amélie with its two canonically equivalent Unicode forms (NFC and NFD)  NFC character  | A | m | é | l | i | e

|
|
|
|
|
|

NFC code point  | 0041 | 006d | 00e9 | 006c | 0069 | 0065
NFD code point  | 0041 | 006d | 0065 | 0301 | 006c | 0069 | 0065
NFD character  | A | m | e | ◌́ | l | i | e

### Typographical non-interaction

Some scripts regularly use multiple combining marks that do not, in general, interact typographically, and do not have precomposed characters for the combinations. Pairs of such non-interacting marks can be stored in either order. Gernerally, the alternative sequences are canonically equivalent. The rules that define their sequencing in the canonical form also define whether they are considered to interact.

### Typographic conventions

Unicode provides code points for some characters or groups of characters that are modified only for aesthetic reasons (such as ligatures, the half-width katakana characters, or the full-width Latin letters for use in Japanese texts) or to add new semantics without losing the original one (such as digits in subscript or superscript positions, or the circled digits (such as "①") inherited from some Japanese fonts). Such a sequence is considered compatible with the sequence of original (individual and unmodified) characters for the benefit of applications where the appearance and added semantics are not relevant. However, the two sequences are not declared canonically equivalent since the distinction has some semantic value and affects the rendering of the text.

## Encoding errors

UTF-8 and UTF-16 (and also some other Unicode encodings) do not allow all possible sequences of code units. Different software will convert invalid sequences into Unicode characters using varying rules, some of which are very lossy (such as by turning all invalid sequences into the same character). That can be considered a form of normalization and can lead to the same difficulties as others.

## Normalization

A text processing software implementing the Unicode string search and comparison functionality must take into account the presence of equivalent code points. In the absence of that feature, users searching for a particular code point sequence would be unable to find other visually indistinguishable glyphs that have a different but canonically equivalent code point representation.

### Algorithms

Unicode provides standard normalization algorithms that produce a unique (normal) code point sequence for all sequences that are equivalent; the equivalence criteria can be either canonical (NF) or compatibility (NFK). Since one can arbitrarily choose the representative element of an equivalence class, multiple canonical forms are possible for each equivalence criterion. Unicode provides two normal forms that are semantically meaningful for each of the two compatibility criteria: the composed forms NFC and NFKC and the decomposed forms NFD and NFKD. Both the composed and decomposed forms impose a canonical ordering on the code point sequence, which is necessary for the normal forms to be unique.

To compare or search Unicode strings, software can use either composed or decomposed forms; the choice does not matter as long as it is the same for all strings involved in a search, comparison, etc. On the other hand, the choice of equivalence criteria can affect search results. For instance, some typographic ligatures like U+FB03 (ﬃ), Roman numerals like U+2168 (Ⅸ) and even subscripts and superscripts, e.g. U+2075 (⁵) have their own Unicode code points. Canonical normalization (NF) does not affect any of those, but compatibility normalization (NFK) decomposes the ffi ligature into the constituent letters and so a search for U+0066 (f) as substring would succeed in an NFKC normalization of U+FB03 but not in NFC normalization of U+FB03. The same is true when searching for the Latin letter I (U+0049) in the precomposed Roman numeral Ⅸ (U+2168). Similarly, the superscript ⁵ (U+2075) is transformed to 5 (U+0035) by compatibility mapping.

Transforming superscripts into baseline equivalents may not be appropriate, however, for rich text software because the superscript information is lost in the process. To allow for this distinction, the Unicode character database contains compatibility formatting tags that provide additional details on the compatibility transformation.[1] In the case of typographic ligatures, this tag is simply `<compat>`, while for the superscript it is `<super>`. Rich text standards like HTML take into account the compatibility tags. For instance, HTML uses its own markup to position a U+0035 in a superscript position.[2]

### Normal forms

The four Unicode normalization forms and the algorithms (transformations) for obtaining them are listed in the table below.

NFD
Normalization Form Canonical Decomposition | Characters are decomposed by canonical equivalence, and multiple combining characters are arranged in a specific order.

|

NFC
Normalization Form Canonical Composition | Characters are decomposed and then recomposed by canonical equivalence.
NFKD
Normalization Form Compatibility Decomposition | Characters are decomposed by compatibility, and multiple combining characters are arranged in a specific order.
NFKC
Normalization Form Compatibility Composition | Characters are decomposed by compatibility, then recomposed by canonical equivalence.

All of those algorithms are idempotent transformations, meaning that a string that is already in one of those normalized forms will not be modified if processed again by the same algorithm.

The normal forms are not closed under string concatenation.[3] For defective Unicode strings starting with a Hangul vowel or trailing conjoining jamo, concatenation can break composition.

However, they are not injective (they map different original glyphs and sequences to the same normalized sequence) and thus also not bijective (cannot be restored). For example, the distinct Unicode strings "U+212B" (the angstrom sign "Å") and "U+00C5" (the Swedish letter "Å") are both expanded by NFD (or NFKD) into the sequence "U+0041 U+030A" (Latin letter "A" and combining ring above "°"), which is then reduced by NFC (or NFKC) to "U+00C5" (the Swedish letter "Å").

A single character (other than a Hangul syllable block) that gets replaced by another under normalization can be identified in the Unicode tables for having a non-empty compatibility field but lacking a compatibility tag.

### Canonical ordering

The canonical ordering is concerned mainly with the ordering of a sequence of combining characters. For the examples in this section, the characters are assumed to be diacritics, but in general, some diacritics are not combining characters, and some combining characters are not diacritics.

Unicode assigns each character a combining class, which is identified by a numerical value. Non-combining characters have class number 0, and combining characters have a positive combining class value. To obtain the canonical ordering, every substring of characters having non-zero combining class value must be sorted by the combining class value using a stable sorting algorithm. Stable sorting is required because combining characters with the same class value are assumed to interact typographically and so the two possible orders are not considered equivalent.

For example, the character U+1EBF (ế), used in the Vietnamese alphabet, has both an acute and a circumflex accent. Its canonical decomposition is the three-character sequence U+0065 (e) U+0302 (circumflex accent) U+0301 (acute accent). The combining classes for the two accents are both 230 and so U+1EBF is not equivalent to U+0065 U+0301 U+0302.

Since not all combining sequences have a precomposed equivalent (the last one in the previous example can only be reduced to U+00E9 U+0302), even the normal form NFC is affected by combining characters' behavior.

## Errors from normalization differences

When two applications share Unicode data but normalize them differently, errors and data loss may result. In one specific instance, OS X normalized Unicode filenames sent from the Netatalk and Samba file- and printer-sharing software. Netatalk and Samba did not recognize the altered filenames as equivalent to the original, which led to data loss.[4][5] Resolving such an issue is non-trivial, as normalization is not losslessly invertible.

## See also

* Complex text layout
* Diacritic
* IDN homograph attack - Visually similar letters in domain names
* ISO/IEC 14651
* Ligature (typography)
* Precomposed character - Compound character with single codepoint
* Representative glyph
* uconv, can convert to and from NFC and NFD Unicode normalization forms.
* Unicode
* Unicode compatibility characters - Characters encoded solely to maintain round-trip convertibility with other standards

## Notes

1. ↑ "UAX #44: Unicode Character Database". Unicode.org. https://www.unicode.org/reports/tr44/#Character_Decomposition_Mappings.
2. ↑ "Unicode in XML and other Markup Languages". Unicode.org. http://unicode.org/reports/tr20/tr20-2.html#Compatibility.
3. ↑ Per What should be done about concatenation
4. ↑ "netatalk / Bugs / #349 volcharset:UTF8 doesn't work from Mac". https://sourceforge.net/tracker/?func=detail&aid=2727174&group_id=8642&atid=108642.
5. ↑ "rsync, samba, UTF8, international characters, oh my!". 2009. http://forums.macosxhints.com/archive/index.php/t-99344.html.

## References

* Unicode Standard Annex #15: Unicode Normalization Forms

## External links

* Unicode.org FAQ - Normalization
* Charlint - a character normalization tool written in Perl

* v
* t
* e

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 purpose|

* BOM
* Combining 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
* Alias names and abbreviations

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 Registry
* Ideographic Research 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
* Gunjala Gondi
* Gurmukhi
* Hangul
* Hanifi Rohingya
* Hanja
* Hanunuo
* Hebrew
* diacritics
* Hiragana
* Javanese
* Kanji
* Kannada
* Katakana
* Kayah Li
* Khmer
* Lao
* Latin
* Lepcha
* Limbu
* Lisu (Fraser)
* Lontara
* Malayalam
* Masaram Gondi
* Mende Kikakui
* Medefaidrin
* Miao (Pollard)
* Mongolian
* Mru
* N'Ko
* New Tai Lue
* Nüshu
* Nyiakeng Puachue Hmong
* Odia
* Ol Chiki
* Osage
* Osmanya
* Pahawh Hmong
* Pau Cin Hau
* Pracalit (Newa)
* Ranjana
* 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
* Wancho
* 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
* Dogra
* Egyptian hieroglyphs
* Elbasan
* Elymaic
* Glagolitic
* Gothic
* Grantha
* Hatran
* Imperial Aramaic
* Inscriptional Pahlavi
* Inscriptional Parthian
* Kaithi
* Kharosthi
* Khojki
* Khudawadi
* Linear A
* Linear B
* Lycian
* Lydian
* Mahajani
* Makasar
* Mandaic
* Manichaean
* Marchen
* Meetei Mayek
* Meroitic
* Modi
* Multani
* Nabataean
* Nandinagari
* Ogham
* Old Hungarian
* Old Italic
* Old Permic
* Old Persian cuneiform
* Old Sogdian
* Old Turkic
* Palmyrene
* 'Phags-pa
* Phoenician
* Psalter Pahlavi
* Runic
* Sharada
* Siddham
* Sogdian
* 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

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Unicode equivalence. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Unicode_equivalence&oldid=4347657"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template