…nd future extension. This document, in combination with [ RFC4647 ], replaces [ RFC3066 ], which replaced [ RFC1766 ]. For a list of changes in this document, see Section 8 The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "…
…ping between 2-letter codes and 3-letter codes is not part of this format.), or RFC3066 ] codes that do not contain script / territory codes. script_code ASCII letters ISO15924 ] 4-letter codes. In most cases the script is not necessary, since the language is only customarily wri…
…es and future extensions. This document 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 …
…ng between 2-letter codes and 3-letter codes is not part of this format.), or [ RFC3066 ] codes that do not contain script / territory codes. script_code ASCII letters [ ISO15924 ] 4-letter codes. In most cases the script is not necessary, since the language is only customarily w…
…es and future extensions. This document 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 …
…alues and future extensions. This document 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", "…
…es and future extensions. This document 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"…
…es and future extensions. This document 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"…
… the same syntax. The latest draft text and registry for that successor is at [ RFC3066bis ]. The field values are given in the following table. All field values are case-insensitive, except for the type , which is case-sensitive. However, customarily the language code is lowerca…
…ping between 2-letter codes and 3-letter codes is not part of this format.), or RFC3066 ] codes that do not contain script / territory codes. script_code ASCII letters ISO15924 ] 4-letter codes. In most cases the script is not necessary, since the language is only customarily wri…
… the same syntax. The latest draft text and registry for that successor is at [ RFC3066bis ]. The field values are given in the following table. All field values are case-insensitive, except for the type , which is case-sensitive. However, customarily the language code is lowerca…
…es and future extensions. This document 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"…
…using these schemes. This 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 inter…
…using these schemes. This 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 inter…
US
rfc4647
https://www.rfc-editor.org/rfc/inline-errata/rfc4647.html
…nd using these schemes. This 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 interpre…
Page 1
Next →