Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Special Characters on received emails not displaying correctly after update to 78

  • 1 wótegrono
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót fosforo1313

fosforo1313
fosforo1313
more options

Hi

Just noticed that emails with special characters such as â ã ç é and so on, now display as � after update to 78.

If i go to (in the main window) View>Text Encoding, Unicode is selected. If i change it to Western, then the special characters in the selected email displays correctly.

If i select another email, when i go back to the problem email, it no longer displays correctly, and Unicode is selected again.

This happens to emails received before the update to 78 too.

I have changing options in Options>General>Language & Appearance>Fonts & Colors>Advanced and for incoming emails the selected option is Western (ISO-8859-1), and changing this option had no visible results.

Thanks in advance

Hi Just noticed that emails with special characters such as â ã ç é and so on, now display as � after update to 78. If i go to (in the main window) View>Text Encoding, Unicode is selected. If i change it to Western, then the special characters in the selected email displays correctly. If i select another email, when i go back to the problem email, it no longer displays correctly, and Unicode is selected again. This happens to emails received before the update to 78 too. I have changing options in Options>General>Language & Appearance>Fonts & Colors>Advanced and for incoming emails the selected option is Western (ISO-8859-1), and changing this option had no visible results. Thanks in advance

Wšykne wótegrona (1)

fosforo1313
fosforo1313 Pšašaŕ
more options

Problem still exists after 78.4.3