RFC 1922: Chinese Character Encoding for Internet Messages
In plain English — editorial summary, not part of the RFC
This memo describes methods of transporting Chinese characters in Internet services which transport text, such as electronic mail [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World Wide Web [RFC-1866]. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1922
- Published
- March 1996
- Authors
- HF. Zhu; DY. Hu; ZG. Wang; TC. Kao; WCH. Chang; M. Crispin
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2447iCalendar Message-Based Interoperability Protocol (iMIP)Obsoleted
November 1998
- RFC 1991PGP Message Exchange FormatsObsoleted
August 1996
- RFC 1843HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII charactersCurrent
August 1995
- RFC 1842ASCII Printable Characters-Based Chinese Character Encoding for Internet MessagesCurrent
August 1995
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 1996
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
- RFC 2062Internet Message Access Protocol - Obsolete SyntaxCurrent
December 1996
- RFC 1725Post Office Protocol - Version 3Obsoleted
November 1994
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?