搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Encoding works for message subject but not for message text

  • 5 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 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.