Closed Bug 81456 Opened 25 years ago Closed 25 years ago

Fail to set up the right encoding for Reply/Forward when two folders with different encodings are open in stand alone window

Categories

(MailNews Core :: Internationalization, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 59229

People

(Reporter: marina, Assigned: nhottanscp)

Details

**** observed with 2001-05-17 build **** Steps to reproduce: - open in stand alone windows two folders ( either on the IMAP or News account); - select a mail on one of them ( say: Cyrillic folder, koi8-r mail); - click Reply(Forward); bring up the reply window; //note: header and body are displayed correctly in Koi8-r encoding; - select a different folder now ( say JA, jp-iso-2022 mail); - click on Reply( forward); bring up the reply ( forward) window; //note: header and body are unreadable because the encoding for the window is KOI8-R you can not reverse this condition to the correct behavior unless you close/reopen mail ( but you won't be able to send reply/forward mail with two different encodings folders open at the same time
dup of 49230?
Summary: Fail to set up the right encoding for Reply/Forward when two folders with different encodings are open in stand alone window → Fail to set up the right encoding for Reply/Forward when two folders with different encodings are open in stand alone window
49230 is describing the case when there is no MIME or the message is mislabled, then when open in the standalone window it fail to inherit the correct encoding; in my case both mails are MIME encoded and when open in standalone windows the display is correctl:only in case of Reply(Forward) the encoding of the first mail (in that case KOI8-R) becomes a default for the second Reply
sorry a wrong bug, dup of bug 59229?
yep, this is a dup of Kat's bug # 59229, a very annoying one btw...
*** This bug has been marked as a duplicate of 59229 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
verified as such
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.