233337 - ASCII subject fools character encoding algorithm and leads to data loss

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Roman R.]

User-Agent:       
Build Identifier: 0.5b (20040204)

Messages with non-ASCII (Cyrillic in my case) characters in the body are not
saved as Unicode UTF-8 if subject is made of ASCII characters. When I attempt to
save or send a message with non-ASCII characters, I am presented with a message
box that offers to convert my message to UTF-8 by pressing OK button. However,
this works ONLY if the subject also consists of non-ASCII characters. Otherwise,
the message is saved or sent with '?' characters instead of non-ASCII characters.

Reproducible: Always
Steps to Reproduce:
1. Compose a message with a non-ASCII body and ASCII subject (an empty subject
will do too).
2. Invoke save or send command.
3. Click OK on a message box that says, "The message you composed contains non
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. ..."
Actual Results:  
The message will be saved/sent with ?'s instead of non-ASCII characters, and
encoding is set to ISO-8859-1, which is the default on my system.

Expected Results:  
The whole message should've been converted to UTF-8.

Comment 1

[Roman R.]

Changing severity of this bug to critical as the bug leads to data loss.

Comment 2

[Rimas Kudelis [use needinfo to ping]]

Confirming.

this also happens for me on Thunderbird 0.5 on linux.

for example, characters:
"bandom ąčęąčęūąėęėč"
were converted to:
"bandom a;c(e.a;c(e.u-a;e;e.e;c("

Comment 3

[Eliot Landrum]

User-Agent: Mozilla Thunderbird 0.6+ (Windows/20040907)

I was unable to see the reporters result.

I tested with the following text in the message: 

ĄĆĉ 

My subject was "bug 233337".

If the reporter is still experiencing this problem, perhaps the reporter could
provide a test case for us?

The comment by Rimas Kudelis seems completely unrelated. 

Comment 4

[Roman R.]

I just upgraded to 0.7.3 and was happy to notice that this problem is no longer
present. I guess this bug can be closed now.

Comment 5

[Eliot Landrum]

Glad to hear it, reporter! Enjoy Thunderbird!