ASCII Escaping of Unicode Characters

Metadata

Publisher: IETF
Doc Type: Best Practice
Pages: 13
Abstract: There are a number of circumstances in which an escape mechanism is needed in conjunction with a protocol to encode characters that cannot be represented or transmitted directly. With ASCII coding, the traditional escape has been either the decimal or hexadecimal numeric value of the character, written in a variety of different ways. The move to Unicode, where characters occupy two or more octets and may be coded in several different forms, has further complicated the question of escapes. This document discusses some options now in use and discusses considerations for selecting one for use in new IETF protocols, and protocols that are now being internationalized. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Publication Date: 2008-02-01
Status Note: Best Current Practice
DOI: 10.17487/RFC5137
Link: https://doi.org/10.17487/RFC5137
Author(s): Dr. John C. Klensin
Keyword(s): Internationalization, ASCII, Unicode, UTF-8, Encoding

Latest version of IETF RFC 5137

Document Versions — IETF RFC 5137

▶ IETF RFC 5137 (2008-02-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

ISO 10646:2003 [Withdrawn]
IETF RFC 2119 [Active*]
IETF RFC 3629 [Active*]
IETF RFC 5234 [Active, Amended*]
UNICODE.STD.5.0 — Unicode EXTERNAL

Bibliographic Reference(s)

INCITS.X3.4.1968 — 1 EXTERNAL
ISO 9899: 1999 [Withdrawn]
Sun Microsystems, Inc., "Java Language Specification, Third Edition", 2005, < http:// java.sun.com/docs/books/jls/third_edition/html/ lexical.html#95413p >. EXTERNAL
The Unicode Consortium, "Glossary of Unicode Terms", June 2007, < http://www.unicode.org/glossary >. EXTERNAL
Hietaniemi, J., "perluniintro", Perl documentation 5.8.8, 2002, < http://perldoc.perl.org/perluniintro.html >. EXTERNAL
IETF RFC 2277 [Active*]
IETF RFC 3492 [Active*]
W3C.charmod — CharModel EXTERNAL

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5137.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5137, ASCII Escaping of Unicode Characters. Available at https://doi.org/10.17487/RFC5137

Snippet:

IETF RFC 5137, ASCII Escaping of Unicode Characters. Available at https://doi.org/10.17487/RFC5137

HTML (ISO 690 compliant)

Preview:

IETF RFC 5137, ASCII Escaping of Unicode Characters. Available at https://doi.org/10.17487/RFC5137

Snippet:

<span class="citation"><cite>IETF RFC 5137</cite>, ASCII Escaping of Unicode Characters. Available at <a href="https://doi.org/10.17487/RFC5137" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5137</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5137, ASCII Escaping of Unicode Characters
doi: 10.17487/RFC5137
url: https://doi.org/10.17487/RFC5137

Snippet:

<li>
<cite id="bib-rfc5137">IETF RFC 5137</cite>, ASCII Escaping of Unicode Characters
<span class="doi">10.17487/RFC5137</span>
</li>

Referenced By

IETF RFC 5284 [Active*]
IETF RFC 6365 [Active*]
IETF RFC 7997 [Active*]