From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/5634 Path: news.gmane.org!not-for-mail From: Peter Simons Newsgroups: gmane.emacs.gnus.user Subject: Re: Strange charset selection when posting in iso-8859-1 Date: 05 Sep 2005 13:21:11 +0200 Organization: private Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138671331 28246 80.91.229.2 (31 Jan 2006 01:35:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:35:31 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:35:36 2006 Original-Path: quimby.gnus.org!newsfeed.gazeta.pl!fu-berlin.de!newsfeed.arcor.de!news.arcor.de!not-for-mail Original-Sender: simons@write-only.cryp.to Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Date: 05 Sep 2005 13:21:11 MEST Original-NNTP-Posting-Host: b494a575.newsread4.arcor-online.net Original-X-Trace: DXC=UaeN_KPGC_b0_l3b[L=KQc:ejgIfPPlddjW\KbG]kaMhea\9g\;7Nme@I;EfX\P3hjC8]WRNfV_jn;J?Rj`U Reiner Steib writes: >> The problem started to appear after I added >> >> (setq-default enable-multibyte-characters nil) >> >> to my ~/.emacs file. Now, I don't want multi-byte mode >> enabled, > > Why? Because I had lots of trouble with Emacs choosing weird encodings for _all_ kind of files when I had it enabled. > Gnus doesn't work correctly in unibyte mode, AFAIK. Well, using the proper charset identifiers as defined in RFC1521 would fix the problem for me, as far as I can tell. I don't see why that wouldn't be possible. What is the rationale behind a choice like "latin1-iso-8859-1"? Isn't that a pleonasm anyway? Peter