maemo.org Bugzilla – Bug 7139
Replying to an email with non-ascii chars in From cuts name short
Last modified: 2010-03-15 20:56:26 UTC
You need to
before you can comment on or make changes to this bug.
(Settings > General > About product)
EXACT STEPS LEADING TO PROBLEM:
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Receive an email from a person with non-ascii chars in the name. Eg. "Adam
2. Reply to the email.
3. Note that the To: field has chopped off one letter per non-ascii char in the
name, eg. "Adam Sjøgre"
The full name in the To: field, eg. "Adam Sjøgren"
One letter chopped off: "Adam Sjøgre"
(always, less than 1/10, 5/10, 9/10)
EXTRA SOFTWARE INSTALLED:
It looks like a strlen() counting bytes vs. utf-8 characters problem. If I
receive a test email from "Frække frølår Test" (eg. three non-ascii chars) and
reply to it, the To: field contains the text "Frække frølår T" (three letters
I haven't had time to dive into the code to produce a patch yet.
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199)
Gecko/20091216 Iceweasel/3.5.6 (like Firefox/3.5.6; Debian-3.5.6-1)
Created an attachment (id=1804) [details]
Example email and reply
I am attaching an mbox file containing an email sent to my N900 and a reply
written on it, showing the chopping of three letters.
This works fine here running the internal version 2009.51-8, so I assume that
this has been fixed in the maintime.
Attaching two screenshots from the Composer window (but Name display also is
correct in the list view).
Created an attachment (id=1809) [details]
Screenshot 1 from version 2009.51-8
Created an attachment (id=1810) [details]
Screenshot 2 from version 2009.51-8
(In reply to comment #2)
> This works fine here running the internal version 2009.51-8, so I assume that
> this has been fixed in the maintime.
I seem to have narrowed the problem down to
quote_name_part () in src/modest-text-utils.c, but when I compare that to the
latest from "modest" on gitorious.org, I can't see what change fixed it. I
wonder what it was...
Ah, I was looking at the master branch, not the modest-3-2 branch (which oddly
contains fixes that master doesn't). This problem was fixed by svillar
I must admit that I don't know if the fix is already included in today's
2.2009.51-1 update release or not. Checking and reporting back is welcome!
(In reply to comment #6)
> I must admit that I don't know if the fix is already included in today's
> 2.2009.51-1 update release or not. Checking and reporting back is welcome!
I can confirm that it is fixed for me in 2.2009.51-1. Thanks!
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).