Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Richmond Newsgroups: alt.comp.software.seamonkey Subject: Re: The default text encoding for message display Date: Wed, 19 Jun 2024 21:33:16 +0100 Organization: Frantic Message-ID: <86cyocllkj.fsf@example.com> References: <861q4t45m7.fsf@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: solani.org; logging-data="1977835"; mail-complaints-to="abuse@news.solani.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Cancel-Lock: sha1:mBV2bielLWI1gXShDzAHZ38W7VQ= sha1:OAVlID/QJ4hee61rZTQt641bOCE= X-User-ID: eJwNyskBwCAIBMCWFFmOcsgi/Zdg5j04to2uBlMMhoL4bikSxWnPwOm7Vk0w+p+SxU3RoULCHywBEXE= Xref: csiph.com alt.comp.software.seamonkey:6514 Mark Bourne 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.