28868 - Cyrillic page display is wrong when forwarding as Inline

Status: VERIFIED INVALID

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

Description

[marina]

Steps to reproduce:
- go to the above URL (from 5.0);
- go View| Character coding and notice that this is Win-1251 page;
- send it to your acount (File|Send page);
- get the message;
- select it and go Message | Forward|Inline;
- in the Composition window there is no Win-1251 encoding so chose KOI-8r;
- send the message and open it;
//note: the page is garbled
(the problem doesn't occur if you repeat all steps in exception to send it as an 
Attachment), sent as Attachment Display is correct

Comment 1

[rhp (gone)]

Plain text or HTML compose?

- rhp

Comment 2

[marina]

This is HTML compose.

Comment 3

[Katsuhiko Momoi]

The web server at the above site sends HTTP charset info for 
Windows-1251.
This is correctly reflected in the Content-Type line when it is 
sent by Mozilla using Send Page function. 
But somehow, the charset parameter disappears from the 
Content-Type line when we do forward/inline. And since there is
no meta charset tag in the attachment itself, it cannot be 
displayed correctly at present.

Comment 4

[rhp (gone)]

Following product marketing on this one.

- rhp

Comment 5

[scottputterman]

reassigning to ducarroz

Comment 6

[Jean-Francois Ducarroz]

Accepting.

I think the problem is due to the fact that when we specify attachment in
nsiMsgCompFields, we cannot specify the characters set. I have plane to rewrite
the way we store attachment information.

Comment 7

[marina]

it seems that a lot of thins have changed since this bug was filed. i am able to
customized the encoding while sending, this particular page has a meta-tag
<win-1251> and when sent in the right encoding and reloaded after it displays
correctly. i will invalid this bug now because we are able to send attachment
now correctrly

Comment 8

[marina]

and verified as such