1 - 2 - 4 - 6 - 7 - 8 - A - B - C - D - E - F - G - H - I - L - M - N - O - P - R - S - T - U - V - W
language
Click on the red underlined text to get to the source
... recommendations expressed by the IETF policy related to character
sets and languages as defined in RFC 2277 [RFC2277].
...
... Language Support ...
... Character Set Workshop Report [RFC2130] suggests that clients and
servers SHOULD negotiate a language for "greetings" and "error
messages". This specification interprets the use of the term "error
message", by RFC 2130 ...
...
Language support of greetings and command responses shall be the
default language supported by the server ...
... Language support of greetings and command responses shall be the
default language supported by the server or the language supported by
the server ...
... default language supported by the server or the language supported by
the server and selected by the client.
...
... FTP server might not support
virtual servers, or virtual servers might be configured to support an
environment without regard for language. To allow language
negotiation ...
... virtual servers, or virtual servers might be configured to support an
environment without regard for language. To allow language
negotiation this specification defines a new LANG command. Clients
and servers ...
... FTP command set to allow
server-FTP process to determine in which language to present server
greetings and the textual part of command responses. The parameter
associated with the LANG command SHALL be one of the language tags ...
... language to present server
greetings and the textual part of command responses. The parameter
associated with the LANG command SHALL be one of the language tags
defined in RFC 1766(-> 3282draft | 3066(-> 4647 | 4646)) [RFC1766 ...
... 1766(-> 3282draft | 3066(-> 4647 | 4646)) [RFC1766]. If a LANG command without a parameter
is issued the server's default language will be used.
...
...
Greetings and responses issued prior to language negotiation SHALL be
in the server's default language ...
... language negotiation SHALL be
in the server's default language. Paragraph 4.5 of [RFC2277] state
...
... RFC2277] state
that this "default language MUST be understandable by an English-
speaking person". This specification RECOMMENDS that the server
default language ...
... language MUST be understandable by an English-
speaking person". This specification RECOMMENDS that the server
default language be English encoded using ASCII. This text may be
augmented by text from other languages ...
... 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
...
... server-PI
MUST return server messages and textual part of command responses in
the negotiated language and encoded in UTF-8. Server-PI MAY wish to
...
... Server-PI MAY wish to
re-send previously issued server messages in the newly negotiated
language.
...
... User-PI SHOULD be capable of supporting UTF-8 encoding for the
language negotiated. Guidance on interpretation and rendering of
UTF-8, defined in section 3, SHALL apply.
...
... user-PI issues a HOST command, and the server's
default language is acceptable, it need not issue a LANG command.
However, if the implementation does not support the HOST command, a
...
... The OPTIONAL "Lang-tag" given as a parameter specifies the primary
language tags and zero or more sub-tags as defined in [RFC1766]. As
...
... RFC1766]. As
described in [RFC1766] language tags are treated as case insensitive.
If omitted server-PI MUST use the server's default language ...
... language tags are treated as case insensitive.
If omitted server-PI MUST use the server's default language.
Server-FTP ...
... - If server-FTP receives "Lang" with no parameters it SHOULD return
messages and command responses in the server default language.
- If server-FTP ...
... tag argument
(e.g. en, fr, de, ja, zh, etc.), which it can support, it SHOULD
return messages and command responses in the language associated
with that primary tag. It is possible that server-FTP ...
... tag(s)
argument, which is implemented, it SHOULD return messages and
command responses in support of the language argument. It is
possible that server-FTP can support the primary tag ...
... FTP sends a "LANG en-AU" command and server-FTP
has implemented language tags en-US and en-UK it may decide that the
most appropriate language tag is en-UK and return "200 en-AU not
...
... has implemented language tags en-US and en-UK it may decide that the
most appropriate language tag is en-UK and return "200 en-AU not
supported. Language set to en-UK". The numeric response is a protocol
element ...
... most appropriate language tag is en-UK and return "200 en-AU not
supported. Language set to en-UK". The numeric response is a protocol
element and can not be changed. The associated string is for
illustrative purposes only.
...
...
A server-FTP process that supports the LANG command, and language
support for messages and command responses, MUST include in the
response to the FEAT command ...
... RFC2389], a feature line indicating
that the LANG command is supported and a fact list of the supported
language tags. A response to a FEAT command SHALL be in the following
format:
...
...
The lang-feat response contains the string "LANG" followed by a
language fact. This string is not case sensitive, but SHOULD be
transmitted in upper case, as recommended in [RFC2389]. The initial
...
... In this example server-FTP can only support English, which is the
current language (as shown by the asterisk) being used by the server
for messages and command responses.
...
... by the initial response to the FEAT command. The asterisk indicates
that English is the current language in use by server-FTP. After a
LANG command is issued to change the language ...
... language in use by server-FTP. After a
LANG command is issued to change the language to French, the FEAT
response shows French as the current language ...
... character sets beyond 1 byte
and a new language negotiation command. Conformance to this document
should not induce a security risk ...
... Alvestrand, H., "Tags for the Identification of Languages", RFC 1766(-> 3282draft | 3066(-> 4647 | 4646)), March 1995. ...
... copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
...