Unicode compatibility characters
character encoded solely to maintain retrocompatibility and round trip convertibility with other referenced standards
In Unicode and the Universal Character Set (UCS), a compatibility character is a character that is encoded solely to maintain round-trip convertibility with other, often older standards. According to the Unicode Glossary:
A character that would not have been encoded except for compatibility and round-trip convertibility with other standards.
Although the term compatibility appears in character names, it is not itself represented as a distinct character property. In practice, the definition is more complex. One of the properties assigned to characters by the Unicode Consortium is decomposition, including compatibility decomposition. More than five thousand characters have a compatibility decomposition mapping that relates the compatibility character to one or more other UCS characters. By assigning a compatibility decomposition to a character, Unicode effectively designates it as a compatibility character.
The reasons for assigning compatibility status vary and are discussed in more detail below. The term decomposition can be confusing, because in some cases a character’s decomposition consists of a single character. In such cases, the decomposition maps one character to another that is approximately—but not canonically—equivalent.
The public source identifies “Unicode compatibility characters” as character encoded solely to maintain retrocompatibility and round trip convertibility with other referenced standards. This brief keeps that definition visible, then builds a research path around Unicode, compatibility and characters.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Unicode compatibility characters”, the useful work is to connect “character encoded solely to maintain retrocompatibility and round trip convertibility with other referenced standards” to the records capable of establishing context and consequence.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Sep 10, 2026. The linked authority identifier is Q6137535. None of the 0 selected statements returned an explicit reference.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Unicode compatibility characters”, its source revision and the description used here.
- Expand the search: follow Unicode compatibility characters primary sources, Unicode compatibility characters archive and Unicode research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Unicode compatibility characters”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Unicode compatibility characters” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.