NoOp wrote:
On 09/25/2011 08:32 PM, Mike Easter wrote:
NoOp wrote:
Mike Easter wrote:
I also have (just now) Tb 3.1.15 on an XP system and Tb 7.0 on a Mint 11
system. I just tested 3.1.15 and it *still* has the 'deficiency' of
which I speak, namely stripping the trailing spaces on quoted material.
Why do you keep asking this when you are posting with:
User-Agent: Thunderbird 2.0.0.24 (X11/20100623)
I'm trying to talk about SeaMonkey's problem here. I only mention that
the same problem exists in Tb3 but not other Tbirds because I tho't that
information might help someone in SeaMonkey's development.
Any difference on your side using your newly updated TB 3?
As I said above, the problem still exists in Tb 3.1.15, but I don't
really want to talk about that here.
Yet you are posting with TB 2.x and TB is now at 6.x.
I also am not interested in talking about it in tbird support because
the problem has been resolved in more current v/s of Tbird.
I see.
If I were going to talk about anything related to f=f in Tb support, it
would be about 'upgrading' the rewrap function to result in f=f lines
instead of rewrap stripping existing trailing spaces.
That improvement would be a good thing for SM too, so let us stay with
SM issues here.
OK. Let's do that. My post that you responed to was from:
Build identifier: Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20110923
Firefox/7.0 SeaMonkey/2.4
and as I said I posted it with:
And now with both set to:
mailnews.display.disable_format_flowed_support;true
mailnews.send_plaintext_flowed;false
So would you care to detail?
BTW: this reply is using:
mailnews.display.disable_format_flowed_support;true
mailnews.send_plaintext_flowed;false
I'm bottom posting untrimmed here so that I can leave intact how your SM
2.4 handled the EOLs of the quoted material above.
All of the lines which I posted above had trailing spaces and would flow
and did flow when read in my original post.
When your SM quoted those paragraphs of mine, it stripped all of the
trailing spaces causing them to no longer flow.
That is the problem. Your SM v. and all other SM v/s strip existing
trailing spaces and so they 'de-f=f' the quoted material which was
previously 'good' f=f.
Once the trailing spaces have been stripped, the lines are no longer f=f
and they never will be f=f when they are later cited, because there are
no f=f editors which can restore the trailing spaces to lines where they
have been stripped.
I explained earlier how you can examine a post for the presence or
absence of trailing spaces at the EOLs within a par. You use ctrl-U and
examine the message source and put your cursor at the EOL. You can see
the presence or absence of a space.
As it happens, none of your paragraphs above are/were long enough to
show the flowing characteristic for your paragraphs, but previously my
longer paragraphs flowed in the 'original' until your SM stripped their
trailing spaces.
--
Mike Easter
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
