Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

RFC 5137, "ASCII Escaping of Unicode Characters", February 2008

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app
See Also: RFC 5137 w/ inline errata

---

Errata ID: 7234
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-02
Verifier Name: RFC Editor
Date Verified: 2022-11-03

Section 2 says:

      or more decoding steps to determine a Unicode code point that can
      used to look up the character in a table.  That may be appropriate
      in some cases where the goal is really to represent the UTF-8 form
      but, in general, it just obscures desired information and makes
      errors more likely and debugging harder.

It should say:

      or more decoding steps to determine a Unicode code point that can
      be used to look up the character in a table.  That may be
      appropriate in some cases where the goal is really to represent
      the UTF-8 form but, in general, it just obscures desired
      information and makes errors more likely and debugging harder.

Notes:

Missing "be".

Report New Errata