Encoding of received message in 60.6.1
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: om, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0
Steps to reproduce:
I'm not the sender of the bugged messages, but the receiver.
The messages are sent in French, with accented (non-ASCII) characters. It worked with Thunderbird/60.5.0 and it stopped working with 60.6.1 without any configuration change.
Actual results:
Each accented character is replaced with the sequence � which is the Latin1 mis-coding of the UTF-8 replacement character.
I note that the Content-Type charset is windows-1252 (Windows Latin1) instead of UTF-8, and maybe a workaround would be to force sending in UTF-8. I will ask the sender to test this, but we communicate only by e-mail so I don't know when the test will be done.
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Expected results:
That « é » weren't replaced with « � ».
|
Reporter | |
Comment 1•6 years ago
|
||
Oups! I forgot to tell the complete User-Agent, which is on Windows (I am on Linux).
Encoding was correct with:
%%%%%%%%%%
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.5.0
%%%%%%%%%%
Encoding is bad with:
%%%%%%%%%%
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.6.1
%%%%%%%%%%
|
||
Updated•6 years ago
|
|
||
Comment 2•6 years ago
|
||
I don't think there is anything that can be done. If the sender uses Yahoo or a related service and sends encoded in windows-1252 (Western), then Yahoo messes up every high bit character and puts a UTF-8 replacement character in (since it ignores the encoding). The UTF-8 replacement character interpreted as windows-1252 gives what your seeing.
That's been an issue for years. See bug 1435903 comment #15, bug 1435903 comment #29, bug 1435903 comment #31.
To my knowledge, Yahoo never fixed the issue, but in the meantime they shut down their support forums.
I'm duplicating this to bug 1435903 so we keep it all together.
|
|
Reporter | |
Comment 3•6 years ago
|
||
You are right, she is using yahoo. I told her how to encode using UTF-8, and now all is OK. Thank you!
Description
•