Skip to main content

Multiple Language Content Type
RFC 8255

Revision differences

Document history

Date By Action
2017-10-12
(System) IANA registries were updated to include RFC8255
2017-10-10
(System)
Received changes through RFC Editor sync (created alias RFC 8255, changed abstract to 'This document defines the 'multipart/multilingual' content type, which is an addition …
Received changes through RFC Editor sync (created alias RFC 8255, changed abstract to 'This document defines the 'multipart/multilingual' content type, which is an addition to the Multipurpose Internet Mail Extensions (MIME) standard.  This content type makes it possible to send one message that contains multiple language versions of the same information.  The translations would be identified by a language tag and selected by the email client based on a user's language settings.', changed pages to 19, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-10-10, changed IESG state to RFC Published)
2017-10-10
(System) RFC published