Closed Bug 457236 Opened 17 years ago Closed 17 years ago

Forwarding a message can result in mangled text. Replying to the same message does not pose a problem.

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 307023

People

(Reporter: post, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 Build Identifier: TB 2.0.0.17 (20080914) Forwarding a message with 2-byte characters (UTF8) goes amiss because the encoding (UTF8) is "forgotten" by Thunderbird. This is not the case when replying a message (that works). A workaround is to reply and then to change the recipient(s). Another, more interesting workaround is to change the encoding to some random value (view --> character encoding --> random) and then to change back the encoding to UTF8: the message can now be forwarded without problems. It's probably a message edited in Microsoft Word, which results in garbage HTML. Nonetheless, replying that message does not result in mangled text. Only forwarding the message goes wrong. I think that TB "forgets" the correct encoding when forwarding a message. Reproducible: Always Steps to Reproduce: You can download the entire message that shows this mangling when being forwarded. The file is encrypted with Ncrypt (http://ncrypt.sourceforge.net/). Please email me ([url]post@evert.net[/url])for the password. http://www.evert.net/temp/fw.eml.ncrypt Actual Results: some mangled characters Expected Results: same characters / same encoding as the original message version 2.0.0.17 (20080914) The problem can be reproduced on older versions, with other user profiles and no add-ons. have a look at my screenshots: http://forums.mozillazine.org/viewtopic.php?f=31&t=872595&p=4577835#p4577835
Version: unspecified → 2.0
According to your post to the thread of MozillaZine forum, mail header is as follows. > ------=_NextPart_002_003B_01C91EFD.C1445590 > Content-Type: text/html; charset="utf-8" > Content-Transfer-Encoding: quoted-printable Really charset related problem(encoding (UTF8) is "forgotten")? Problem upon "HTML with quoted-printable"(i.e. DUP of Bug 307023), isn't it? > Another, more interesting workaround is to change the encoding to some random value (view --> character encoding --> random) > and then to change back the encoding to UTF8: > the message can now be forwarded without problems. It sounds for me to be an evidence of DUP of Bug 307023. - By "view->character encoding->random, then to change back to UTF8", "already decoded" flag is set for original "HTML with quoted-printable" data. Read Bug 307023 Comment #36, please.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.