In Eudora (later versions) a format "flowed" is used to tell the client that even though the text is wordwrapped, it is one paragraph and one should be able to change linebreaks to avoid things like: > Really Really Really Really Really Really Really Really > long > row that is an example of the stupid linebreaks caused by > rows > getting longer when quoting. One could use HTML to avoid this but flowed is a better idea since it also makes the message readable as plain text. I'm not into all details in the format but I could research it if you think it's an interesting idea. What I do know (by looking at messages sent by Eudora) is that they have a special content-type, for instance: Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Type: text/plain; format=flowed or Content-Type: text/plain; charset="us-ascii"; format=flowed you see the pattern? I also thinks Hotmail does this. (Please change the component to a more appropriate, I just guessed.)

Adding to [HELP WANTED] list and reassigning to nobody@mozilla.org

I found the specification at ftp://ftp.ietf.org/internet-drafts/draft-gellens-format-06.txt It's a good thing and I would really like to see it in mozilla. I will look at this but I don't think I can find the time anytime soon. Is the mime converters a good place to start?

Ok, I want to work on this. Assigning the bug to myself.

By the way, it is no longer a draft. See RFC 2646.

I attached a libmime class that should make it possible to view format=flowed mails in the enhanced way. Feel free to test and give me feedback.

By the way. To implement this in mozilla would be a possible solution to bug 2916.

The first half (approximately the part in the attachments) checked in by rhp@netscape.com. (Yes, I confess, I'm the nameless external contributor mentioned. :-)

Just to clarify. I've only done the format=flowed-support part. The new MimeURLUtils is not something I been involved in.

Daniel Bratell, work collosion. You changed major parts of nsHTMLToTXTSinkStream, while I was working on it (and mad large changes), too. Please stop working at least on that class until I merged the changes. Thanks. Akk knows about it.

see bugs #16507 and 16800

Daniel, sorry if I sounded bad in my last comment. I was just a bit frustrated. Unfortunately, I will need some time, until I finish bug #17723 (added as dependency). Are there still things to do for you in the sink (nsHTMLToTXTSinkStream)? Is yes, please tell me, so we can find a solution.

With todays checkin (done by Akkana) it should both be possible to send mail with format=flowed (It's controlled with a pref mailnews.send_plaintext_flowed) and read format=flowed mail in mozilla.

changing qa assigned to pmock@netscape.com

I sent a e-mail to Daniel asking for his help. I wrote: ---- Subject: Need help understanding the fix for bug 16398 Date: Tue, 04 Jan 2000 14:24:43 -0800 From: pmock@netscape.com (Peter Mock) To: bratell@lysator.liu.se CC: rhp@netscape.com Hello Daniel, I attempting to verify bug 16398 "Support format=flowed (RFC 2646) in mail", but I'm having difficult getting this feature to work. By default, any plain text message that is sent has the message content-type set with format=flow, I have been unsuccessful in getting the text to flow as specified in RFC 2646. I've tried to enabling/disabling the preference mailnews.send_plaintext_flowed and read format=flowed mail but with no results. Is this the correct user preference? Could you confirm if this feature is still working for you? I noticed that mozilla@bucksch.org is working on bug 17723 which share some of the same code. Thank you for your help. /Peter Client Mail QA

I should mention that I was testing with the 2000-01-03 builds. ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2000-01-03-09-M13/sea monkey32e.exe ftp://sweetlou/products/client/seamonkey/unix/linux_glibc/2.2/x86/2000-01-03-08- M13/netscape-i686-pc-linux-gnu.tar.gz ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/2000-01-03-08-M13/NSMacIn staller-M13.sea.bin

Reopening, because plain text mail is no longer composed as format=flowed. The mails are marked as such, but they are not. There are several other problems with plain text composing of mail that may be related to this. There is also some problems with the conversion from html to plain text. It is as the mail is line wrapped after the conversion even though it is line wrapped already in the conversion. As the mail is sent as Quoted Printable the lines has hot a little longer so the line wrapping gets strange. Reading format=flowed mails still works though.

Clearing resolution.

Thank you Daniel for reviewing this bug. :)

CC'ed nhotta and myself.

When composing with plaintext the outputsink was initialized with mPreFormatted, nsIDocumentEncoder::OutputPreformatted and nsIDocumentEncoder::OutputFormatted. That combination went through the "just emit what comes in"-path and was neither wrapped nor formatted for "format=flowed". I've tried to change so that combination goes through the intelligent code path, but I have no idea if that breaks anything else. I'll attach the patch for testing.

Added John M. to CC.

Well, it works now. It must have been a temporary thing elsewehere in the code. I'll close this as FIXED again.

Verified as fixed on Windows, Linux and Mac using the following: Windows commercial seamonkey build 2000-060909-m17 installed on PIII win98 Linux commercial seamonkey build 2000-060908-m17 installed on PII RedHat 6.1 MacOS commercial seamonkey build 2000-060908-m17 installed on G3/400 OS 9.04

Forgot to clear status on whiteboard.