…ed with the LANG command SHALL be one of the language tags defined in RFC 1766 [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 lang…
…ed with the LANG command SHALL be one of the language tags defined in RFC 1766 [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 lang…
…ted with the LANG command SHALL be one of the language tags defined in RFC 1766 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 lan…
…ted with the LANG command SHALL be one of the language tags defined in RFC 1766 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 lan…
…tify a language tag string specifically; the language tag itself makes use of [ RFC1766 ] language tag strings spelled out using the Plane 14 tag characters. Provision of a specific, low-overhead mechanism for embedding language tags in plain text is aimed at meeting the need of …
…nt replaces [ RFC4646 ] (which obsoleted [ RFC3066 ] which, in turn, replaced [ RFC1766 ]). This document, in combination with [ RFC4647 ], comprises BCP 47 . For a list of changes in this document, see Section 8 . The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT…
…nt replaces [ RFC4646 ] (which obsoleted [ RFC3066 ] which, in turn, replaced [ RFC1766 ]). This document, in combination with [ RFC4647 ], comprises BCP 47 . For a list of changes in this document, see Section 8 . The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT…
…cument, in combination with [ RFC4646 ], replaces [ RFC3066 ], which replaced [ RFC1766 ]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC…
…ocument replaces [RFC4646] (which obsoleted [RFC3066] which, in turn, replaced [RFC1766]). This document, in combination with [RFC4647], comprises BCP 47. For a list of changes in this document, see Section 8. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "S…
…nt replaces [ RFC4646 ] (which obsoleted [ RFC3066 ] which, in turn, replaced [ RFC1766 ]). This document, in combination with RFC4647 ], comprises BCP 47 . For a list of changes in this document, see Section 8 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "…
…nt replaces [ RFC4646 ] (which obsoleted [ RFC3066 ] which, in turn, replaced [ RFC1766 ]). This document, in combination with RFC4647 ], comprises BCP 47 . For a list of changes in this document, see Section 8 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "…
…cument, in combination with [ RFC4646 ], replaces [ RFC3066 ], which replaced [ RFC1766 ]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC…
…is document, in combination with [RFC4646], replaces [RFC3066], which replaced [RFC1766]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC21…
…nt replaces [ RFC4646 ] (which obsoleted [ RFC3066 ] which, in turn, replaced [ RFC1766 ]). This document, in combination with RFC4647 ], comprises BCP 47 . For a list of changes in this document, see Section 8 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "…
…cument, in combination with [ RFC4646 ], replaces [ RFC3066 ], which replaced [ RFC1766 ]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC…