Enriched text
| Internet media type |
text/enriched |
|---|---|
| Type of format | Formatted text format |
| Standard | RFC 1896 |
Enriched text is a formatted text format for email, defined by the IETF in RFC 1896 and associated with the text/enriched MIME type which is defined in RFC 1563.
Format
[edit]It is "intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms". As of 2012, enriched text remained almost unknown in email traffic, while HTML email is widely used.[citation needed] Enriched text, or at least the subset of HTML that can be transformed into enriched text, is seen as preferable to full HTML for use with email (mainly because of security considerations).[1][2]
A predecessor of this MIME type was called text/richtext in RFC 1341 and RFC 1521. Neither should be confused with Rich Text Format (RTF, MIME type text/rtf or application/rtf) which are unrelated specifications, devised by Microsoft.
A single newline in enriched text is treated as a space. Formatting commands are in the same style as SGML and HTML. They must be balanced and nested.
Enriched text is a supported format of Emacs,[3] Mutt,[4] Mulberry and Netscape Communicator.
Examples
[edit]| Code | Output |
|---|---|
<bold>Hello, <italic>world!</italic></bold>
|
Hello, world! |
<color><param>red</param>Blood</color> is <bold>thicker</bold> than
<color><param>blue</param>water</color>.
<paraindent><param>left</param><italic>-- Well-known proverb
</italic></paraindent>
|
Blood is thicker than water.
|
References
[edit]- ^ "Why HTML is Inappropriate for E-Mail". www.avernus.com.
- ^ "EFAIL". efail.de. Retrieved 2021-01-05.
- ^ "gnu.org". www.gnu.org.
- ^ "The Mutt E-Mail Client: Mutt's MIME Support". Archived from the original on 2013-03-08. Retrieved 2013-02-26.