Avatar for Username

Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

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

  • 2 válasz
  • 1 embernek van ilyen problémája
  • 4 megtekintés
  • Utolsó üzenet ettől: 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!

Összes válasz (2)

Matt
Matt
  • Moderator
  • Top 10 Contributor
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?