41460 - Int chars in subject kills rest of subject

Status: VERIFIED FIXED

(SeaMonkey :: MailNews: Message Display, defect, P3)

Description

[Henrik Gemal]

If you send a mail with fx the followin headers:
Subject: første møde

the subject is correct shown in the Subject column of the 3pane, but when the 
selecting the mail the only thing that is shown is:
Subject: f

It seems like the parser dies because of not encoded subject with danish chars.

Since it's possible to parse it ok in the Subject column so should it be in the 
mail view.

Comment 1

[Henrik Gemal]

Attachment: Subject is shown differently

Comment 2

[scottputterman]

reassigning to rhp since I'm not sure where we're losing the subject, cc mscott.

Comment 3

[scottputterman]

reassigning to hyatt.  It looks like the change to bold is causing this.

Comment 4

[Henrik Gemal]

What is going on here...? Why did you change the subject...?
The last comment:
"reassigning to hyatt.  It looks like the change to bold is causing this."
must be to bug 41463!

Comment 5

[scottputterman]

sorry, there's a bug in the current build where when you start using bugzilla 
heavily, old values start showing up in new bugs.  See 41373.  Sorry about that.  
I've been trying to be careful to prevent it from happening when I see this.

this bug should go back to rhp with a cc to mscott.

Comment 6

[rhp (gone)]

This seems kind of bad. Should be easy once I find it...Nominating for beta2

- rhp

Comment 7

[rhp (gone)]

Hi Naoki,
I think I need your help on this one. I've debugged it down to the point where 
we are doing the following at line 194 of 
mozilla\mailnews\mime\emitters\src\nsMimeHtmlEmitter.cpp :

rv = 
mUnicodeConverter->DecodeMimePartIIStr(NS_ConvertASCIItoUCS2(headerInfo->value)
, charset, getter_Copies(unicodeHeaderValue));


the value of headerInfo->value is "første møde" and charset is UTF-8.

Well, when I do the conversion, I get "f" for unicodeHeaderValue and rc is not 
zero, but its not a failure either 5242892.

- rhp

Comment 8

[leger]

Putting on [nsbeta2+] [will be minus on 6/15] radar.

Comment 9

[leger]

Per msanz, very bad must fix bug.  Removing 6/15.

Comment 10

[nhottanscp]

I cannot reproduce this. I copy/paste "første møde" in subject and sent by 4.x 
and 6.0 (as ISO-8859-1). In both cases I see the subject correctly.

Comment 11

[marina]

I am not able to reproduce it on my NT machine but Henrik used Win 2000.

Comment 12

[Henrik Gemal]

The reason way you cant reproduce the problem is that when sending a mail 
from netscape 4.x with the subject "første møde" it will MIME encode the subject 
because of the "ø". This was not the case when I recieved the mail.

I'll attach a mail you can send to yourself via fx sendmail.

Comment 13

[Henrik Gemal]

Attachment: mail with difficult subject...:)

Comment 14

[nhottanscp]

I can reproduce this now.
The charset parameter for DecodeMimePartIIStr() specifies a default charset 
which is taken from folder attribute. That is filed as a bug 41125.
Currently, "UTF-8" is used as a default for this default value but that should 
be "ISO-8859-1" instead. I will make the change and that should resolve the 
problem of this bug.

Comment 15

[Katsuhiko Momoi]

You can also use NoMime.zip test case I uploaded for  
Bug 41816. Display of Message envelope headers
gets cut off for all the 8-bit no-MIME-encoded headers
there. (There are about 9 charsets in the data there
and all exhibit this problem except ISO-2022-JP which is 
7-bit code.)

Comment 16

[Katsuhiko Momoi]

For some reason, I18n QAs were missing from CC line. 

Comment 17

[nhottanscp]

checked in yesterday

Comment 18

[Henrik Gemal]

Verified with build 2000061220 on win2k