Closed
Bug 845833
Opened 11 years ago
Closed 11 years ago
Wrong character visualization of messages with Cyrillic encoding windows-1251 in SeaMonkey mail after update to 2.16
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 594646
People
(Reporter: ivanov.b.c, Unassigned)
Details
Attachments
(1 file)
15.54 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 SeaMonkey/2.16 Build ID: 20130217195808 Steps to reproduce: I've updated to SeaMonkey 2.16. After update there's a wrong visualization of messages with charset="windows-1251" encoding. Both new incoming and old sent messages. All my message folders are with default character encoding windows-1251. I've tried to visualize them correctly using View->Character Encoding->Windows 1251. The problem even exists after editing a message with Message->Edit As New. Actual results: I still can not get the right visualization of characters in the messages.
Comment 1•11 years ago
|
||
Probably a duplicate of Bug 594646
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•11 years ago
|
||
Hi guys, This bug really annoying me. I'm an old-fashioned Netscape user (Do you remeber Netscape) and don't want to deal with any MS or other mail client ****. So please just fix the **** bug, so I can do some of my work.
Comment 3•11 years ago
|
||
(In reply to Borislav Ivanov from comment #2) > Hi guys, > > This bug really annoying me. I'm an old-fashioned Netscape user (Do you > remeber Netscape) and don't want to deal with any MS or other mail client > ****. So please just fix the **** bug, so I can do some of my work. That is being looked into, but it isn't as simple as snapping fingers. Bug 594646 already has 11 duplicates (including this one), and more are coming in every so often, which makes it obvious to anyone looking at it that it has become a sore spot. Workaround: View → Message Body as → Simple HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•