Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

How to tell TB to use the char set befined by the incomming message

  • 2 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 4 gösterim
  • Son yanıtı yazan: sfhowes

juerg_b69
juerg_b69
more options

The char set of my TB-client is set to utf-8. Sometimes incoming mails use char set="iso-8859-1", mostly mails sent from MS-Outlook! i.e. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0055_01D5B5C6.1F3AD8C0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdW1vWIp34TBbueUQn27zs3NUv1eDw== Content-Language: de-ch

This is a multipart message in MIME format.

=_NextPart_000_0055_01D5B5C6.1F3AD8C0

Content-Type: multipart/alternative; boundary="----=_NextPart_001_0056_01D5B5C6.1F3AFFD0"


=_NextPart_001_0056_01D5B5C6.1F3AFFD0

Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

In all those cases non ASCII chars are represented as '?' question mark which makes reading of the mail difficult! The raw text view of the mail shows for instance: 'ü' as '=FC' or 'ö' as '=F6' How and where to tell TB to use the char set defined by the incoming mail to represent such characters correctly? I intend to continue to use utf-8 for outgoing mails. But incoming mails should use the char set of the sender and maybe covert correctly to utf-8 on reply!

The char set of my TB-client is set to utf-8. Sometimes incoming mails use char set="iso-8859-1", mostly mails sent from MS-Outlook! i.e. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0055_01D5B5C6.1F3AD8C0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdW1vWIp34TBbueUQn27zs3NUv1eDw== Content-Language: de-ch This is a multipart message in MIME format. ------=_NextPart_000_0055_01D5B5C6.1F3AD8C0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0056_01D5B5C6.1F3AFFD0" ------=_NextPart_001_0056_01D5B5C6.1F3AFFD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In all those cases non ASCII chars are represented as '?' question mark which makes reading of the mail difficult! The raw text view of the mail shows for instance: 'ü' as '=FC' or 'ö' as '=F6' How and where to tell TB to use the char set defined by the incoming mail to represent such characters correctly? I intend to continue to use utf-8 for outgoing mails. But incoming mails should use the char set of the sender and maybe covert correctly to utf-8 on reply!

Tüm Yanıtlar (2)

Matt
Matt
  • Top 25 Contributor
  • Moderator
more options

Is Thunderbird not using the charset? View menu > text encoding

All I can really do is refer you to this bug https://bugzilla.mozilla.org/show_bug.cgi?id=936466 which appears from my reading to merge various character sets, but I really don't understand the logic used.

sfhowes
sfhowes
  • Top 10 Contributor
more options

If you are seeing question marks ? in place of non-ASCII characters, that could be caused by a bug with TB senders sending through AOL or Yahoo servers. There is a workaround to correct the display at your end, but it requires the senders to make a simple change. Is a Yahoo, or any of its varieties, sending account a common factor in these messages?