RE: Line Wrapping Question
Pete Resnick <presnick@qualcomm.com> Thu, 08 February 1996 04:21 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00438;
7 Feb 96 23:21 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa00433;
7 Feb 96 23:21 EST
Received: from [198.76.81.2] by CNRI.Reston.VA.US id aa00366;
7 Feb 96 23:21 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id WAA27096; Wed, 7 Feb 1996 22:45:39 -0500
Received: from glaucus.cso.uiuc.edu (glaucus.cso.uiuc.edu [128.174.81.2]) by
list.cren.net (8.6.12/8.6.12) with SMTP id WAA27023 for
<ietf-822@list.cren.net>; Wed, 7 Feb 1996 22:44:48 -0500
Received: from resnick1.isdn.uiuc.edu by glaucus.cso.uiuc.edu (AIX 3.2/UCB
5.64/4.03) id AA06270; Wed, 7 Feb 1996 21:44:12 -0600
Message-Id: <v03004b03ad3f1519385a@resnick1.isdn.uiuc.edu>
Date: Wed, 7 Feb 1996 21:40:34 -0600
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: "Sukvinder Singh Gill (Exchange)" <sukvg@wspu.microsoft.com>
Cc: 'Ned Freed' <NED@innosoft.com>,
"ietf-822@list.cren.net" <ietf-822@list.cren.net>
Subject: RE: Line Wrapping Question
In-Reply-To: <c=US%a=_%p=Microsoft%l=DABONE960207174309QO005600@yuri.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: resnick@glaucus.cso.uiuc.edu
X-Mailer: Eudora [Macintosh version 3.0a75-2.96]
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN
On 2/7/96 at 7:43 PM, Sukvinder Singh Gill (Exchange) wrote: >Ned, I believe that your take on QP line wrapping is never >use the line wrapping for text/plain message bodies on >outbound messages, but do so for attachments right? I hope that's not what Ned meant. If a user wants to send long lines in text/plain, QP is a good thing. But I don't think that's the central issue here. Let's back up a bit and define the problem. The basic thing that you want is to deal with auto-wrapped text that the user is giving you. The user is typing with a composition tool which auto-wraps and they desire the same effect on the remote end. That is, they type a single pargraph without hitting the return key, and you want the same or similar auto-wrapping behavior to occur on receipt of such a message. Specifically, the sender doesn't care particularly how the line breaks appear on the screen of the recipient, so long as the text is "wrapped nicely". There is no way to represent the desire to have auto-wrapped text in text/plain. Text/plain makes no indication about presentation. And since QP line breaking is not a presentation mechanism either, that doesn't help you. So, in order to get the desired behavior, you need to go to another MIME type. Text/enriched is a good choice here. For users who have a text/enriched aware agent, the lines will have any inserted CRLFs replaced by spaces, and text/enriched specifies that lines should be presented properly wrapped. For those who don't have text/enriched, it is not a problem: If you get a subtype of text that you don't understand, you're supposed to treat it like text/plain. That means in the worst case, a user may get the text with CRLFs where the sender intended just the continuation of the line which would be wrapped. But since the text/enriched generator is responsible for inserting those CRLFs, they can be put in a reasonable place, somewhere less than 80 characters per line. For text that should not be unwrapped and autowrapped, you simply mark it as <nofill> in text/enriched. You could also use a proprietary format which indicates auto-wrapping presentation. But since there are people who have MIME programs which know how to do text/enriched, and all that you care about is the line wrapping, that wouldn't be terribly friendly. Take a look at the text/enriched draft that Amanda Walker and I wrote which is about to be released as an RFC. You can find it as: <ftp://ds.internic.net/internet-drafts/draft-resnick-text-enriched-03.txt> or an HTML version of the doc at: <http://www.qualcomm.com/People/presnick/textenriched.html> It really looks like this is what you want to do. pr -- Pete Resnick <mailto:presnick@qualcomm.com> QUALCOMM Incorporated Home: (217)337-1905 / Fax: (217)337-1980
- Line Wrapping Question Sukvinder Singh Gill (Exchange)
- Re: Line Wrapping Question Donald E. Eastlake 3rd
- RE: Line Wrapping Question Sukvinder Singh Gill (Exchange)
- Re: Line Wrapping Question Valdis.Kletnieks
- Re: Line Wrapping Question Ned Freed
- Re: Line Wrapping Question Ned Freed
- Re: Line Wrapping Question Terry Crowley
- Re: Line Wrapping Question Ned Freed
- RE: Line Wrapping Question Sukvinder Singh Gill (Exchange)
- RE: Line Wrapping Question Ned Freed
- RE: Line Wrapping Question Pete Resnick
- Re: Line Wrapping Question Jamie Zawinski
- Re: Line Wrapping Question John W. Noerenberg
- Re: Line Wrapping Question Jamie Zawinski
- Re: Line Wrapping Question Terry Crowley
- Using Quoted-Printable (Re: Line Wrapping Questio… Harald.T.Alvestrand
- Re: Line Wrapping Question Jim Conklin
- Re: Line Wrapping Question Ned Freed
- Re: Line Wrapping Question John W. Noerenberg
- Re: Line Wrapping Question Barton E. Schaefer
- Re: Line Wrapping Question Larry Masinter
- Re: Line Wrapping Question Lennart Lovstrand
- Re: Line Wrapping Question Larry Masinter
- Re: Line Wrapping Question Ned Freed
- Re: Line Wrapping Question Pete Resnick
- Re: Line Wrapping Question Ned Freed
- Re: Line Wrapping Question Terry Crowley
- Re: Line Wrapping Question Jim Conklin
- Re: Line Wrapping Question Ned Freed
- Re: Line Wrapping Question Ned Freed
- Re: Line Wrapping Question Terry Crowley
- Re: Line Wrapping Question Terry Crowley
- The extent of <nofill> and other text/enriched ni… Lennart Lovstrand
- Re: The extent of <nofill> and other text/enriche… Pete Resnick