Fixed in CVS and 3.0.6.

Attached is a proposed patch to file framework/Text_Flowed/Flowed.php.

If you compose message in pine it leaves the message as is and does 
not try to remove any extra CRLFs or whitespace that might be in the 
message.



What I understood from reading the RFC 2646 is that you should not try 
to remove any extra CRLFs or whitespace when and while the message is 
being composed or sent. But you may remove the soft line breaks when 
you show the message to the user. I understood that the soft line 
break is defined as 1*WS CRLF, and if this is followed by more CRLFs 
or whitespace then you should leave those extra CRLFs and whitespace 
as is.

Known issue - I've been waiting to finish the namespace mess before 
tackling this.  Ben Chavet previously submitted the following to dev@:



I wondered how this worked, now it makes sense.  Is there anything in

the spec that would handle a line ending with a space followed like a

blank line?  Something like:



End of paragraph._



next paragraph



I've found that this will end up like "End of paragraph. next

paragraph" even though there is a line that doesn not end with a space

between the two.  Bug, or feature?



--Ben

In the RFC 2646 the soft line break in flowed formatted test is 
defined as 1*SP CRLF. But in Imp if I write something like: 
"lines_of_text 1*SP CRLF CRLF CRLF CRLF more_lines_of_text" then Imp 
optimizes these lines  to something like this: lines_of_text 1*SP 
more_lines_of_text. In effect you lose any paragraph separation you 
might have done.