Re: format=flowed text -> RTFM + RTF FAQ + RTF RFC

u* Sven Guckes <guckes <at> math.fu-berlin.de> [01-Dec-2002 21:27]:
> * James Marsh <james <at> snoopy.freeserve.co.uk> [2002-12-01 19:54]:
> > * Sven Guckes <guckes <at> math.fu-berlin.de> [01-Dec-2002 19:46]:
> > > * David Champion <dgc <at> uchicago.edu> [2002-12-01 19:28]:
> > > > I think it's still a valid mutt issue. Those among us who
> > > > don't (and won't) use vim might like to know just what it
> > > > is that the editor needs to do to provide "support".
> > >
> > > comp.editors is the place to discuss editor settins.
> > > for all editors.  except maybe for the editor in
> > > emacs os - which has its own newsgroup hierarchy.
> >
> > What formatting is required for mutt to
> > be able to send format=flowed emails?
> 
> mutt does no formatting to text - the editor does.
> and the name of the format is "format=flowed".
>
> the only difference between a normal message
> and a f=f message is in the header:
> 
> 1 Content-Type: text/plain; charset="iso-8859-1"
> 2 Content-Type: text/plain; charset="iso-8859-1"; format="flowed".

OK - that's all I realy wanted to know.

Also, the fact that in a f=f message line breaks within paragraphs
have a space before the CR, whereas between paragraphs there is just a
CR.

> all mutt needs to add to the header is the part with
> 'format="flowed"'.  and you'll find in the manual
> that setting the variable text_flowed does that.
>
> mutt is only *one* of the many programs
> involved with sending data of a special kind.

Yup, I understand that. I know it's not specifically a mutt issue, but
given the generally knowledgeable people that use mutt, it seems a
reasonable place to ask. Some debate as to whether format=flowed is
worthwhile would have been interesting.

James.