Closed
Bug 368036
Opened 18 years ago
Closed 18 years ago
wrong mailto link handling on url encoded links with international characters
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 169388
People
(Reporter: szimszon, Assigned: mscott)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061208 Firefox/2.0.0.1 Build Identifier: version 2 beta 2 (20070116) If you try to click to the web page http://linux.oregpreshaz.hu/mailto.html and the mail compose window appears after the first not English character I see only that: http://linux.oregpreshaz.hu/thunderbird_mailto.png Reproducible: Always Steps to Reproduce: 1.Ckick on http://linux.oregpreshaz.hu/mailto.html Actual Results: http://linux.oregpreshaz.hu/thunderbird_mailto.png Expected Results: Text in body like this: Tisztelt Öregprés-ház! Köszönöm!
Comment 1•18 years ago
|
||
Junk in, junk out -you have some encoding error on the page/with the data. The url i put the URL field works fine for me.
Hmmm, that's weird... It seems to me that TB has trouble with iso8859-2 uri escaped text. I tried your link (mailto:foo@test.com?subject=some%20subject&body=Tisztelt%20%C3%96regpr%C3%A9s-h%C3%A1z!%20K%C3%B6sz%C3%B6n%C3%B6m!) all good, but my link (http://linux.oregpreshaz.hu/mailto.html - corrected, to use correct content charset iso8859-2). What I'm using is perl URI::Escape; iso8859-2 -- uri_escape("�regpr�s-h�z"); utf-8 -- uri_escape("Öregprés-ház"); to get my uri escaped text. With that function I have two outputs of "Öregprés-ház": 1; iso8859-2: "%D6regpr%E9s-h%E1z" result: http://linux.oregpreshaz.hu/thunderbird_mailto.png 2; utf-8: "%C3%96regpr%C3%A9s-h%C3%A1z" result: good
Comment 3•18 years ago
|
||
Dupe of bug 169388, I think. The results you are seeing are actually expected; the URL should be in UTF-8 when unescaped -- that's the standard for URLs, it has nothing to do with page encoding.
Yes you are right. We can't use any non ascii characters in mailto link's message body :( (only in header, with some encoding info see comment #7 in bug 169388) Thank you!
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•