RFC 2184:MIME Parameter Value and Encoded Word Ext...
RFC-Ref

language


Click on the red underlined text to get to the source

... to specify the language to be used should the value be displayed, and ...
... This memo also defines an extension to the encoded words defined in RFC 2047draft to allow the specification of the language to be used for display as well as the character set. ...


... character set information is not sufficient to properly display some sorts of information -- language information is also needed [RFC-2130]. For example, support for handicapped users may require reading ...
... RFC-2130]. For example, support for handicapped users may require reading text string aloud. The language the text is written in is needed for this to be done correctly. Some parameter values ...
... parameter values may need to be displayed, hence there is a need to allow for the inclusion of language information. ...


... Parameter Value Character Set and Language Information ...
... parameter values may need to be qualified with character set or language information. It is clear that a distinguished parameter name is needed to identify when this information is present along with a specific syntax for the information in the value itself. In ...
... Asterisks ("*") are reused to provide the indicator that language and character set information is present and encoding ...
... encoding is being used. A single quote ("'") is used to delimit the character set and language information at the beginning of the parameter value. Percent signs ...
... Specifically, an asterisk at the end of a parameter name acts as an indicator that character set and language information may appear at the beginning of the parameter value. A single quote is used to ...
... parameter value. A single quote is used to separate the character set, language, and actual value information in the parameter value ...
... Note that it is perfectly permissible to leave either the character set or language field blank. Note also that the single quote delimiters MUST be present even when one of the field values is omitted. This is done when either character set ...
... delimiters MUST be present even when one of the field values is omitted. This is done when either character set, language, or both are not relevant to the parameter value at hand. This MUST NOT be ...
... parameter value at hand. This MUST NOT be done in order to indicate a default character set or language -- parameter field definitions MUST NOT assign a default character set ...
... Combining Character Set, Language, and Parameter Continuations ...
... Character set and language information may be combined with the parameter continuation mechanism. For example: ...
... Language and character set information only appear at the beginning of a given parameter value ...
... Continuations do not provide a facility for using more than one character set or language in the same parameter value. ...
... The first segment of a continuation MUST be encoded if language and character set information are given. ...
... segment of a continued parameter value is encoded the language and character set field delimiters MUST be present even when the fields are left blank. ...


... Language specification in Encoded Words ...
... This is done by defining an encoded word construct which can appear in any of these places. Given that these are fields intended for display, it is sometimes necessary to associate language information with encoded words as well as just the character set. This ...
... inclusion of such information. This is simply done by suffixing the character set specification with an asterisk followed by the language tag. For example: ...


... extended-initial-value := [charset] "'" [language] "'" extended-other-values ...
... character set name> language := <registered language tag [RFC-1766]> ...
... language := <registered language tag [RFC-1766]> ...
... encoded-word := "=?" charset ["*" language] "?" encoded-text "?=" ...


... Character sets which allow specification of language ...
... In the future it is likely that some character sets will provide facilities for inline language labelling. Such facilities are inherently more flexible than those defined here as they allow for language ...
... language labelling. Such facilities are inherently more flexible than those defined here as they allow for language switching in the middle of a string. ...
... If and when such facilities are developed they SHOULD be used in preference to the language labelling facilities specified here. Note that all the mechanisms defined here allow for the omission of language ...
... language labelling facilities specified here. Note that all the mechanisms defined here allow for the omission of language labels so as to be able to accomodate this possible future usage. ...


... Alvestrand, H., "Tags for the Identification of Languages", RFC 1766(-> 3282draft | 3066(-> 4647 | 4646)), March 1995. ...



Google
Web
RFC-Ref