7 - 8 - A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
character set
Click on the red underlined text to get to the source
... MIME media types. The third document
describes extensions to RFC 822std11(-> 2822prop) formats to allow for character sets
other than US-ASCII. This document describes what portions of MIME ...
... to send at least text/plain messages, with the
character set specified with the charset parameter if
it is not US-ASCII ...
...
-- Recognize and display "text" mail with the
character set "US-ASCII."
...
... US-ASCII."
-- Recognize other character sets at least to the
extent of being able to inform the user about what
character set ...
... character sets at least to the
extent of being able to inform the user about what
character set the message uses.
-- Recognize the "ISO ...
...
-- Recognize the "ISO-8859-*" character sets to the
extent of being able to display those characters that
are common to ISO ...
... octet values 1-127.
-- For unrecognized subtypes in a known character
set, show or offer to show the user the "raw" version
of the data after conversion of the content from
...
... canonical form to local form.
-- Treat material in an unknown character set as if
it were "application/octet-stream".
...
... non-standard support for non-MIME messages employing
character sets other than US-ASCII, to do so on
received messages only. Conforming user agents ...
... MIME labelling when sending anything other than plain
text in the US-ASCII character set.
In addition, non-MIME ...
... must support both the "B" and "Q" encodings for any
character set which it supports. The program must be
able to display the unencoded text if the character set
...
... character set which it supports. The program must be
able to display the unencoded text if the character set
is "US-ASCII". For the ISO ...
... is "US-ASCII". For the ISO-8859-* character sets, the
mail reading program must at least be able to display
the characters which are also in the US-ASCII ...
... This is unavoidable in some environments, notably those
not based on the US-ASCII character set. Such
conversion is STRONGLY DISCOURAGED, but it may occur,
and mail formats must not rely on the persistence of
...
... The body to be transmitted is created in the system's
native format. The native character set is used and,
where appropriate, local end of line conventions are
used as well. The body may be a UNIX-style ...
... canonical form that is used. Conversion to the proper
canonical form may involve character set conversion,
transformation of audio data, compression ...
... other operations specific to the various media types.
If character set conversion is involved, however, care
must be taken to understand the semantics of the media
type ...
... semantics of the media
type, which may have strong implications for any
character set conversion, e.g. with regard to
syntactically meaningful characters in a text subtype
other than "plain".
...
... For example, in the case of text/plain data, the text
must be converted to a supported character set and
lines must be delimited with CRLF delimiters in
...
...
must be first represented in the text/foo form, then (if necessary)
represented in the "bar" character set, and finally transformed via
the base64 algorithm ...
... text message in a
non-ASCII character set. The embedded multipart message itself
contains two objects to be displayed in parallel, a picture and an
audio ...
... header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]
...
...
(4) The more specific "US-ASCII" character set name has
replaced the use of the informal term ASCII in many
...
... message/external-body".
(15) The definition of a character set has been reorganized
to make the requirements clearer.
...
... been extensively revised. IANA registration procedures
for character sets have been moved to a separate
document that is no included in this set of documents.
...
... US-ASCII
and ISO-8859-X character sets these documents define
have been clarified: Such mechanisms should never be
used in conjunction ...
... have been clarified: Such mechanisms should never be
used in conjunction with these character sets and their
effect if they are used is undefined.
...
... International Standard -- Information Processing -- 8-bit Single-Byte Coded Graphic Character Sets - Part 1: Latin Alphabet No. 1, ISO 8859-1:1987, 1st ed. - Part 2: Latin Alphabet No. 2, ISO 8859-2:1987, 1st ed. - Part 3: Latin Alphabet No. 3, ISO ...
... ISO 8859-8:1988, 1st ed. - Part 9: Latin Alphabet No. 5, ISO/IEC 8859-9:1989, 1st ed. International Standard -- Information Technology -- 8-bit Single-Byte Coded Graphic Character Sets - Part 10: Latin Alphabet No. 6, ISO/IEC 8859-10:1992, 1st ed. ...
... International Standard -- Information Technology -- ISO 7-bit Coded Character Set for Information Interchange, ISO 646:1991, 3rd ed.. ...
... Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, June 1992. ...
... Coded Character Set -- 7-Bit American Standard Code for Information Interchange, ANSI X3.4-1986. ...