re: Mixing text and graphics with text/enriched and multipart/mixed
Terry Crowley <tcrowley@vermeer.com> Fri, 03 May 1996 14:39 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id ab17781;
3 May 96 10:39 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17777;
3 May 96 10:39 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa11262;
3 May 96 10:39 EDT
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id KAA25793; Fri, 3 May 1996 10:28:03 -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 KAA25597 for
<ietf-822@list.cren.net>; Fri, 3 May 1996 10:26:49 -0400
Received: from vermeer.vermeer.com (vermeer.vermeer.com [204.252.75.5]) by
dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq+grosshack/8.6.12) with ESMTP
id KAA04413 for <ietf-822@dimacs.rutgers.edu>; Fri, 3 May 1996 10:26:39 -0400
Received: from localhost (uucp@localhost) by vermeer.vermeer.com (8.6.5/8.6.5)
id KAA14554; Fri, 3 May 1996 10:26:19 -0400
Received: from thoreau.vermeer.com(198.69.149.76) by vermeer.vermeer.com via
smap (V1.3) id sma014550; Fri May 3 10:25:59 1996
Message-Id: <BMSMTP83114327944tcrowley@vermeer>
Date: Fri, 3 May 1996 10:24:03 -0700
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: ietf-822@dimacs.rutgers.edu, Lennart Lovstrand <lennart@next.com>
Subject: re: Mixing text and graphics with text/enriched and multipart/mixed
In-Reply-To: <9605022322.AA06398@pan.next.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
>> 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>. I discovered this problem three or four years ago. As Nathaniel pointed out, the original MIME spec was indeed careful about being able to generate body parts (specifically text/richtext) that did not end in CRLF. Some interpreters (e.g Andrew) then interpreted this to mean that the following object should appear on the same line. However, the clarifications made when text/enriched was written to more carefully specify line breaking issues around alignment directives apparently broke this in the example you are giving. However, the more important issue is that multipart/mixed places no concrete requirements on the layout of the individual parts, certainly not to the details of how a missing or present CRLF on one object should change the way the following object is layed out. It was reasonably clearly understood at the time MIME was written that the proper way to handle this was to have one representation (e.g HTML) that specifies the relationship of a set of objects and then use multipart/mixed (or some other multipart subtype) as the way of packaging those objects. If someone desired to enhance text/enriched to provide the necessary control you want, the proper way of achieving this would be to support references within the text/enriched to other objects (e.g. by Content-ID) in a containing multipart/mixed object. Or to have some new multipart subtype that explicitly requires text/enriched as the first object followed by any referenced objects (one could make the argument that this more clearly reflects the semantics). Terry
- Internet draft draft-onions-822-mailproblems-00.t… Julian Onions
- Re: Internet draft draft-onions-822-mailproblems-… Tomas Kullman
- Re: Internet draft draft-onions-822-mailproblems-… Olle Jarnefors
- Re: Internet draft draft-onions-822-mailproblems-… Rick Troth
- Re: Internet draft draft-onions-822-mailproblems-… Rick Troth
- Re: Internet draft draft-onions-822-mailproblems-… Tomas Kullman
- Re: Internet draft draft-onions-822-mailproblems-… Rick Troth
- Re: Internet draft draft-onions-822-mailproblems-… Harald.T.Alvestrand
- Re: Internet draft draft-onions-822-mailproblems-… Harald.T.Alvestrand
- Re: Internet draft draft-onions-822-mailproblems-… Patrik Faltstrom
- Re: Internet draft draft-onions-822-mailproblems-… John Gardiner Myers
- Re: Internet draft draft-onions-822-mailproblems-… Ned Freed
- Re: Internet draft draft-onions-822-mailproblems-… Harald.T.Alvestrand
- Re: Internet draft draft-onions-822-mailproblems-… Patrik Faltstrom
- Re: Internet draft draft-onions-822-mailproblems-… Steve Dorner
- Re: Internet draft draft-onions-822-mailproblems-… Keith Moore
- Re: Internet draft draft-onions-822-mailproblems-… Steve Dorner
- Re: Internet draft draft-onions-822-mailproblems-… Ned Freed
- Re: Internet draft draft-onions-822-mailproblems-… John Gardiner Myers
- CR LF SPACE CR LF John Gardiner Myers
- Re: Internet draft draft-onions-822-mailproblems-… John Gardiner Myers
- Re: Internet draft draft-onions-822-mailproblems-… Ned Freed
- Mixing text and graphics with text/enriched and m… Lennart Lovstrand
- re: Mixing text and graphics with text/enriched a… Terry Crowley
- Re: Mixing text and graphics with text/enriched a… Harald.T.Alvestrand