Unicode anomaly
The Unicode Standard has imposed for itself strict rules to guarantee stability.[1] This implies that when mistakes against these permanent rules are published, these mistakes cannot be corrected. Depending on the grade of 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.
Contents |
Anomalies
- U+0818 ࠘ samaritan mark dagesh and U+0819 ࠙ samaritan mark occlusion: Names mixed up.
- Corrected text, names swapped:
- U+0818 ࠘ samaritan mark occlusion (HTML:
࠘"strengthens" the consonant, for example changing /w/ to /b/) and - U+0819 ࠙ samaritan mark dagesh (HTML:
࠙indicates consonant gemination)[2]
- U+2118 ℘ script capital p (HTML:
℘℘): 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:
𝒫)[3]
- U+FE18 ︘ presentation form for vertical right white lenticular brakcet (HTML:
︘): BRAKCET is spelled wrong. Since this is the fixed Character Name by policy, it cannot be changed.[4]
- In 2006 Unicode has published a list of anomalies in character names.[5]
Stability policy
Version 1.0 versus Version 2.0 Names
In version 2.0, Unicode changed many code point "Names" from version 1. At the same moment, Unicode stated that from then on, an assigned Name to a code point will never change anymore.
References
- ^ Unicode stability policy
- ^ Errata 02 April 2010, Unicode version 6.0
- ^ Unicode chart: "actually this has the form of a lowercase calligraphic p, despite its name"
- ^ ]http://www.unicode.org/charts/PDF/UFE10.pdf "Misspelling of BRACKET in character name is a known defect"]
- ^ http://unicode.org/notes/tn27/
