GNOME Bugzilla – Bug 612190
Copying email addresses with utf8 chars is broken for the To: and Cc: edit boxes
Last modified: 2018-11-29 05:53:01 UTC
I've been seeing this for the last 3 years, so it's a long standing bug. Currently I'm reporting with evolution 2.28.3-0ubuntu3 / Ubuntu Lucid alpha 3. Steps to reproduce: 1) Copy this email address: Άλκης Γεωργόπουλος <alkisg@somewhere.com> 2) Start writing a new mail and paste it to the "To:" line. 3) Copy the email address from the "To:" line and paste it to the email body. You should be seeing: =?UTF-8?Q?=CE=86=CE=BB=CE=BA=CE=B7=CF=82_?= =?UTF-8?Q?=CE=93=CE=B5=CF=89=CF=81=CE=B3=CF=8C=CF=80=CE=BF=CF=85=CE=BB?= =?UTF-8?Q?=CE=BF=CF=82?= <alkisg@somewhere.com> which obviously isn't what we want. So *copying* from the "To:" or "Cc:" fields is broken in evolution for non-ascii email addresses. -- This has been reported to https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/533129, and I'm forwarding it upstream as requested.
I could reproduce this bug by just pasting α <a> into the "To:" field Trying then to copy it again from the "To:" field and paste it into the mail body resulted to: =?UTF-8?Q?=CE=B1?= <a>
looks similar to bug 442934
I think that bug 442934 is about decoding headers, while this one is about the To: box encoding its contents before putting them to the clipboard. It shouldn't use any kind of encoding for the clipboard, imho. So I think they're not related at all.
may be fixed with bug 609042. Can you please check again whether this issue still happens in Evolution 2.32.0 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
Is there a live distro available with that Evolution version? I tried downloading Ubuntu Maverick but it only has evolution 2.30.3-1ubuntu5. The bug is still valid there.
(In reply to comment #5) > Is there a live distro available with that Evolution version? > I tried downloading Ubuntu Maverick but it only has evolution 2.30.3-1ubuntu5. > The bug is still valid there. bug 609042 mentioned in comment#4 was fixed in 2.30.0 so if you still see bug in evolution 2.30.3 then your problem is not yet fixed.
Assuming this is obsolete nowadays. If not, then please reopen if you can still reproduce in 3.30 or later.