Summary: | Characters not included in charset are replaced by ? (question mark) | ||
---|---|---|---|
Product: | knode | Reporter: | Alexander Skwar <alexander> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Alexander Skwar
2005-05-03 18:21:56 UTC
Hi, I think KMail's solution is the best. (Look at Kmail -> settings -> Composer -> Charset tab.) There you can have a list of encodings, and KMail checks it topdown for every outgoing mail till it finds an encoding which contains all needed letters. As an example my list is like this: us-ascii // "Bla bla." iso-8859-1 // "Blä blöü." iso-8859-15 // "Blä blöü with €." utf-8 So if I don't have Umlaute in my mail, the charset will be us-ascii, with Umlaute it'll be iso-8859-1, if I use the Euro-sign it'll be iso-8859-15 and if I suddenly start writing chinese, well, than it will be utf-8. Regards, Tassilo Yes, that sounds like a good solution. What happens in KMail, if you respond to iso-8859-15 Mail and use only us-ascii characters? Will the mail be encoded in iso-8859-15? That is exactly what SHOULD happen, IMO. BTW: The KMail is solution your proposing here, is also what Thunderbird/Mozilla is using. The answer to a iso-8859-15 encoded message will also be encoded in iso-8859-15, even if it contains no letters requiring iso-8859-15. *** This bug has been confirmed by popular vote. *** I'm curious - will eventually something be done about this bug? I mean, it just recently celebrated it's 2nd birthday... Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. |