Closed Bug 290738 Opened 20 years ago Closed 20 years ago

Reply-To header is truncated at the point where it reaches an accented character

Categories

(Thunderbird :: Message Compose Window, defect)

Product:
Thunderbird
Component:
Message Compose Window
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 135428

People

(Reporter: td419, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; hu-HU; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; hu-HU; rv:1.7.5) Gecko/20041108 Firefox/1.0

I am a Hungarian and have accented characters in my first & last name. I use the
Reply-To headers. In Tools/Account settings I set the Reply-To field to

"Tereánszky, Dávid" <user@host.com>

When I was testing this setting (because of accents, I check how my emails look
like - in Central Europe things are not easy :-D), I found out that if the
Reply-To header contains any accented characters, the reply message's Reply-To
field will be truncated. It takes place when it reaches the first accented
character.

Reproducible: Always

Steps to Reproduce:
1. Set up the "Reply-to address" field in Account settings with a string (like
the following) that CONTAINS ACCENTS:
"This_á_is_é my_í_fake_ó_name with_ú_accents" <user@host.com>

2. Click "Write"
Actual Results:  
The Reply-To field looks like this:

This_

Expected Results:  
The Reply-To field should look like this:

"This_á_is_é my_í_fake_ó_name with_ú_accents" <user@host.com>

I used the default theme, the app didn't crash, it's only a tiny problem.
ISO-8859-2 encoding works fine in headers and the message body, IMHO the problem
is caused by the module that fills in the headers of the reply message.

I think this is a european problem - English names usually don't contain accents...
Suite bug 135428 is about a different field that gets truncated at a special
character, maybe related?
(In reply to comment #1)
> Suite bug 135428 is about a different field that gets truncated at a special
> character, maybe related?

OK, that's similar. I was searching the DB especially for accented characters,
becasue I've found bugs related with special characters (if the sender contains
eg. "(").

*** This bug has been marked as a duplicate of 135428 ***
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.