126120 - message source window should inherit the charset for mail body view

Status: RESOLVED DUPLICATE of bug 111164

(MailNews Core :: Internationalization, defect)

Description

[u32858]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205
BuildID:    2002020511

Hi,

I recieved an email with some japanese, but in the header 

Content-Type: text/plain; charset=ISO-8859-1

it takes about 10 seconds to render the window, so i think its having problems
deciding what the email is






Reproducible: Always
Steps to Reproduce:
1.I selected View Message source and I could read the Japanese ok, but the main
window was locked to ISO-8859-1, correctly I belive.
2.However after forceably chaging the Message display window to Shift_JIS making
the japanese visible.. Now the Message source windo was  not displaying the
Japanese message source correctly
3.

Actual Results:  Message source window using different charset to the Main window

Expected Results:  Should follow the main windows char set, but it was
surprising that it worked with the main window char set to ISO-8859-1

Sample source email


Subject: moshi moshi
Message-ID: <[e-mail]>
Date: Sun, 17 Feb 2002 15:39:15 -0500 (EST)
From: Yxxxxxon <yxxxnon@pxxxx>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.2
X-Originating-IP: 6xxxxxx9
X-UIDL: 4W5!!AWM!!CX7"!VN@"!
Status: U

���@���@JG�[����,

�@�@��{��@�͂ǂ��ł����H�y���܂����H

      how is it

Comment 1

[ji]

I agree that the message source window should inherit the charset of the 3-pane
window. Confirmed the bug. The workaround is to turn on the auto-detector.

Comment 2

[nhottanscp]

Is this Linux only?
'charset of the 3-pane window', does this mean the charset of the message body view?

Comment 3

[ji]

Yes, I meant charset for mail body view.
It happens to the other platforms too.

Comment 4

[Boris Zbarsky [:bzbarsky]]

*** Bug 131070 has been marked as a duplicate of this bug. ***

Comment 5

[u32858]

re: My new bug report
Actually this is differerent as its got the correct headers.
same topic, so i don't mind how it gets fixed though :)
JG

Comment 6

[Dimitrios]

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

Comment 8

[Kent James (:rkent)]

Was this dup unintentional? If intentional, it deserves a comment.

Comment 9

[aleth [:aleth]]

It was a typo, thanks.