Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.software.seamonkey > #6512 > unrolled thread

The default text encoding for message display

Back to article view | Back to alt.comp.software.seamonkey

Contents

  The default text encoding for message display Richmond <dnomhcir@gmx.com> - 2024-06-19 10:57 +0100
    Re: The default text encoding for message display Mark Bourne <nntp.mbourne@spamgourmet.com> - 2024-06-19 20:38 +0100
      Re: The default text encoding for message display Richmond <dnomhcir@gmx.com> - 2024-06-19 21:33 +0100
        Re: The default text encoding for message display Nuno Silva <nunojsilva@invalid.invalid> - 2024-06-20 11:05 +0100

#6512 — The default text encoding for message display

If I post an article to uk.test I get an email response including the
text of the article. When the article contains utf-8 characters they are
not displayed properly in the email with seamonkey. I think this is
because the email does not specify the encoding in its headers. So I
check in the settings for seamonkey and it says to use the default
encoding for the system, which on my debian system is LANG=en_GB.UTF-8

So why did the message not display properly? If I select the message and
check View -> Text -> Encoding it says "Western", and changing it to
unicode corrects the problem, at least temporarily.

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.18.2

[toc] | [next] | [standalone]

#6513

Richmond wrote:
> If I post an article to uk.test I get an email response including the
> text of the article. When the article contains utf-8 characters they are
> not displayed properly in the email with seamonkey. I think this is
> because the email does not specify the encoding in its headers. So I
> check in the settings for seamonkey and it says to use the default
> encoding for the system, which on my debian system is LANG=en_GB.UTF-8

Does it work any better if you explicitly select "Unicode (UTF-8)" as 
the fallback encoding, rather than "Default for Current Locale"?  Just 
wondering if perhaps SeaMonkey isn't detecting your system encoding as 
being UTF-8.  Also make sure you're looking at the fallback encoding for 
display, and not the default used for composing messages.

> So why did the message not display properly? If I select the message and
> check View -> Text -> Encoding it says "Western", and changing it to
> unicode corrects the problem, at least temporarily.
> 
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
> Firefox/91.0 SeaMonkey/2.53.18.2

The headers of your message here, that I'm replying to, include:

Content-Type: text/plain

...with no character encoding, presumably similar to your test message. 
I can't tell whether it's actually rendered correctly as UTF-8, since I 
don't think there are any non-ASCII characters, but for me View > Text 
Encoding has  "Unicode" selected without having manually changed it.  In 
SeaMonkey's preferences, under Mail & Newsgroups > Text Encoding, I have:
* Message Display: Fallback Text Encoding: Default for Current Locale
* Composing Messages: Default Text Encoding: Unicode (UTF-8)

My user agent is:
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 SeaMonkey/2.53.18.2
...so basically the same as yours, except I have it set to identify as 
SeaMonkey without advertising Firefox compatibility.  Mine is installed 
from the UbuntuZilla repositories, in case that makes any difference.

One thing I do find is that, when reading messages in the "Message Pane" 
rather than opening them in a separate window, they are sometimes 
initially displayed with the wrong encoding, but hiding and re-showing 
the Message Pane (press F8 a couple of times) fixes that.

-- 
Mark.

[toc] | [prev] | [next] | [standalone]

#6514

Mark Bourne <nntp.mbourne@spamgourmet.com> writes:

> Does it work any better if you explicitly select "Unicode (UTF-8)" as
> the fallback encoding, rather than "Default for Current Locale"?  Just
> wondering if perhaps SeaMonkey isn't detecting your system encoding as
> being UTF-8.  Also make sure you're looking at the fallback encoding
> for display, and not the default used for composing messages.

Yes it does work better if I do that.

> The headers of your message here, that I'm replying to, include:

I didn't post with Seamonkey here, but it wasn't the posting which was
the issue, it was displaying an incoming email.

> One thing I do find is that, when reading messages in the "Message
> Pane" rather than opening them in a separate window, they are
> sometimes initially displayed with the wrong encoding, but hiding and
> re-showing the Message Pane (press F8 a couple of times) fixes that.

Yes same here. I guess it doesn't matter if I can set the default
encoding, but what was the default encoding if it wasn't the system
default?

This character:

—

should make gnus put a utf-8 header.

[toc] | [prev] | [next] | [standalone]

#6515

On 2024-06-19, Richmond wrote:

> Mark Bourne <nntp.mbourne@spamgourmet.com> writes:
>
>> Does it work any better if you explicitly select "Unicode (UTF-8)" as
>> the fallback encoding, rather than "Default for Current Locale"?  Just
>> wondering if perhaps SeaMonkey isn't detecting your system encoding as
>> being UTF-8.  Also make sure you're looking at the fallback encoding
>> for display, and not the default used for composing messages.
>
> Yes it does work better if I do that.
>
>> The headers of your message here, that I'm replying to, include:
>
> I didn't post with Seamonkey here, but it wasn't the posting which was
> the issue, it was displaying an incoming email.

And posting normally doesn't have this issue, it is only happening when
that group sends you back a copy of the post?

>> One thing I do find is that, when reading messages in the "Message
>> Pane" rather than opening them in a separate window, they are
>> sometimes initially displayed with the wrong encoding, but hiding and
>> re-showing the Message Pane (press F8 a couple of times) fixes that.
>
> Yes same here. I guess it doesn't matter if I can set the default
> encoding, but what was the default encoding if it wasn't the system
> default?
>
> This character:
>
> —
>
> should make gnus put a utf-8 header.

It did :-)

-- 
Nuno Silva

[toc] | [prev] | [standalone]

Back to top | Article view | alt.comp.software.seamonkey

csiph-web