227360 - Wrong character encoding when viewing message/rfc822 email from http source

Status: NEW

(MailNews Core :: Backend, defect)

Description

[Martin von Gagern]

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

When opening a location that provides mime type message/rfc822 and in this
message an "text/plain; charset=iso-8859-1" body with some strange characters,
those are not automatically displayed correctly. Usually my default character
encoding, ISO-8859-15 is used, rendering for example german umlauts as two
characters. Manually selecting UTF-8 encoding fixes the problem. I believe that
the message encoding is internally translated to UTF-8, but the coding of the
whole page is not automatically set correctly.

Reproducible: Always

Steps to Reproduce:
1. Open HTTP URL with message/rfc822 content

Actual Results:  
2. character coding is still at its default value
3. non-ASCII characters are rendered as multiple strange symbols

Expected Results:  
2. character coding automatically set corretly (i.e. UTF-8)
3. message displayed respecting the coding specification in the message header(s)

Comment 1

[Boris Zbarsky [:bzbarsky]]

message/rfc822 to HTML conversion is done in mailnews code...

Comment 2

[Simón Medrano]

Attachment: Attachment 1: Content-type: text/html; charset=iso-8859-1

A multipart message with an HTML part described as
Content-type: text/html; charset=iso-8859-1
(See Attachment 1 [details] [diff]) displays with weird characters on Mozilla Navigator (from a
local or remote location), but it renders OK on Mozilla Mail and News and
Thunderbird (from the mailbox).

Comment 3

[Simón Medrano]

Attachment: Attachment 2: Content-type: text/html; charset=UTF-8

If you change
Content-type: text/html; charset=iso-8859-1
to
Content-type: text/html; charset=UTF-8
(See Attachment 2 [details] [diff]) then it renders OK on Navigator.

Comment 4

[(not reading, please use [e-mail] instead)]

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 5

[OstGote!]

I guess it is the same issue like Bug 206421.

Comment 6

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"

Comment 7

[WADA:World Anti-bad-Duping Agency]

Attachment: Attachment 2x: Same data as Attachment 2. To set MIME-Type=message/rfc822;charset=iso-8859-1

Comment 8

[WADA:World Anti-bad-Duping Agency]

Attachment: Attachment 1x: Same data as Attachment 1. To set MIME-Type=message/rfc822;charset=iso-8859-1

Comment 9

[WADA:World Anti-bad-Duping Agency]

(1) charset of MIME-type of attachment relates to auto-detect only.
    If charset is specified, it is used even when auto-detect=on.
(2) Both SeaMonkey 1 & 2 uses charset of MIME type or auto-detected charset.
    It's displayed in View/Character Encoding at first display.
    "Content-Type: ...; charset=xxxx" header in mail data is not used.
(3) It's displays as expected if View/Character Encoding is changed to utf-8. 

Problem like next?
  Browser expects charset of MIME type or auto-detected charset.
  But Mailer returns data in UTF-8.

Comment 10

[WADA:World Anti-bad-Duping Agency]

I changed MIME type of Attachment 1 [details] [diff]X to "message/rfc822; charser=utf-8".
Message body was displayed as expected by SeaMonkey.

Comment 11

[WADA:World Anti-bad-Duping Agency]

Problem had been explained by Bug 206421 Comment #4 in 2004-11.

Comment 13

[WADA:World Anti-bad-Duping Agency]

Copy of Bug 206421 Comment #4 From OstGote! on 2004-11-03.

> The character encoding is respected (look at view - character encoding) 
> but in spite of the display is wrong.
> I guess because there is an internal UTF-conversion. (snip)
> The browser displays that ISO-8859-15 is used (that is correct, see source)
> but the umlauts are still wrong.
> Now change to UTF-8 and the display is ok.