Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

How to change default text encoding from Western to Unicode

  • 1 reply
  • 4 have this problem
  • 6 views
  • Last reply by Matt

Greg Couch
Greg Couch
more options

In mail that I'm receiving, the characters are displayed incorrectly. When I go the View / Text Encoding menu, it show that the encoding is Western. When I change the encoding to Unicode, the message is display correctly. I have to do this for practically every message. Looking the the email source, it has in it "Content-Type: text/plain; charset=utf-8", so I would expect it to be display as UTF-8 instead of Western. I tried changing the default by using the Options dialog's Formatting tab's Advanced dialog to set the Text Encoding for both Incoming Mail and Outgoing Mail to Unicode (UTF-8). But that has no effect. FYI, I'm running on Windows 10.

In mail that I'm receiving, the characters are displayed incorrectly. When I go the View / Text Encoding menu, it show that the encoding is Western. When I change the encoding to Unicode, the message is display correctly. I have to do this for practically every message. Looking the the email source, it has in it "Content-Type: text/plain; charset=utf-8", so I would expect it to be display as UTF-8 instead of Western. I tried changing the default by using the Options dialog's Formatting tab's Advanced dialog to set the Text Encoding for both Incoming Mail and Outgoing Mail to Unicode (UTF-8). But that has no effect. FYI, I'm running on Windows 10.

All Replies (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

The issue I see is that encoding appears so many times. Usually there is one in the header, then the body has it specified again. Is there any commonality in the source of your problem emails? Yahoo is known to have broken servers for instance. But it should not be the cause of this particular issue.