{
  "draft": "draft-klensin-unicode-escapes-07",
  "doc_id": "RFC5137",
  "title": "ASCII Escaping of Unicode Characters",
  "authors": [
    "J. Klensin"
  ],
  "format": [
    "TEXT",
    "HTML"
  ],
  "page_count": "13",
  "pub_status": "BEST CURRENT PRACTICE",
  "status": "BEST CURRENT PRACTICE",
  "source": "IETF - NON WORKING GROUP",
  "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.",
  "pub_date": "February 2008",
  "keywords": [
    "Text",
    "internationalization",
    "ascii",
    "unicode",
    "utf-8",
    "encoding"
  ],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC5137",
  "errata_url": "https://www.rfc-editor.org/errata/rfc5137"
}