On Thu, 2007-10-18 at 15:10 +0200, Bernd Markgraf wrote: > > Trying with lastedt Evolution 2.20, it behaves different from your > > description. > > My locale is C. I change charset to UTF-8 on preference and then restart > > evolution. Charset is kept as my setting, i.e. UTF-8. So I think the > > problem you raised has been fixed. > Evolution kept my settings as well... No problem at this point. The > message you sent now indeed specified the character set: > Content-type: text/plain; format=flowed; charset=ISO-8859-1 > > So if you have set it tp UTF-8 something went wrong again. OR evolution > might have used the character set from the message you replied to (I had > locale de_DE / iso-8859-1 set at the time of writing that mail). > Could you check if the character set appears in the header with the > value you choose when you write yourself a new message?
First of all, please ignore my last two mail becase it was written by Thunderbird rather than Evolution. I test evolution 2.20 again. locale: C Preference setting: UTF-8 - Sent a mail contain Chinese Characters to myself, message head showed below Subject: testing Sender: Simon.Zheng at Sun.COM To: "simon.zheng" <Simon.Zheng at Sun.COM> Message-id: <1192790762.11330.19.camel at goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.12.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 8BIT - Then replied to myself again, message head still specified UTF-8 encoding. Subject: Re: testing In-reply-to: <1192790762.11330.19.camel at goaltender> Sender: Simon.Zheng at Sun.COM To: "simon.zheng at sun.com" <Simon.Zheng at Sun.COM> Message-id: <1192791200.11330.28.camel at goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.12.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 8BIT - New a message without Chinese Character, it liked this Subject: testing agaiin Sender: Simon.Zheng at Sun.COM To: "simon.zheng" <Simon.Zheng at Sun.COM> Message-id: <1192790818.11330.21.camel at goaltender> MIME-version: 1.0 X-Mailer: Evolution 2.12.0 Content-type: text/plain Could you possibly describe your issue again, I'm a bit confused.:-) -Simon
