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

How can I get View/Text Encoding/Unicode setting to stay set?

  • 5 replies
  • 4 have this problem
  • 92 views
  • Last reply by Tom Cluster

more options

I'm using Thunderbird 52.3.0 32bit on an unpdated Win7 64bit OS computer. I often get emails which have non-ascII characters in them. Per suggestions from the TB forum, I select View/Text Encoding/Unicode and I can read this message without the garbage characters. I go to the next message and the Unicode is not longer set--it returns to Western.

My Tools/Options/Display Fonts & Colors/Advanced settings are: Proportional Sans Serif, the next 43 choices are Arial. Both Font control choices are enabled. Both Text Encoding (outgoing & Incoming) are set to Unicode (UTF-8), I've tried setting both to Western (ISO-8859-1 and it makes no difference. Also--Auto is set to Off in the box above the Unicode radio button.

It does the same thing when I run in Safe Mode. I may have made a change to config when I asked a for a suggestion in the TB forum, but I have no idea what might have been changed years ago. Could it be one of those changes might have affected this?

I notice there are other questions with the exact problem here using a Linux vs Windows, No answers to them tho.

This is the thread with the help and my answers on the TB forum: http://forums.mozillazine.org/viewtopic.php?f=39&t=3033756

Thanks for any help, Ron

I'm using Thunderbird 52.3.0 32bit on an unpdated Win7 64bit OS computer. I often get emails which have non-ascII characters in them. Per suggestions from the TB forum, I select View/Text Encoding/Unicode and I can read this message without the garbage characters. I go to the next message and the Unicode is not longer set--it returns to Western. My Tools/Options/Display Fonts & Colors/Advanced settings are: Proportional Sans Serif, the next 43 choices are Arial. Both Font control choices are enabled. Both Text Encoding (outgoing & Incoming) are set to Unicode (UTF-8), I've tried setting both to Western (ISO-8859-1 and it makes no difference. Also--Auto is set to Off in the box above the Unicode radio button. It does the same thing when I run in Safe Mode. I may have made a change to config when I asked a for a suggestion in the TB forum, but I have no idea what might have been changed years ago. Could it be one of those changes might have affected this? I notice there are other questions with the exact problem here using a Linux vs Windows, No answers to them tho. This is the thread with the help and my answers on the TB forum: http://forums.mozillazine.org/viewtopic.php?f=39&t=3033756 Thanks for any help, Ron

All Replies (5)

more options

Solved After I posted this--I did a search in TB support forum and found an untried suggestion: Right click Inbox, choose Properties and change Fallback Text Encoding to Unicode. Now when I look at at View/Text Encoding--Unicode is always selected.

I hope this helps others, Ron

more options

If I forward a message that I originally created (it was sent to someone else who responded back to me, and then I forward it to someone else) multiple spaces show up in a peculiar way. I've seen discussions about Western versus Unicode. I don't completely understand these postings, but I get the feeling that specifying Western fixes this problem, but the problem is that there doesn't appear to be a global setting that forces Western on every message. The Alt-V "Text Encoding" option only appears when you're looking at a particular message. I've seen the post about right clicking on the inbox and looking at "Fallback Text Encoding" but there are two "Western" options - ISO-8859-1 and Windows-1252. Can someone explain why this is a problem only when I forward mail? Maybe if I understand that I'd be more able to understand the issues involved. Thank you.

more options

I am the op. I had problem with the same issue. My "Helpful Reply" fixed the issue for me. But as mentioned--I used Unicode--NOT Western.

more options

Uniode is the defacto standard for email transfer. That is because it has so many character sets built in someone included Egyptian hieroglyphs, Japanese and Traditional Chinese among others.

Unfortunately some vendors and some users have not kept with the times and still use what are best described as legacy text encoding. Unfortunately Microsoft and IBM both fell into this category until recently. So we have all the die hard Eudora fans out there, and other folk using other "legacy" email programs that just do not to text properly etc. The result is you have to, on occasion, use a manual selection of text encoding to fix the problems generated by defective software sending you mail.

.

more options

Thank you. I specified Unicode in the "Fallback text encoding" field and I'm unable to re-create the problem, so apparently it fixed it. I don't totally understand why, but that's okay! Thanks again!