Re: Line Wrapping Question

Terry Crowley <tcrowley@vermeer.com> Fri, 09 February 1996 15:23 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13635; 9 Feb 96 10:23 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ab13631; 9 Feb 96 10:23 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa08235; 9 Feb 96 10:23 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id JAA17815; Fri, 9 Feb 1996 09:35:06 -0500
Received: from vermeer.vermeer.com (vermeer.vermeer.com [204.252.75.5]) by list.cren.net (8.6.12/8.6.12) with ESMTP id JAA17659 for <ietf-822@list.cren.net>; Fri, 9 Feb 1996 09:31:29 -0500
Received: from localhost (uucp@localhost) by vermeer.vermeer.com (8.6.5/8.6.5) id JAA00170; Fri, 9 Feb 1996 09:30:47 -0500
Received: from thoreau.vermeer.com(198.69.149.76) by vermeer.vermeer.com via smap (V1.3) id sma000167; Fri Feb 9 09:30:45 1996
Message-Id: <BMSMTP82388578246tcrowley@vermeer>
Date: Fri, 9 Feb 1996 09:30:41 -0800
Reply-To: Terry Crowley <tcrowley@vermeer.com>
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Terry Crowley <tcrowley@vermeer.com>
To: Larry Masinter <masinter@parc.xerox.com>
Cc: ietf-822@list.cren.net, NED@innosoft.com, sukvg@wspu.microsoft.com
Subject: Re: Line Wrapping Question
In-Reply-To: <96Feb8.151107pst.2733@golden.parc.xerox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7Bit
X-Mailer: BeyondMail for Windows/SMTP 2.2
X-BeyondMail-Priority: 1
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN

>  Sorry to ask a stupid question, but why not use text/html instead of
>  text/enriched?

Larry,

Here's my take on it.  Millions of people are now using mail composition and
reading tools that support automatically wrapped text with very simple markup
(usually fonts and color, sometimes simple margins, alignment).  Text/enriched
is a good representation for that content and presentation material (personally
I wish it had been less schizoid with respect to procedural/semantic markup,
ie. had accepted that what was needed with precise procedural markup and had
actually provided precise margins, tabs, etc, but that's water under the
bridge).

text/html provides no special benefits for this type of content and is
significantly more complex to parse and layout.  It's therefore much less
likely that all mail readers/gateways etc will do something "useful" with it
(that is, convert it to a readable plain text representation).

That said, text/html is obviously going to be a major content type in MIME
mail, and mail vendors would find it well worth it to make the presentation of
text/html natural and seamless.  But I don't think it makes sense to take your
normal casual email note and convert it to text/html.

One other point: one of text/enriched's goals was to be an "acceptable" format,
even for non MIME mail readers.  While text/enriched is readable, I think must
vendors have found it is not "acceptable".  That is, if our customers are
sending mail to recipients without MIME software, they don't want to send
text/enriched, in the same way that they don't want to send QP - any oddities
make the sender look bad.  That's too bad, because it means slowly growing the
community to be distributing text/enriched rather than text/plain (when
text/enriched is the appropriate form for the presentation and content) has
proven difficult.  Not sure what to do about that, but if we keep on urging
vendors, including gateways,  to support text/enriched, than eventually we'll
get to a point where it is acceptable to send since few recipients will
actually see any oddities.

Terry