Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Can't read some email contents, I think it comes from ISO-2022-KR encoding problem

  • 1 odgovor
  • 5 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od Wayne Mery

ds1rbi
ds1rbi
more options

I can't read korean(even other languages) mail contents as like attached images. It has been occoured from when I upgrade to version 38.0.1. Is there somewhat changed?

If I trun to view mode to source of that email message, there shows like below at the header,

--=_alternative 00182EAD49257E6C_= Content-Type: text/plain; charset="ISO-2022-KR"

I think the errors comes from that encoding method 'ISO-2022-KR'.

because other email that has no problem, shows like below,

Content-Transfer-Encoding: base64 Content-type: text/plain; charset=UTF-8

How can I read emails that has problem?

I can't read korean(even other languages) mail contents as like attached images. It has been occoured from when I upgrade to version 38.0.1. Is there somewhat changed? If I trun to view mode to source of that email message, there shows like below at the header, --=_alternative 00182EAD49257E6C_= Content-Type: text/plain; charset="ISO-2022-KR" I think the errors comes from that encoding method 'ISO-2022-KR'. because other email that has no problem, shows like below, Content-Transfer-Encoding: base64 Content-type: text/plain; charset=UTF-8 How can I read emails that has problem?
Priložene slike ekrana

Izmjenjeno od ds1rbi

Izabrano rješenje

Please submit a bug report at https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird and attach to the bug report a sample message saved to an .eml file

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

Odabrano rješenje

Please submit a bug report at https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird and attach to the bug report a sample message saved to an .eml file