German umlauts, UTF-8 declaration missing?
Posted: Sat Dec 26, 2020 8:04 am
I recently purchased OE classic (OEC) running on Win10 which is quite similar to the old Outlook Express. I know that other options do exist, but this one is most liked by my wife. She does not want to use MS Outlook, Firebird or other clients. Needless to explain in more detail
Living in a German speaking area, we use German umlauts: äöüßÄÖÜ
These umlauts are not displayed correctly in certain situations. PopPeeper is set to create messages in "quoted printable".
1) Umlauts are displayed wrongly in OEC, in emails received via Microsoft exchange server and are replaced by black strange characters, when it is not a multi-part message. The change of sending a pure text mail without attachments to Base64, automatic (QP) or none, does not change anything.
2) As already mentioned, when attaching a file, PopPeeper creates a multi-part message and all is fine.
I contacted the OEC developer and they say that the declaration UTF-8 was missing inside the email. They further say that I was probably using an obsolete email client which would not respect the standardisation rules. Please see attached files.
Is there any proven advice who is right or wrong? More, importantly, is there any chance to force PopPeeper to use UTF-8 or to declare that it's UTF-8, or to force PopPeeper to create a multi-part message even if there is no attachment? For example MS-Outlook always creates a multi-part message regardless of an attachment.
Btw, the setting of localisation (region settings) inside Windows, stated in previous contributions to the umlaut subject has no influence on this.
Any help will be very welcome.
Peter
Living in a German speaking area, we use German umlauts: äöüßÄÖÜ
These umlauts are not displayed correctly in certain situations. PopPeeper is set to create messages in "quoted printable".
1) Umlauts are displayed wrongly in OEC, in emails received via Microsoft exchange server and are replaced by black strange characters, when it is not a multi-part message. The change of sending a pure text mail without attachments to Base64, automatic (QP) or none, does not change anything.
2) As already mentioned, when attaching a file, PopPeeper creates a multi-part message and all is fine.
I contacted the OEC developer and they say that the declaration UTF-8 was missing inside the email. They further say that I was probably using an obsolete email client which would not respect the standardisation rules. Please see attached files.
Is there any proven advice who is right or wrong? More, importantly, is there any chance to force PopPeeper to use UTF-8 or to declare that it's UTF-8, or to force PopPeeper to create a multi-part message even if there is no attachment? For example MS-Outlook always creates a multi-part message regardless of an attachment.
Btw, the setting of localisation (region settings) inside Windows, stated in previous contributions to the umlaut subject has no influence on this.
Any help will be very welcome.
Peter