Why Outlook email messages show unreadable characters

When you receive a new email in Outlook, you may see unreadable characters in the email message body. This issue could be caused by one of the following reasons on Outlook client side:

The email you received is converted to plain text format or a different encoding by a virus scanner. 

This always happens when you are using characters (Such as apostrophes, double quotes, dashes, and ellipsis) supported by the "Smart Quotes" feature. When the email you received is converted to plain text format or a different encoding by a virus scanner, the character is converted from the ASCII character to a Unicode character, which is not supported on the recipients side.

To prevent this issue from happening, we can turn off the Smart Quotes Feature in Outlook:

1. Open Outlook 2013.

2. Click File > Options > Mail.

3. Click Spelling and AutoCorrect button.

4. In the Editor Options window, click AutoCorrect Options button to open the AutoCorrect dialog.

5. Click AutoFormat tab, and then clear the check box before Straight quotes with smart quotes under Replace heading.

6. Click OK.

The issue may be related to font substitution when a change is made to the Web Options in Microsoft Word. 

If a change is made to the Web Options in Microsoft Word, registry data under the following key may be configured incorrectly:

HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Word\Internet\Fonts

This problem has been seen to occur when the Latin string value under the \Fonts key was empty (no value). 

We can check the Web Options setting in Word via:

1. Start Word.

2. Go to File > Options > Advanced.

3. Scroll down to the General section, click Web Options button.

4. Switch to Font tab.

To resolve the problem, we need to delete the \Fonts registry key. To do this, please follow:

1. Exit Word.

2. Press Windows key + R to open the Run command, type regedit and press Enter.

3. Navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Word\Internet\Fonts

4. Right-click the Font key and select Delete.

5. Click Yes and exit Registry Editor.

The sender used an e-mail program that did not mark messages with a language encoding (character set), or marked messages with an incorrect encoding setting.

In this case, we will see unreadable characters when we open the received message in our Outlook. For example, European regional characters (like German) require UTF-8 encoding protocol. So if the encoding in your environment is set to ASCII, the regional characters will not be available. 

To resolve this issue, we need to change the encoding in Outlook to which will display your message correctly.

1. Double-click to open the message you received.

2. Click Actions button in the Move group under Message tab.

3. Click Other Actions > Encoding.

4. Click More and select the correct encoding setting for the email.

5. After you finish reading the message, close the message, and click Yes button to save changes to the message.

When we send an email with Outlook, we can set Outlook to automatically select encoding for outgoing email messages to increase the possibility that the recipient receiving the message will see all the characters rendered properly, even if they run older e-mail programs. By default, Outlook 2013 will automatically select an optimal encoding for outgoing e-mail messages. We can change the settings here in Outlook 2013: File > Options > Advanced > International Options section.

Something you may need to know when you set the encoding settings:

* The Unicode (UTF-8) character enables the complete range of characters on all computers. Its the official IANA code for the UTF-8 character encoding.

* Western European (ISO) and Western European (Windows) character set can be read by almost all computers.

* If you are using a language other than English, you must choose the correct character set for that language, or the characters you need will not be displayed correctly.

If you have any comments on this article, please feel free to post

April 13th, 2015 2:05am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics