Closed
Bug 843600
Opened 11 years ago
Closed 11 years ago
Seamonkey mail preview uses incorrect encoding since 2.16
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(seamonkey2.16 affected, seamonkey2.19 affected)
RESOLVED
DUPLICATE
of bug 594646
People
(Reporter: bjoernv, Unassigned)
Details
(Keywords: testcase, Whiteboard: [seamonkey 2.15-unaffected] [testcase=attachment 717463])
Attachments
(6 files)
The test message in Seamonkey 2.16
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 SeaMonkey/2.16 Build ID: 2013021700 Steps to reproduce: Some email messages are not displayed with the correct encoding. Manual correction of encoding is not possible for these messages. Only some messages are effected: - the message is multipart with text/plain and text/html - the message uses special characters like umlauts - a non-ASCII character set (like ISO-8859-15) is used Actual results: The umlauts in the test message (see attachment) are not displayed correctly in Seamonkey 2.16. In older releases (tested with Seamonkey 2.15.2) display is correct.
|
Reporter | |
Comment 1•11 years ago
|
||
|
|
Reporter | |
Comment 2•11 years ago
|
||
|
||
Comment 3•11 years ago
|
||
Probably a DUPLICATE of: Bug 594646 - If order of http-equiv and content in <meta> is reversed(<meta content="...;charset=..." http-equiv="Content-Type">), charset in <meta> is applied to mail data coverted to utf-8. Thus, non-ascii characters are shown in garbled. I'll set a dependency to that bug.
Depends on: 594646
|
|
Reporter | |
Comment 4•11 years ago
|
||
The patch from Bug 594646 fixes the this bug. So I also guess, that this bug is a duplicate of Bug 594646.
|
||
Comment 5•11 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 SeaMonkey/2.19a1 ID:20130222003017 c-c:f10a1c2973fd m-c:885cde564ff3 When I read this email, anything above U+007F is displayed as "the UTF-8 bytecode shown as if Latin1". Hitting F5 doesn't help. When replying (in plaintext), everything is suddenly displayed as it should.
|
|
||
Updated•11 years ago
|
Status: UNCONFIRMED → NEW
status-seamonkey2.16:
--- → affected
status-seamonkey2.19:
--- → affected
Ever confirmed: true
Keywords: testcase
Whiteboard: [seamonkey 2.15-unaffected] [testcase=attachment 717463]
Version: SeaMonkey 2.16 Branch → Trunk
|
|
||
Comment 6•11 years ago
|
||
|
|
||
Comment 7•11 years ago
|
||
|
|
||
Comment 8•11 years ago
|
||
P.S. My testcase (attachment 717463 [details]) indeed includes the following inside the <HEAD> of its HTML part:
in quoted-printable:
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
which translates as the following when dequotedprintablized:
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
That testcase is a real email which I received. It has no User-Agent header but the "Display Mail User Agent" extension (version 1.6.9) identifies it as "Microsoft Windows Live Mail 15.4.3555.308", apparently from the X-Mailer header.|
|
||
Comment 9•11 years ago
|
||
P.P.S. That same HTML part has the part-email headers Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable which conflict with the <META> tag for Content-Type.
|
|
||
Comment 10•11 years ago
|
||
> The patch from Bug 594646 fixes the this bug. So I also guess, that this bug is a
> duplicate of Bug 594646.
Thanks for letting us know. Marking as DUP.
You need to log in
before you can comment on or make changes to this bug.
Description
•