Also, apart from my previous comment, I want to raise an additional one that is closely related to it. When I set my "Your name:" in "Account settings" to
Borovička, Jaroslav
i.e. I'm using iso-8859-2 charset, the header actually looks the following way:
Note the two pairs of =22 encoded characters. This are quotation mark signs added by the Thunderbird client into the header. Such a header should be properly decoded and !displayed! as
"Borovička, Jaroslav"
i.e. the recipent should see two extra quotation marks, which I have not specified as my full name ("Your name:"). In fact, many clients behave in this way, and they correctly display the quotation marks after these have been incorrectly added by Thunderbird. It is the same misunderstanding of RFC 2047 as before.
The correct way how the header should look like is
I guess that this whole error was originally not a bug, but a misunderstanding of RFC 2047. I post this comment here because I believe that these issues should be solved hand-in-hand. Again, I would like to urge the responsible person to deal with this, since more and more people are using non-ASCII characters in their full names.
Also, apart from my previous comment, I want to raise an additional one that is closely related to it. When I set my "Your name:" in "Account settings" to
Borovička, Jaroslav
i.e. I'm using iso-8859-2 charset, the header actually looks the following way:
From: =?ISO-8859- 2?Q?=22Borovi= E8ka=2C_ Jaroslav= 22?= <email address hidden>
Note the two pairs of =22 encoded characters. This are quotation mark signs added by the Thunderbird client into the header. Such a header should be properly decoded and !displayed! as
"Borovička, Jaroslav"
i.e. the recipent should see two extra quotation marks, which I have not specified as my full name ("Your name:"). In fact, many clients behave in this way, and they correctly display the quotation marks after these have been incorrectly added by Thunderbird. It is the same misunderstanding of RFC 2047 as before.
The correct way how the header should look like is
From: =?ISO-8859- 2?Q?Borovi= E8ka=2C_ Jaroslav? = <email address hidden>
I guess that this whole error was originally not a bug, but a misunderstanding of RFC 2047. I post this comment here because I believe that these issues should be solved hand-in-hand. Again, I would like to urge the responsible person to deal with this, since more and more people are using non-ASCII characters in their full names.