MIME
Click on the red underlined text to get to the source
... Internet. Because the term is used to mean different things,
confusion has arisen. For example, the MIME registry of character
sets [MIME ...
... of these components are already familiar to the users of encoding
protocols such as MIME. Not all of these are discussed in detail in
this report; we restrict ourselves primarily to those components
...
... wrapper placed around the text for transport.
MIME headers are a good example of this technique.
- Included in the data stream, where the data stream ...
... useful in particular situations, interoperability requires a more
consistent set of techniques. Thus, we recommend that MIME
registered values be used for all tagging of character sets and
...
... IAB.
However, it is important to point out that the MIME concept of
'charset' in some cases cuts across several layers of components in
...
... our model. While this can be accepted in existing registrations, we
also recommend that the MIME registration procedure for character
sets be modified to show how a proposed character set deals with the
...
... ISO-8859-1 for HTTP. The recommended specification scheme is the
MIME "charset" specification, using the IANA "charset ...
... IANA "charset"
specifications. The MIME specifications will need to be clarified to
meet this model in the future.
...
... the same recommendation holds as above. The specification technique
should either be defined in the protocol, if only one way is
permitted, or by use of MIME content-transfer-encoding (CTE)
techniques, using IANA ...
... readable text, there should always be a way to specify the natural
language. The specification technique should be a MIME identifier
with IANA ...
...
There is no recommended default for the Culture level. The
specification technique should be a MIME or MIME-like identifier
...
... There is no recommended default for the Culture level. The
specification technique should be a MIME or MIME-like identifier
(e.g. Content-Culture) and should use the Cultural register ...
...
There is no recommended default for the Presentation level. The
specification technique should be a MIME or MIME-like identifier
...
... There is no recommended default for the Presentation level. The
specification technique should be a MIME or MIME-like identifier
(e.g. Content-Layout) and use the glyph register ...
... Because stored text may very well be stored without any of the
additional information necessary for decoding, stored text SHOULD be
tagged in a MIME compliant fashion. This alleviates the problem of
being unable to interpret text which has been stored for a long time,
...
... information to display the text properly.
It was observed that in contemporary usage of MIME charsets, the
language ...
... To specify the language used in a particular block of text, we
recommend that the MIME tag "Content-Language" be used. There are a
...
... Register UTF-8 as a Character Encoding Scheme for MIME.
H: The current use of the "x-*" format for distinguishing
...
...
Ned Freed will be releasing a new MIME registration document in
conjunction with this paper.
...
... Email text bodies is
reasonably well covered by the charset= parameter on Text/* MIME
types. Language is defined by the Content-language header ...
... 1766(-> 3282draft | 3066(-> 4647 | 4646)). Other information will have to be added using body
part headers; due to the way MIME differentiates between body
part headers and message headers ...
... IMAP
IMAP's information objects are MIME Email objects, and therefore
are able to use that standard's methods ...
... Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045draft, November 1996. ...
... SINTEF DELAB, August 1993.
Borenstein, N., "Implications of MIME for Internet Mail Gateways",
...
...
Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045draft ...
... Freed, N., and N. Borenstein, "Multipurpose Internet Mail Extensions
(MIME) Part Two: Media Types", RFC 2046draft, November 1996.
...
...
Goldsmith, D., and M. Davis, "Using Unicode with MIME", RFC 1641exp,
Taligent, Inc., July 1994.
...
... University, July 1972.
Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Two:
Message Header Extensions ...
... 2047draft.)
Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three:
Message Header Extensions ...
...
Nussbacher, H., "Handling of Bi-directional Texts in MIME", Israeli
Inter-University, December 1993.
...