268549 - ISO-2022-JP encoding cannot be used if non-ASCII characters are in sender's name

Status: RESOLVED DUPLICATE of bug 249530

(Thunderbird :: Message Compose Window, defect)

Description

[Alf]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040825 Camino/0.8.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040825 Camino/0.8.1

(For proper display of the steps to reproduce the bug set browser encoding to UTF8)
Whenever sendind/replying mail using ISO-2022-JP encoding and the name of the
sender used has characters outside ISO-2022-JP (I guess it affects any other
encoding) UTF8 must be used or else Thunderbird won't allow the message be sent.
As far as I'm concerned it happened since 0.8 under Linux platform but it also
happens in 0.8 and 0.9 under Mac OS X.

Reproducible: Always
Steps to Reproduce:
1. In account settings enter in "Your name" field, e.g., ñ (n tilde)
2. Write a mail
3. Write anything or just leave everything blank (content doesn't matter)
4. Choose ISO-2022-JP encoding in menu "View-Character Encoding"
5. Send message
Actual Results:  
A warning dialog saying "The message you composed contains characters not found
in the selected Character Encoding. While you can choose a different Character
Encoding, it is usually safe to use Unicode for mail. To send or save it as
Unicode (UTF-8), click OK. To return to the Composer window where you can choose
a different Character Encoding, click Cancel".

Expected Results:  
Although the sender's name field contains characters outside the encoding
selected it would make sense to let the user "force" the application to use it,
adding a button "Use current encoding (ISO-2022-JP)" or similar. Other
applications like Evolution or Apple Mail let you do it and it's a nuisance to
change your name only for sending some messages. I strongly encourage the use of
UTF8 but currently in Japan mobile phones only accept messages using this
encoding, so in certain situations ISO-2022-JP must be used.

Comment 1

[Jungshik Shin]

*** This bug has been marked as a duplicate of 249530 ***