Nuno Silva wrote on 05/03/2019 21:32:
On 2019-03-05, Rubens wrote:
Rubens wrote:
I am receiving some Unicode-encoded e-mails which look garbled because
Seamonkey always try to display them with Western encoding in the first place,
so I always have to manually change the Text Encoding option for every Unicode
e-mail I read.
In the "Text Encoding - Message Display" preferences setting I
tried both the "Default for current locale" and the "Other
(including Western European)"
but none gets what I need (to force opening every e-mail in Unicode viewing
mode).
Can anybody help ? My Seamonkey version is 2.49.4, language UK
English and my OS is Windows 7Â Pro 64-bit, language US English.
[...]
Hi guys, any more ideas on this ? It is really annoying to have to change
setting for every read e-mail.
I don't have a solution to offer, but what you describe sounds
slightly strange.
I have seen broken e-mail messages, where some piece of software manages
to do something in a wrong way, and one thing that can go wrong is the
content encoding. But, when this happens, you'd only see the problem in
messages sent using that software, and not in all messages. This is
what sounds strange to me. Can you confirm that this problem occurs with
*all* messages? Or, at least, all e-mail messages? (I'll add some
unicode-only characters just before the signature so that you can check
whether this post is affected by the same problem.)
It might be that there is some setting I'm not aware of, that does
exactly what you are looking for (a way to force a given encoding), and
it is currently set to the "wrong" encoding.
Are you using anything that intercepts e-mail messages before they reach
Seamonkey? (I believe some "internet security" software packages offer
this as a feature.)
Open/select one of the affected messages and look at its source (CTRL+U
or "View->Message Source"). Can you locate the problematic text?
If so, could you please copy the content of the latest Content-Type
header that precedes it? This should be one line beginning with
"Content-Type: ", possibly followed by more lines beginning with space
or tab (I believe I got this right, somebody please correct me if I'm
wrong...), like this:
Content-Type: text/plain;
charset=utf-8
What I am curious about is the charset=... part of the header.
While you are viewing the source, please copy the User-Agent header as
well, if it exists.
Unicode characters:
- trademark mark: â„¢
- superscript 9: â¹
- :-) smiley: ☺
Hi Nuno,
Below follow my findings, answers and comments to your questions:
1- No, the problem does not afect *all* messages, but most of them (around 95%)
For any message incorrectly displayed, changing the viewing mode from
Western to Unicode *always* correct that.
Unfortunately the Unicode mode setting does not stick for messages (as it
does for the browser).
2- No, I am not using any software which may intercept the messages.
3- The problem occurs for both e-mail and newsgroup messages, including this
post you have just sent me.
4- Yes, the message source view display the problematic (Unicode) characters in
the same way as the normal message display.
Interestingly, for some messages in the source window, changing the setting
to Unicode also corrects the characters display.
5- The content line for the problematic messages is exactly the same as you
have written:
Content-Type: text/plain; charset=utf-8
6- The user agent header for your post is:
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
7- The Unicode characters you have inserted clearly reproduce the problem, they
are displayed incorrectly
in the Western viewing mode.
NOTE: I noticed this problem has been increasing over the years, with more and
more operating systems and e-mail client programs
being able to encode messages in Unicode.
O.S. INFO: I am using Windows 7 Pro 64-bit (English version) with locale and
language set to Brazilian Portuguese.
Thanks for you help.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
