Browse Prior Art Database

The text/enriched MIME Content-type (RFC1563)

IP.com Disclosure Number: IPCOM000002397D
Original Publication Date: 1994-Jan-01
Included in the Prior Art Database: 2001-Nov-09
Document File: 17 page(s) / 33K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

N. Borenstein: AUTHOR

Abstract

MIME [RFC-1341, RFC-1521] defines a format and general framework for the representation of a wide variety of data types in Internet mail. This document defines one particular type of MIME data, the text/enriched type, a refinement of the "text/richtext" type defined in RFC 1341. The text/enriched MIME type is intended to facilitate the wider interoperation of simple enriched text across a wide variety of hardware and software platforms.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 11% of the total text.

Network Working Group                                      N. Borenstein

Request for Comments: 1563                                      Bellcore

Obsoletes: 1523                                             January 1994

Category: Informational

                  The text/enriched MIME Content-type

Status of this Memo

   This memo provides information for the Internet community.  This memo

   does not specify an Internet standard of any kind.  Distribution of

   this memo is unlimited.

Abstract

   MIME [RFC-1341, RFC-1521] defines a format and general framework for

   the representation of a wide variety of data types in Internet mail.

   This document defines one particular type of MIME data, the

   text/enriched type, a refinement of the "text/richtext" type defined

   in RFC 1341.  The text/enriched MIME type is intended to facilitate

   the wider interoperation of simple enriched text across a wide

   variety of hardware and software platforms.

Table of Contents

   The Text/enriched MIME type..............................  2

   Formatting Commands......................................  4

         Font-Alteration Commands...........................  4

         Fill/Justification Commands........................  5

         Indentation Commands...............................  6

         Miscellaneous Commands.............................  6

         Balancing and Nesting of Formatting Commands.......  7

         Unrecognized formatting commands...................  8

   White Space in Text/enriched Data........................  8

   Initial State of a text/enriched interpreter.............  8

   Non-ASCII character sets.................................  8

   Minimal text/enriched conformance........................  9

   Notes for Implementors...................................  9

   Extensions to text/enriched.............................. 10

   An Example............................................... 11

   Security Considerations.................................. 12

   Author's Address......................................... 12

   Acknowledgements......................................... 12

   References............................................... 12

   Appendix A -- A Simple enriched-to-plain Translator in C. 13

   Appendix B -- Differences from RFC 1341 text/richtext.... 15

Borenstein                                                      [Page 1]

RFC 1563             A text/enriched type for MIME          January 1994

The Text/enriched MIME type

   In order to promote the wider interoperability of simple formatted

   text, this document defines an extremely simple subtype of the MIME

   content-type "text", the "text/enriched" subtype.  This subtype was

   designed to meet the following criteria:

      1.  The syntax must be extremely simple to parse,

          so that even teletype-oriented mail systems can

          easily strip away the formatting information and

          leave only the readable text.

      2.  The syntax must be extensible to allow for new

          formatting commands that are deemed essential for

          some application.

      3.  If the character set in use is ASCII or an 8-

          bit ASCII superset, then the raw form of the data

          must be readable enough to be largely

          unobjectionable in the event that it is displayed

          on the screen of the user of a non-MIME-conformant

          mail reader.

      4.  The capabilities must be extremely limited, to

          ensure that it ca...