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

Plain text or HTML compose? - rhp

This is HTML compose.

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.

Following product marketing on this one. - rhp

reassigning to 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.

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

and verified as such