Bug 81078

Summary: Inserting email address via DnD does not decode =?...?= encoding
Product: [Unmaintained] kmail Reporter: Jens <jens-bugs.kde.org>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kollix, mmodem00, opensourcecat
Priority: NOR Keywords: triaged
Version: 1.6.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: proposed patch

Description Jens 2004-05-07 10:38:15 UTC 
Version:           1.6.2 (using KDE 3.2.2,  (testing/unstable))
Compiler:          gcc version 3.3.3 (Debian 20040401)
OS:          Linux (i686) release 2.6.5-rc1-bk2-p3

Hi,

I have a mail from "Heinz Müller" <mueller@foo.co>.
Press CTRL-N to open a new mail to Heinz Möller, and drag and drop the email adress from the main KMail window into the text field for "To:" for the new mail.

The name inserted in the "To:" field will be something like 
"Heinz =?utf-8?q?M=C3=B6ller?= <mueller@foo.co>". Looks to me like UTF-8 (at least) is not properly decoded when drag&drop is used.


Thanks if anybody cares to have a look at this bug ;)
Comment 1 Jakob Schroeter 2004-08-21 14:51:25 UTC 
Created attachment 7205 [details]
proposed patch

I'd like to propose the attached patch. It's basically copy & paste from
KMMsgBase so I think it's not the most elegant solution.
Is it correct to use local8Bit() here?

Suggestions?
Comment 2 Jens 2005-01-11 14:59:30 UTC 
Hi,

the proposed patch seems not to be in CVS yet.
Does anything speak against it? The bug is still there.

Thank you!
Comment 3 Stefan Borggraefe 2006-06-30 13:25:17 UTC 
*** Bug 129990 has been marked as a duplicate of this bug. ***
Comment 4 Philip Rodrigues 2006-10-29 19:39:23 UTC 
Same behaviour in r599765
Comment 5 Salvatore Brigaglia 2008-11-09 12:50:06 UTC 
Still here, (bug day 09 november 2008). opensourcecat.
Comment 6 Thomas McGuire 2009-08-23 18:37:35 UTC 
I think Martin just fixed this in r1014687.
Comment 7 Martin Koller 2009-08-30 20:00:40 UTC 

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