Closed
Bug 178432
Opened 23 years ago
Closed 22 years ago
accents are transformed into strange codes in all messages after clicking on a swf link in a message
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 110729
People
(Reporter: pascalc, Assigned: mscott)
Details
Build 2002103004 WinXP
Steps to reproduce the bug
1 send to yourself an email with a link to a swf file,
http://home.attbi.com/~n9ivo/whatswrong.swf for instance
2 send to yourself a message containing accents such as
é
à
è
ô
û
ö
ï
3 Open the message with the accents, note that they are displayed correctly
4 Open the second message with the lonk, click on the link to the swf file in
MailNews, the swf file gets displayed in the message window
5 reopen the message with the accents, they are displayed like this:
é
Ã
è
ô
û
ö
ï
All messages in all my mailboxes now display wrongly accentuated characters. The
only way to get them displayed correctly (on a message per message basis) is to
force Charset coding to UTF8
Hee are the header lines concerning coding for the test message with the accents:
X-Accept-Language: en, fr-fr, en-gb, es-es
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
dup of bug # 110729?
Comment 2•22 years ago
|
||
I could reproduce this bug on Linux RedHat 7.3 with updated mozilla packages :
mozilla-1.2.1-0_rh7
mozilla-mail-1.2.1-0_rh7
nautilus-mozilla-1.0.6-16
[...]
Changing Character encodig to UTF-8 for the message with accents leads to
the correct display.
Jean-Michel BARBET.
| Reporter | ||
Comment 3•22 years ago
|
||
setting OS to ALL following Jean-Michel's comment
OS: Windows XP → All
| Reporter | ||
Comment 4•22 years ago
|
||
this was indeed a dupe of bug 110729, it is now fixed.
*** This bug has been marked as a duplicate of 110729 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•