178106 - japanese subject corrupted in window bar and subject line of messenger

Status: RESOLVED EXPIRED

(MailNews Core :: Internationalization, defect)

Description

[u32858]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021029
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021029

japanese subject corrupted in window bar and subject line of messenger.

it is strange that I can "view->message source" and the japanese in their is
displayed fine, also the body japanese text is displayed fine.

Reproducible: Always

Steps to Reproduce:
1.open the attatchment and see the subject line and the messenger window title 
2.
3.

Actual Results:  
D.D.B.$B%"%/%;%9%Q%9%o!<%I$N$*CN$i$;(B

Expected Results:  
D.D.B.&#12450;&#12463;&#12475;&#12473;&#12497;&#12473;&#12527;&#12540;&#12489;&#12398;&#12362;&#30693;&#12425;&#12379;

Bug submitted in UTF-8

Comment 1

[u32858]

Attachment: example

What is also strange is that opening the file in mozilla browser and setting
char set to iso-2022-jp means the subject is readable in window title and
message
but msg is corrupted :(

View message source again looks fine for subject and body of msg

JG

Comment 2

[u32858]

Somthing strange, the corrupted text i pasted is displayed fine in this window
as iso-2022-jp

but the unicode is not

JG

Comment 3

[marina]

adding Xianglan to the cc list

Comment 4

[ji]

The testing mail doesn't show after I saved it into the Local Folders. Marina,
do you have problem with it?

Comment 5

[marina]

yep, i have the same problem

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.