Closed
Bug 285053
Opened 19 years ago
Closed 19 years ago
Incorrect change of header when replying message that uses different charsets for body and subject
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 229399
People
(Reporter: black.fox, Assigned: sspitzer)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041220 K-Meleon/0.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041220 K-Meleon/0.9 Then someone uses Mozilla Mail or Thunderbird and tries to relpy message that uses different charsets for body and headers (body encoded using UTF-8 and subject encoded using ISO-8859-2) Mozilla Mail (or Thunderbird) tries to use UTF-8 for all parts of the message. The problem is that when changing charset for headers Mozilla spoilts it and makes unreadable. Reproducible: Always Message (posted using 40tude_Dialog) with ISO-8859-2 subject and UTF-8 body: http://www.google.pl/groups?as_umsgid=hh8ipks1aw43.dlg@blackfox.org&lr=&hl=pl Message (posted using Thunderbird 1.0 20041206) that is a reply for message above: http://www.google.pl/groups?as_umsgid=422B8664.4010203@blackfox.org&lr=&hl=pl
Comment 1•19 years ago
|
||
Those URLs are not useful in figuring out the problem. Please save the original message as a .EML file, and attach that file to this bug using the Create New Attachment link above.
Comment 2•19 years ago
|
||
-> Core/MailNews: Composition
Component: MailNews: Main Mail Window → MailNews: Composition
Product: Mozilla Application Suite → Core
Version: unspecified → Trunk
Reporter | ||
Comment 3•19 years ago
|
||
Message no 1 - created by 40tude Dialog 2.0.15.1
Reporter | ||
Comment 4•19 years ago
|
||
Message 2 - crated by Thunderbird 1.0 Win32
Comment 5•19 years ago
|
||
Thanks. *** This bug has been marked as a duplicate of 229399 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•