Bug 259043

Summary: Bad encoding in 'to' field when saving message as draft with non-Latin characters
Product: [Applications] kmail2 Reporter: Murz <MurzNN>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 2.0.89   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: message_drafts.mbox
message_outbox.mbox

Description Murz 2010-12-06 20:57:57 UTC
Version:           2.0.89
OS:                Linux

When I create the message via kmail2 interface, I fill the fields with Cyrillic symbols in utf-8 encoding.
But when I save this message as draft, I see '?????' symbols instead of cyrillic letters in to-cc-bcc fields.

Reproducible: Always

Steps to Reproduce:
Create new message via kmail2 interface and fill the fields:

to: Вася Vasya Иванов <vasya@example.com>
cc: Петя Petya <petya@example.com>
bcc: Маша 123 <masha@example.com>
subject: Тема subject 123
body: Сообщение 123.

Press File > Save as Draft.
Look at the message in folder Draft.

Actual Results:  
To:	???? Vasya ?????? <vasya@example.com>
CC:	???? Petya <petya@example.com>
BCC:	???? 123 <masha@example.com>
Subject:	Тема subject 123
Body:
Сообщение 123.

Expected Results:  
To:	Вася Vasya Иванов <vasya@example.com>
CC:	Петя Petya <petya@example.com>
BCC:	Маша 123 <masha@example.com>
Subject:	Тема subject 123
Body:
Сообщение 123.

OS: Linux (x86_64) release 2.6.35-23-generic
Compiler: cc
Comment 1 Murz 2010-12-06 21:01:44 UTC
Created attachment 54220 [details]
message_drafts.mbox

The message after save it to drafts.
Comment 2 Murz 2010-12-06 21:03:47 UTC
Created attachment 54221 [details]
message_outbox.mbox

If I press "Send now" or "Send later" on newly created message (without saving it to drafts), it saves and sends normally, without ???? symbols.
The example of message how it looks in outbox folder is attached.
Comment 3 Murz 2010-12-24 13:37:30 UTC
Same problem is with "from" field too.
Comment 4 Murz 2011-01-21 09:15:31 UTC

*** This bug has been marked as a duplicate of bug 263761 ***