ietf-822
[Top] [All Lists]

Re: overdefining text/plain?

1998-03-11 08:22:37
From: Ned Freed <Ned(_dot_)Freed(_at_)innosoft(_dot_)com>
To: Dan Kohn <dan(_at_)teledesic(_dot_)com>
Cc: Ned Freed <Ned(_dot_)Freed(_at_)innosoft(_dot_)com>; Bill Janssen
<janssen(_at_)parc(_dot_)xerox(_dot_)com>; ietf-822(_at_)imc(_dot_)org 
<ietf-822(_at_)imc(_dot_)org>; Chris Newman
<Chris(_dot_)Newman(_at_)innosoft(_dot_)com>; Paul Hoffman 
<phoffman(_at_)imc(_dot_)org>
Date: Wednesday, March 11, 1998 12:25 AM
Subject: RE: overdefining text/plain?


Well, for one thing, it's implicit in the first conformance requirement for
text when the charset is US-ASCII:

 -- Recognize and display "text" mail with the charset "US-ASCII."

This doesn't say anything about the subtype being "plain".

But then there's an explicit conformance requirement covering this case:

 -- For unrecognized subtypes in a known charset, show or offer to show
 the user the "raw" version of the data after conversion of the content
from
 canonical form to local form.


How does converting the text/paragraph entity to an attachment violate
either of these constraints?


<Prev in Thread] Current Thread [Next in Thread>