RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Reported (1)

RFC 2640, "Internationalization of the File Transfer Protocol", July 1999

Source of RFC: ftpext (app)

Errata ID: 8007
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Tim Geiser
Date Reported: 2024-06-27

Section B.2.1 & B.2.3 says: 

The first step in the process can be performed by maintaining a
mapping table that includes the local character set code and the
corresponding UCS code. For instance the ISO/IEC 8859-8 [ISO-8859]
code for the Hebrew letter "VAV" is 0xE4. The corresponding 4 byte
ISO/IEC 10646 code is 0x000005D5.

=====================================================================

This example demonstrates mapping ISO/IEC 8859-8 character set to
UTF-8 and back to ISO/IEC 8859-8. As noted earlier, the Hebrew letter
"VAV" is convertd from the ISO/IEC 8859-8 character code 0xE4 to the
corresponding 4 byte ISO/IEC 10646 code of 0x000005D5 by a simple
lookup of a conversion/mapping file.

=====================================================================

Finally, the UCS-4 character code is converted to ISO/IEC 8859-8
character code (using the mapping table which matches ISO/IEC 8859-8
to UCS-4 ) to produce the original 0xE4 code for the Hebrew letter
"VAV".

It should say:

The first step in the process can be performed by maintaining a
mapping table that includes the local character set code and the
corresponding UCS code. For instance the ISO/IEC 8859-8 [ISO-8859]
code for the Hebrew letter "VAV" is 0xE5. The corresponding 4 byte
ISO/IEC 10646 code is 0x000005D5.

=====================================================================

This example demonstrates mapping ISO/IEC 8859-8 character set to
UTF-8 and back to ISO/IEC 8859-8. As noted earlier, the Hebrew letter
"VAV" is convertd from the ISO/IEC 8859-8 character code 0xE5 to the
corresponding 4 byte ISO/IEC 10646 code of 0x000005D5 by a simple
lookup of a conversion/mapping file.

=====================================================================

Finally, the UCS-4 character code is converted to ISO/IEC 8859-8
character code (using the mapping table which matches ISO/IEC 8859-8
to UCS-4 ) to produce the original 0xE5 code for the Hebrew letter
"VAV".

Notes:

The ISO-8859-8 encoding for the Hebrew letter "VAV" is 0xE5, not 0xE4.
The Unicode U+05D5 (0x000005D5) is the Hebrew letter "VAV" so everything else about these examples are correct. If you actually try converting 0xE4 you'll get Hebrew letter "HE" (U+05D4).

Status: Held for Document Update (1)

RFC 2640, "Internationalization of the File Transfer Protocol", July 1999

Source of RFC: ftpext (app)

Errata ID: 5444
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: David LAMBERT
Date Reported: 2018-07-28
Held for Document Update by: Barry Leiba
Date Held: 2019-04-30

Section 4.3.1 says: 

        C> LANG fr
        S> 200 Le response sera changez au francais

        C> feat
        S> 211- <quelconque descriptif texte>
        S>  ...
        S>  LANG EN;FR*
        S>  ...
        S> 211 end

It should say:

        C> LANG fr
        S> 200 Les réponses seront en français

        C> feat
        S> 211- <texte descriptif quelconque>
        S>  ...
        S>  LANG EN;FR*
        S>  ...
        S> 211 end

Notes:

I'm natively speaking French, and the original text is not correct.
In particular, some words stayed in English, and word order is not the same in French.

The correction make the hypothesis that UTF-8 is allowed in reply messages, which is not specified in the RFC (see other errata).

Status: Rejected (1)

RFC 2640, "Internationalization of the File Transfer Protocol", July 1999

Source of RFC: ftpext (app)

Errata ID: 5445
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: David LAMBERT
Date Reported: 2018-07-28
Rejected by: Barry Leiba
Date Rejected: 2019-04-30

Throughout the document, when it says:

Notes:

The RFC talks about UTF-8 for paths, but not about response messages.
The LANG command specified in the RFC can lead servers to send reply messages containing character outside of the ASCII character set.
It should specify that UTF-8 should also be used for reply messages.
--VERIFIER NOTES--

Section 4.1 says:

This specification RECOMMENDS that the server
default language be English encoded using ASCII. This text may be
augmented by text from other languages. Once negotiated, server-PI
MUST return server messages and textual part of command responses in
the negotiated language and encoded in UTF-8.

Report New Errata



Advanced Search