Mixing text and graphics with text/enriched and multipart/mixed

Lennart Lovstrand <lennart@next.com> Thu, 02 May 1996 23:37 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17201; 2 May 96 19:37 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17197; 2 May 96 19:37 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa04567; 2 May 96 19:37 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id TAA13003; Thu, 2 May 1996 19:25:01 -0400
Received: from dimacs.rutgers.edu (root@dimacs.rutgers.edu [128.6.75.16]) by list.cren.net (8.6.12/8.6.12) with ESMTP id TAA12940 for <ietf-822@list.cren.net>; Thu, 2 May 1996 19:23:36 -0400
Received: from pan.next.com (sn2h199.next.com [129.18.2.199]) by dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq+grosshack/8.6.12) with SMTP id TAA12798 for <ietf-822@dimacs.rutgers.edu>; Thu, 2 May 1996 19:23:30 -0400
Received: by pan.next.com (NX5.67f1/NX3.0M) id AA06398; Thu, 2 May 96 16:22:53 -0700
Received: by NeXT.Mailer (1.146)
Message-Id: <9605022322.AA06398@pan.next.com>
Date: Thu, 2 May 96 16:22:50 -0700
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Lennart Lovstrand <lennart@next.com>
To: ietf-822@dimacs.rutgers.edu
Subject: Mixing text and graphics with text/enriched and multipart/mixed
References: <01HNH1XQWT8699DGKL@INNOSOFT.COM>
Mime-Version: 1.0 (NeXT Mail 3.3risc v146)
Content-Type: text/enriched; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Url: http://www.next.com/~lennart
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN

Earlier today, I was debugging a problem where a message was sent with
some text and images centered on the same line, but got received with the
same images and text split into separate lines.  At first, I thought there
was a bug in our text/enriched generator or parser, but then I came across
this section in RFC1563:

<nofill>
>    [...] Each of these commands  force a line break before and after
>    the formatting environment if there is not otherwise a line break.
>    For example, if one of these commands occurs anywhere other than the
>    beginning of a line of text as presented, a new line is begun.
> 
>       Center -- causes the affected text to be centered.
</nofill>

The only currently "standard" way of mixing rich text and graphics in MIME
that I know of is to use an enclosing multipart/mixed containing
text/enriched and image/* body parts.  However, since each text/enriched
part needs to be complete in itself, we need to terminate the <<center>
directive before adding each image/* part.  This, in turn, means that
we'll be forcing a newline to be displayed on the receiving end next to
each <<center> or <</center>.


Unless I'm missing something, this is really bad, but I don't see any way
around this with the standard as it is today.  This and a few other
gotchas we've had in the past makes me wonder how many other real
implementations of text/enriched there are out there.  I suspect not very
many.  Hopefully, this will all change with emergence of text/html in
MIME, though.  (Go for it, Jacob!)

<nofill>
Lennart Lövstrand
NeXT Software Engineering
</nofill>