RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Verified (5)

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

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 5138
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Smith
Date Reported: 2017-10-04
Verifier Name: Alexey Melnikov
Date Verified: 2017-10-04

Section A.3 says: 

   EmbeddedUnicodeChar =   %x5C.7A 4HEXDIG ; starts with "\u"

It should say:

   EmbeddedUnicodeChar =   %x5C.75 4HEXDIG ; starts with "\u"

Notes:

Hex 7A is the character 'z', which doesn't match the comment.
As far as I can tell, the Java language defines unicode characters to be \u, like the comment says, and therefore the ABNF should be %x5C.75

Errata ID: 4888
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Matthew Kerwin
Date Reported: 2016-12-14
Verifier Name: Orie Steele
Date Verified: 2024-04-01

Section 1.1 says: 

So, even for the fairly simple cases of ASCII and standard built by
extending ASCII, such as the ISO 8859 family, we have been living

It should say:

So, even for the fairly simple cases of ASCII and standards built by
extending ASCII, such as the ISO 8859 family, we have been living

Notes:

Should be plural "standards"

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".

Errata ID: 7235
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-02
Verifier Name: Orie Steele
Date Verified: 2024-04-01

Section 2 says: 

   form used in Java (See Section 6.3).  While those forms are

It should say:

   form used in Java (see Section 6.3).  While those forms are

Notes:

The word "see" should not be capitalized here.

Errata ID: 7236
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ivan Panchenko
Date Reported: 2022-11-02
Verifier Name: Orie Steele
Date Verified: 2024-04-01

Section 5.1 says: 

   start in "\u" (See, e.g., Section 6.1, below>), but uses explicit

It should say:

   start in "\u" (see, e.g., Section 6.1, below), but uses explicit

Notes:

The character ">" should not be here and the word "see" should not be capitalized here.

Report New Errata



Advanced Search