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

Pete Resnick <presnick@qualcomm.com> Sun, 05 May 1996 08:44 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08623; 5 May 96 4:44 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08619; 5 May 96 4:44 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa03928; 5 May 96 4:44 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net (8.6.12/8.6.12) with SMTP id EAA04056; Sun, 5 May 1996 04:20:23 -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 EAA04025 for <ietf-822@list.cren.net>; Sun, 5 May 1996 04:19:50 -0400
Received: from glaucus.cso.uiuc.edu (glaucus.cso.uiuc.edu [128.174.81.2]) by dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq+grosshack/8.6.12) with SMTP id EAA06773 for <ietf-822@dimacs.rutgers.edu>; Sun, 5 May 1996 04:19:42 -0400
Received: from resnick1.isdn.uiuc.edu by glaucus.cso.uiuc.edu (AIX 3.2/UCB 5.64/4.03) id AA11876; Sun, 5 May 1996 03:15:14 -0500
Message-Id: <v03006c04adb21448d852@resnick1.isdn.uiuc.edu>
Date: Sun, 5 May 1996 03:18:06 -0500
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Pete Resnick <presnick@qualcomm.com>
To: Martin R Raskovsky <martin@atelier.demon.co.uk>
Cc: ietf-822@dimacs.rutgers.edu
Subject: Re: Mixing text and graphics with text/enriched and multipart/mixed
In-Reply-To: <9605031605.AA10599@atelier.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: resnick@glaucus.cso.uiuc.edu
X-Mailer: Eudora [Macintosh version 3.0b108]
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN

On 5/3/96 at 11:05 AM  -0500, Martin R Raskovsky wrote:

>==| That doesn't help because each of the paragraph formatting commands like
>==| <center>, which is what Lennart was using, will cause a line break and
>==| commands cannot be continued across multipart boundaries.
>
>Does not matter that commands can not be continued provieded they do not
>force a line break accross a mixed boundary.

But how can you expect any interpreter to actually do something intelligent
across a multipart boundary? Are you claiming is that the text/enriched
commands may be left "open" at a multipart boundary? How would the
interpreter know where it is continued? And in what order? Remember, many
interpreters are handed the contents of a single part to work on without
any context. Creating something like you did with the expectation that it
would work as embedded images seems like a really bad plan.

>Is this against the spec?

Not directly. However, there is a passage which mentions this in the
discussion of using multiple character sets:

Every time a new character set is desired, a new MIME body part is started
with different character sets specified in the charset parameter of the
Content-type line. However, using multiple character sets this way in
text/enriched messages introduces problems. Since a change in the charset
parameter requires a new part, text/enriched formatting commands used in
the first part would not be able to apply to text that occurs in subsequent
parts. It is not possible for text/enriched formatting commands to apply
across MIME body part boundaries.

The assumption is simply made that this is not guaranteed to work.

pr

--
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated
Home: (217)337-1905 / Fax: (217)337-1980