Groups | Search | Server Info | Login | Register
Groups > alt.comp.software.seamonkey > #6514
| From | Richmond <dnomhcir@gmx.com> |
|---|---|
| Newsgroups | alt.comp.software.seamonkey |
| Subject | Re: The default text encoding for message display |
| Date | 2024-06-19 21:33 +0100 |
| Organization | Frantic |
| Message-ID | <86cyocllkj.fsf@example.com> (permalink) |
| References | <861q4t45m7.fsf@example.com> <v4vc3m$24grc$1@dont-email.me> |
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.
Back to alt.comp.software.seamonkey | Previous | Next — Previous in thread | Next in thread | Find similar
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
csiph-web