搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Encoding works for message subject but not for message text

  • 5 回覆
  • 1 有這個問題
  • 6 次檢視
  • 最近回覆由 orionnebula

more options

Hi, I'm using ubuntu 14.04 32-bit (german setup). I installed from scratch: Thunderbird 52.6.0 32-bit

I changed some settings in TB, but none related to encoding, thus using UTF-8.

I encounter the following problem sending an email that contains german special letters (e.g äöü): The message subject e.g. "test äöü" is transmitted correctly, but the message body "test äöü" arrives at the receiver as "test ???". This can be tested by myself by including my address CC.

Hi, I'm using ubuntu 14.04 32-bit (german setup). I installed from scratch: Thunderbird 52.6.0 32-bit I changed some settings in TB, but none related to encoding, thus using UTF-8. I encounter the following problem sending an email that contains german special letters (e.g äöü): The message subject e.g. "test äöü" is transmitted correctly, but the message body "test äöü" arrives at the receiver as "test ???". This can be tested by myself by including my address CC.

被選擇的解決方法

Matt, maybe your were right. Now it's working as it should (using "sans-serif"). Perhaps a reboot of the system (or some other change ?) did it. Thanks for your contributions.

從原來的回覆中察看解決方案 👍 0

所有回覆 (5)

more options

What are your Fonts settings? Please post a screenshot of your Fonts & Encodings window.

more options

Hi, please find attached the requested screenshot.

more options

Arial is not a unicode font. Change it to a font that is, or download a unicode version names Arial unicode MS and use that instead.

more options

Sorry, but Wikipedia thinks Arial is a unicode font, please see https://en.wikipedia.org/wiki/Unicode_font#List_of_Unicode_fonts

Be that as it may. The problem persists even if I use "sans serif" which is the installation default font.

more options

選擇的解決方法

Matt, maybe your were right. Now it's working as it should (using "sans-serif"). Perhaps a reboot of the system (or some other change ?) did it. Thanks for your contributions.