Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Text encoding is wrong in incoming emails

  • 1 baphendule
  • 1 inale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu Renar

more options

Good day, Last week I updated Thunderbird to version 78.10.1 and since then Text Encoding in all of my incoming letters is messed up. Every time I receive a letter, I have to do "View > Text Encoding" and try out 3, sometimes 4 different options before I see the email without hieroglyphs. Whenever I switch to a different letter, I have to do the same thing with every letter, even with the ones I read a second ago. Whenever I need to print out an incoming letter, encoding is messed up in Print Preview. I receive letters in 4 different languages - English, Russian, Latvian and sometimes German. Due to this reason setting one type of Text Encoding option won't fix the issue. In this regard I have two questions:

  1. 1 Why all of a sudden text encoding messed up after an update?
  2. 2 How do I fix it?
Good day, Last week I updated Thunderbird to version 78.10.1 and since then Text Encoding in all of my incoming letters is messed up. Every time I receive a letter, I have to do "View > Text Encoding" and try out 3, sometimes 4 different options before I see the email without hieroglyphs. Whenever I switch to a different letter, I have to do the same thing with every letter, even with the ones I read a second ago. Whenever I need to print out an incoming letter, encoding is messed up in Print Preview. I receive letters in 4 different languages - English, Russian, Latvian and sometimes German. Due to this reason setting one type of Text Encoding option won't fix the issue. In this regard I have two questions: # 1 Why all of a sudden text encoding messed up after an update? # 2 How do I fix it?

All Replies (1)

more options

Just got an update to 78.10.2 and nothing changed - problem still persists.