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

character set


Click on the red underlined text to get to the source

... a means to specify parameter values in character sets other than US-ASCII, ...
... 2047draft to allow the specification of the language to be used for display as well as the character set. ...


... textual message bodies in character sets other than US-ASCII, ...
... textual header information in character sets other than US-ASCII. ...
... parameter values. This makes it impossible to have parameter values in character sets other than US-ASCII without specifying some sort of private per- ...
... It has recently become clear that character set information is not sufficient to properly display some sorts of information -- language ...


... Parameter Value Character Set and Language Information ...
... Some parameter values may need to be qualified with character set or language information. It is clear that a distinguished parameter ...
... Asterisks ("*") are reused to provide the indicator that language and character set information is present and encoding is being used. A single quote ("'") is used to delimit the character set ...
... character set information is present and encoding is being used. A single quote ("'") is used to delimit the character set and language information at the beginning of the parameter value ...
... 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 ...
... the beginning of the parameter value. A single quote is used to separate the character set, language, and actual value information in ...
... 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 ...
... 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, language, or both are not relevant to the parameter value ...
... are not relevant to the parameter value at hand. This MUST NOT be done in order to indicate a default character set or language -- parameter field definitions ...
... language -- parameter field definitions MUST NOT assign a default character set or lanugage. ...
... 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. ...
... segment of a continuation MUST be encoded if language and character set information are given. ...
... parameter value is encoded the language and character set field delimiters MUST be present even when the fields are left blank. ...


... RFC 2047draft provides support for non-US-ASCII character sets in RFC 822std11(-> 2822prop) message header ...
... display, it is sometimes necessary to associate language information with encoded words as well as just the character set. This specification extends the definition of an encoded word to allow the inclusion of such information. This is simply done by suffixing the ...
... specification extends the definition of an encoded word to allow the inclusion of such information. This is simply done by suffixing the character set specification with an asterisk followed by the language tag. For example: ...


... charset := <registered character set name> language ...


... 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 ...


... Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson, R., Crispin, M., Svanberg, P., "Report from the IAB Character Set Workshop", RFC 2130, April 1997. ...



Google
Web
RFC-Ref