RFC 3629: UTF-8, a transformation format of ISO 10646
In plain English — editorial summary, not part of the RFC
ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.
Document record
- Document ID
- RFC3629
- Published
- November 2003
- Authors
- F. Yergeau
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 14
- Also known as
- STD63
- Obsoletes:
- RFC 2279
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2044 (1996)
- RFC 2279 (1998)
- RFC 3629 (2003)
Read the full history of UTF-8, a transformation format of ISO 10646 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4042UTF-9 and UTF-18 Efficient Transformation Formats of UnicodeCurrent
April 2005
- RFC 2044UTF-8, a transformation format of Unicode and ISO 10646Obsoleted
October 1996
- RFC 7997The Use of Non-ASCII Characters in RFCsUpdated
December 2016
- RFC 3965A Simple Mode of Facsimile Using Internet MailCurrent
December 2004
- RFC 3987Internationalized Resource Identifiers (IRIs)Current
January 2005
- RFC 2913MIME Content Types in Media Feature ExpressionsCurrent
September 2000
- RFC 2912Indicating Media Features for MIME ContentCurrent
September 2000
- RFC 4396RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed TextCurrent
February 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?