Version: unspecified (using Devel) OS: Linux The user selects an encoding for sending an email but a dialogue warn him that another encoding will be used instead. So the mail is not properly readable for the recipient. Reproducible: Always Steps to Reproduce: - Launch Kmail - Click on 'New' - Fill in the recipient (yourself), the subject and enter a few letters using accents in the text editor (ex: ùçàèèèèééééâîùù) - Click on 'send' - Select the mail in your sent-mail folder - Go to View menu/Set Encoding and select Chinese traditional (Big 5) - Select the Chinese characters and copy them into a new email - Enter a recipient (yourself) and a subject - Go to Options menu/Encoding and select Chinese traditional (Big 5) - Click on 'Send' Actual Results: A warning message appears saying:'Encoding the message with ISO-8859-1 will lose some characters. Do you want to continue?' You have to click 'Lose Characters' to send the email so when it arrives the Chinese characters are replaced by ?s. Trunk, Svn Rev 1129830 Expected Results: The selected encoding should be remembered. The email should contain the Chinese characters.
Indeed, KMail seems to ignore the encoding selection here.
I can't reproduce this, after pasting the chinese characters into the new message, and selecting Big5 as the encoding, the mail sends fine. generated mail has Big5 encoding and is decoded properly
SVN commit 1134159 by lfranchi: Properly set the right charset. If the user selects a charset, use that one first. If Force Charset is on, use that as a fallback if the user hasn't explicitly chosen another one. BUG: 238632 M +3 -3 kmcomposewin.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1134159
It is corrected now. The selected encoding works when sending emails now. Note: in an email containing two types of encoding (ex: Chinese characters and Swedish characters like ä, not both of them can be visible. The user has to choose which one are the most important. The less important one ends up being replaced by a '?' after a warning message appears: 'Encoding the message with EncodingSelected will lose some characters. Do you want to continue?' Trunk, Svn Rev 1141839