Enriched text
| Internet media type |
text/enriched |
|---|---|
| Type of format | Formatted textformat |
| Standard | RFC 1896 |
Enriched textis aformatted textformatforemail,defined by theIETFin RFC 1896 and associated with thetext/enrichedMIMEtype 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, whileHTML emailis 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 calledtext/richtextin RFC 1341 and RFC 1521. Neither should be confused withRich Text Format(RTF, MIME typetext/rtforapplication/rtf) which are unrelated specifications, devised byMicrosoft.
A single newline in enriched text is treated as a space. Formatting commands are in the same style asSGMLandHTML.They must be balanced and nested.
Enriched text is a supported format ofEmacs,[3]Mutt,[4]MulberryandNetscape 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-knownproverb
</italic></paraindent>
|
Bloodisthickerthanwater.
|
References
[edit]- ^"Why HTML is Inappropriate for E-Mail".avernus.
- ^"EFAIL".efail.de.Retrieved2021-01-05.
- ^"gnu.org".gnu.org.
- ^"The Mutt E-Mail Client: Mutt's MIME Support".Archived fromthe originalon 2013-03-08.Retrieved2013-02-26.