為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

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

了解更多

gibberish font when replying or forwarding

  • 1 回覆
  • 1 有這個問題
  • 6 次檢視
  • 最近回覆由 Toad-Hall

more options

Whenever a message is replied to or forwarded, the recipient gets gibberish characters in the prior messages on that thread. Like this: ��������������� J. These characters appear randomly and makes reading the thread nearly impossible. Thanks for any help! Graham

Whenever a message is replied to or forwarded, the recipient gets gibberish characters in the prior messages on that thread. Like this: ��������������� J. These characters appear randomly and makes reading the thread nearly impossible. Thanks for any help! Graham

所有回覆 (1)

more options

What server are you sending via eg: yahoo, comcast, att

Sadly some US ISP's like AT&T and Bellsouth have started *corrupting* their customers' e-mail.

If the customer sends in windows-1252 and includes for example special punctuation characters or a non-break space xA0, the ISP doesn't correctly interpret the the message as windows-1252 but as UTF-8. In UTF-8, xA0 is not valid and gets replaced by the so-called replacement character, � (0xEF 0xBF 0xBD).

Since the e-mail is still windows-1252 encoded, the recipient's client displays �.

Try this first: Set preference mail.strictly_mime to true.

  • Menu app icon > Options > Options >Advanced > 'General' tab
  • click on 'Config Editor' button - it will say be careful :)
  • in top search type : mime
  • look for this line: mail.strictly_mime
  • If set to false, double click on line to toggle value to true.
  • close window - top x

If still a problem then try: If still using version 68

  • Menu app icon > Options > Options > Display > 'Formatting' tab
  • click on 'Advanced' to see encoding
  • Set 'Unicode' on both Outgoing and Incoming
  • Select Check box "When possible, use the default text encoding in replies"