I have 2.0.0.0 (20070326) Win-EN version, and I can confirm both a) and b) from comment #70 when viewing e-mails that have been stored on the local database (using POP3) with previous versions of Thunderbird.
However, when I receive a new email now with the new version of Thunderbird, everything seems to work fine.
I suspect that old emails have been already incorrectly stored in the local database. When I look at the header of an old email that causes these problems, I see:
The headers are now being stored with quoted ISO strings, and Thunderbird's behavior is correct (even when replying). However, notice that in the first case, the comma is encoded as =2C, Unfortunately, I was not able to reproduce this to check that Thunderbird behaves correctly even in cases when commas are encoded in such a way in freshly received emails. I think this should be done before marking the problem as solved, just in case.
Regarding c) from comment #70, I cannot confirm the described behavior. Using the new version of Thunderbird to reply to old emails stored with previous versions of Thunderbird still produces the same buggy behavior as described in many previous comments (not the one from comment #70). Replying to newly received emails is correct.
(In reply to comment #74)
> I don't see either issue in 2.0 final.
I have 2.0.0.0 (20070326) Win-EN version, and I can confirm both a) and b) from comment #70 when viewing e-mails that have been stored on the local database (using POP3) with previous versions of Thunderbird.
However, when I receive a new email now with the new version of Thunderbird, everything seems to work fine.
I suspect that old emails have been already incorrectly stored in the local database. When I look at the header of an old email that causes these problems, I see:
From: =?iso-8859- 2?Q?Kub= EDkov=E1= 2C_VF-CZ? = <email address hidden>
However, the headers of freshly received emails contain
From: "=?ISO- 8859-2? Q?Borovi= E8ka,_Jaroslav? =" <email address hidden>
The headers are now being stored with quoted ISO strings, and Thunderbird's behavior is correct (even when replying). However, notice that in the first case, the comma is encoded as =2C, Unfortunately, I was not able to reproduce this to check that Thunderbird behaves correctly even in cases when commas are encoded in such a way in freshly received emails. I think this should be done before marking the problem as solved, just in case.
Regarding c) from comment #70, I cannot confirm the described behavior. Using the new version of Thunderbird to reply to old emails stored with previous versions of Thunderbird still produces the same buggy behavior as described in many previous comments (not the one from comment #70). Replying to newly received emails is correct.