Re: Accept: Client Profile

• Mail folder: WWW Talk Jul-Oct 1993
• Next message: Bill Janssen: "Re: Aliasing in HTML+"
• Previous message: joe@athena.mit.edu: "White space handling"
• In-reply-to: Jay C. Weber: "Re: Accept: Client Profile"
• References: Jay C. Weber: "Re: Accept: Client Profile"

Message-id: <UgPxgD0B0KGWAzQWoH@holmes.parc.xerox.com>
Date: 	Mon, 16 Aug 1993 12:07:59 PDT
Sender: Bill Janssen <janssen@parc.xerox.com>
From: Bill Janssen <janssen@parc.xerox.com>
To: www-talk@nxoc01.cern.ch, weber@yoyo.eitech.com (Jay C. Weber)
Subject: Re: Accept: Client Profile
In-reply-to: <9308141445.AA00671@yoyo>
References: <9308141445.AA00671@yoyo>
Status: RO

Excerpts from ext.WorldWideWeb: 14-Aug-93 Re: Accept: Client Profile Jay
C. Weber@yoyo.eitech (1541)

> 1. application/latex, troff-*, etc. should be text/* instead.  Something
> should be supertype text when it can be treated as text/plain by default.
> Note that this doesn't apply to Postcript, dvi, etc.

Note that if these types are defined as subtypes of text, you must be
careful to generated restricted definitions of them so that they do not
include pic or tbl (on the troff side), or other non-textual items.  In
general, I think they are better defined as subtypes of 'application',
not of 'text'.  The general discussion on the MIME list is wondering
whether there is any really appropriate subtype of 'text' besides
'plain'.  The experience with non-MIME readers encountering richtext,
and displaying it as 'text', has not been overwhelmingly positive.

Bill