Found 2 records.

Status: Held for Document Update (1)

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

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

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