Appendix:Unicode normalization


 * See also Unicode normalization considerations on the MediaWiki website.

Wikimedia, along with most servers on the internet, stores Unicode strings in the form called NFC or Normalization Form (Canonical) Composition. This means that often several different Unicode strings are mapped to the same canonical form. When you enter a Unicode string and save the page, it is automatically converted to the normalized form. Non-normalized strings cannot be saved in a Wiktionary page.

Issues
Most of the time NFC makes processing text easier, but there are some oddities, both semantic and non-semantic that do appear. There are four cases where single characters are not the NFC form.
 * 1) Sometimes an alternative single character is the canonical composed form.
 * Example: U+212B ( &#x212B; - ANGSTROM SIGN) is converted to U+00C5 ( Å - LATIN CAPITAL LETTER A WITH RING ABOVE)
 * 1) For some scripts, precomposed characters are not preferred.
 * Example: U+0958 ( &#x0958; - DEVANAGARI LETTER QA) is converted to the decomposed क़ which is U+0915 ( & - DEVANAGARI LETTER KA) + U+093C ( & - DEVANAGARI SIGN NUKTA).
 * 1) Where a decomposition exists in pre-Unicode 3.0 for a precomposed character added afterwards, the decomposition is preferred.
 * Example: U+2ADC ( &#x2ADC; - FORKING) is converted to ⫝̸ which is U+2ADD ( & - NONFORKING) + U+0338 ( & - COMBINING LONG SOLIDUS OVERLAY).
 * 1) A decomposition is preferred to precomposed characters where the decomposition begins with a non-starter.
 * Example: U+0344 ( &#x0344; - COMBINING GREEK DIALYTIKA TONOS) is converted to U+0308 ( & - COMBINING DIAERESIS (DIALYTIKA)) + U+0301 ( & - COMBINING ACUTE ACCENT (OXIA, TONOS)).

In a number of common cases, Unicode's canonical ordering of two diacritics is counterintuitive, and/or interoperates poorly with certain existing software. In other, less common cases, the problem is that the diacritics should not have a canonical ordering, because the two orderings are not actually equivalent (that is, the two diacritics should have the same value for the Canonical_Combining_Class (ccc) property, but instead they have different ones). For example, Hebrew לַ ִ ("lai") is mistakenly normalized to לִַ ("lia").

As the conversion is automatic, there cannot exist pages for the non-NFC form. Attempting to explicitly link to the non-NFC form, &, will display the non-NFC form, but when clicked on will take the user to the NFC page &.

Display
One can display the non-NFC characters on a page using ( will show ). To note canonical equivalence between two single characters, use in the caption field of the appropriate  template on the NFC character (see Å for an example). To note that the NCF of a precomposed character is a decomposition, use in the caption field of the appropriate  template on the NFC decomposition (see क़ for an example).