RFC Errata
Found 3 records.
Status: Verified (1)
RFC 3454, "Preparation of Internationalized Strings ("stringprep")", December 2002
Note: This RFC has been obsoleted by RFC 7564
Source of RFC: IETF - NON WORKING GROUPArea Assignment: int
Errata ID: 806
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Sergiusz Wolicki
Date Reported: 2006-04-27
Section Appendix C says:
C. Prohibition tables The tables in this appendix consist of lines with one prohibited code point per line. The format of the lines are the value of the code point, a semicolon, and a comment which is the name of the code point.
It should say:
[see Notes]
Notes:
This is not true as the tables in this appendix consist of lines with
one prohibited code point _range_ per line. The format of the lines
are the value of the starting code point of the range, a hyphen,
the value of the ending code point of the range, a semicolon,
and a comment which is the informal name of the range in square brackets.
If the range contains only one code point, then the hyphen and the ending
code point value are omitted, and the comment contains the name of
the code point without brackets.
from pending
Status: Held for Document Update (2)
RFC 3454, "Preparation of Internationalized Strings ("stringprep")", December 2002
Note: This RFC has been obsoleted by RFC 7564
Source of RFC: IETF - NON WORKING GROUPArea Assignment: int
Errata ID: 4577
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Loïc Jonas Etienne
Date Reported: 2016-01-04
Held for Document Update by: Brian Haberman
Date Held: 2016-04-05
Section 3.1 says:
Some characters are only useful in line-based text, and are otherwise invisible and ignored. 00AD; SOFT HYPHEN 1806; MONGOLIAN TODO SOFT HYPHEN 200B; ZERO WIDTH SPACE 2060; WORD JOINER FEFF; ZERO WIDTH NO-BREAK SPACE
It should say:
Some characters are only useful in line-based text, and are otherwise invisible and ignored. 00AD; SOFT HYPHEN 200B; ZERO WIDTH SPACE 2060; WORD JOINER FEFF; ZERO WIDTH NO-BREAK SPACE
Notes:
This issue has been reported to the unicode consortium (http://www.unicode.org/L2/L2015/15277-pubrev.html), according to which: U+1806 is not a control character; RFC 3454 is mistaken in mapping it to nothing, since the character always has a distinct visual appearance; For more information about the character, see page 528 of Core Specification, Version 8.0.
Errata ID: 2686
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jehan Pagès
Date Reported: 2011-01-20
Held for Document Update by: Alexey Melnikov
Section 3.2 says:
The list of characters to add to the mapping table can determined by the following algorithm:
It should say:
The list of characters to add to the mapping table can be determined by the following algorithm:
Notes:
A small omission of a single word: "be" is missing.