Closed Bug 285731 Opened 20 years ago Closed 20 years ago

some characters (like German umlauts) not correct after clicking mailto-Link with body header

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 169388

People

(Reporter: ts, Assigned: mscott)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041122 Firefox/1.0
Build Identifier: Thunderbird Version 1.0 (20041206)

When clicking on mailto links a new mail composing window opens but the body
text beginning from a character like the German ä, ü, ö or ß is replaced by »?«
signs (like unknown UTF-8 chars are displayed in Firefox).

The same link works correctly in Microsoft Outlook and Outlook Express.

example.
<a href"mailto:d?subject=Subject&body=German%20for%20crazy%3A%0Averr%FCckt">...</a>

Reproducible: Always

Steps to Reproduce:
1. Put a link like <a
href"mailto:d?subject=Subject&body=German%20for%20crazy%3A%0Averr%FCckt">...</a>
into an HTML formatted email or into an HTML document.
2. Be sure TB is the preferred MUA.
3. Click the link

Actual Results:  
The body in Thunderbird's mail composing window looks like this:

German word for crazy:
verr����

Expected Results:  
The body in MS Outlook's mail composing window looks like this:

German word for crazy:
verrückt
Summary: some characters (like German ä, ö, ü, ß) not correct after clicking mailto-Link with body header → some characters (like German umlauts) not correct after clicking mailto-Link with body header
I have to switch my Browser to UTF-8 to see both the right and wrong characters
correctly.
(In reply to comment #1)
> I have to switch my Browser to UTF-8 to see both the right and wrong
> characters correctly.

You mean, if you are viewing the link in the browser, that's what you need to 
do?  Interestingly, if I view an email containing that URL and force the 
encoding to UTF-8, I still get the same result.

Looks like this is related to bug 192108, which points to bug 169425.
According to the discussion at that bug, escaped characters in a URI need to be 
escaped as UTF-8 -- so the last bit of your URL should be:
  verr%C3%BCckt

And in fact, that works.
Found a dupe.

*** This bug has been marked as a duplicate of 169388 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.