6 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] No blank lines in mes...
FromSent OnAttachments
wr...@cwru.eduNov 7, 2004 12:47 am 
Sam VarshavchikNov 7, 2004 7:42 am 
wr...@cwru.eduNov 7, 2004 1:46 pm 
Sam VarshavchikNov 7, 2004 2:12 pm 
Warren VolzNov 7, 2004 6:56 pm 
Sam VarshavchikNov 8, 2004 4:06 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [sqwebmail] No blank lines in messagesActions...
From:wr...@cwru.edu (wr@cwru.edu)
Date:Nov 7, 2004 1:46:54 pm
List:net.sourceforge.lists.courier-sqwebmail

I played with some messages to see if Thunderbird is following the spec and from what I can tell it is. The problem is in sqwebmail's choice of return when a blank line follows a paragraph. If the goal is to make the paragraph display exactly like the user typed it in, the final soft return that sqwebmail adds should be a hard return. Perhaps sqwebmail is translating two hard returns into a soft and hard return?

For the following: (* indicates soft return ie: space followed by CRLF, # indicates hard return ie: CRLF)

Example of how sqwebmail encodes a paragraph now:

This is some random text that is# part of a paragraph.* # Here is some more random text that# is also part of a paragraph.* # Junk.#

Example that displays the same way the user entered the text:

This is some random text that is# part of a paragraph.# # Here is some more random text that# is also part of a paragraph.#

-Warren

On Nov 7, 2004, at 8:42 AM, Sam Varshavchik wrote:

sqwebmail follows the RFC 2646 specification for flowed format text.

Mozilla/Thunderbird support for RFC 2646 is broken. I opened a bug about that several years ago, but I guess whoever looked at the bug was too stupid to understand the plain language of RFC 2646, and Mozilla/Thunderbird thus remains broken to this day.

The "extra space" you are referring to is specified by RFC 2646. See section 4.8.