thearchivist.funUTF-8 connects multilingual text with existing byte-based systems
RFC 3629 documented the modern range and structure of UTF-8 in November 2003.
Context and provenance
UTF-8 represents Unicode characters using sequences of bytes of different lengths. RFC 3629, published in November 2003, revised an earlier specification and described a form compatible with the Unicode range then in use. Basic ASCII characters keep their familiar single-byte representation, which helps existing tools handle ordinary text while allowing a much wider repertoire of writing. UTF-8 and Unicode are related but distinct: Unicode identifies characters, while UTF-8 specifies one way to encode those values for storage or transmission. This milestone therefore concerns a revised technical specification, not the original invention of UTF-8 or the beginning of multilingual computing.
Why it matters
Editorial perspective: Backward compatibility can help a system become more inclusive without requiring every existing tool to be discarded. The apparent simplicity of readable text is supported by careful decisions about how old and new representations coexist.