The Unicode sources and references we cite
The source register connects each kind of Unicode claim to the standards body or first-party document able to support it.
What this page covers
Unicode defines identity
The Standard and Character Database establish code points, names, and properties.
Protocols define encoding
IETF and web standards explain how character data moves through software.
Evidence follows scope
A font vendor supports claims about its glyphs; a standard supports normative rules.
Unicode repertoire and property data
The latest Unicode Standard defines the coded character repertoire and conformance model. Unicode Standard Annex #44 documents the Unicode Character Database, including the property model used to interpret formal names and categories.
Normalization, emoji, and security
UAX #15 is the normative reference for NFC, NFD, NFKC, and NFKD; the normalization field guide translates those forms into practical choices. UTS #51 covers emoji properties and sequences. UTS #39 provides mechanisms and data for Unicode security work, expanded in the guide to confusable characters and identifiers.
Encoding and browser implementation
RFC 3629 specifies UTF-8. The code-point and encoding chapter explains the relationship in working terms. W3C internationalization guidance explains web encoding practices, while ECMAScript defines the browser string normalization method used by the interactive checker. A browser result is useful diagnostic evidence but does not replace the relevant normative specification.
How citations are selected
A source is linked where it supports the level of claim being made. Unicode documentation establishes encoded identity; a font or operating-system vendor is the appropriate authority for its own glyph behavior; a cultural interpretation requires subject-specific evidence. Aggregator pages are not used to manufacture authority when the primary material is available.
Version and correction policy
The application runtime may support a particular Unicode data version rather than every character in the newest published release. Coverage claims therefore stay bounded to the rendered catalog. Readers new to that boundary can begin with the practical introduction to Unicode. Broken references or version discrepancies can be reported through contact, and the verification workflow is described in methodology.