Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Gnus doesn't load with Unicode chars in .gnus.el
Date: Thu, 12 Feb 2004 11:32:00 +0100	[thread overview]
Message-ID: <v9hdxwd1wf.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87fzdgeit8.fsf@caracolito.lan>

On Thu, Feb 12 2004, Artem Baguinski wrote:

> Jørn Helge B. Dahl <jornd@users.sourceforge.net> writes:
[...]
>> I have a UTF-8-enabled locale, and I use
>>
>>   (setq locale-coding-system 'utf-8)
>>   (set-terminal-coding-system 'utf-8)
>>   (set-keyboard-coding-system 'utf-8)
>>   (set-selection-coding-system 'utf-8)
>>   (prefer-coding-system 'utf-8)
>
> i think just having utf-8 locale is enough, 

Often people change too many of the *-coding-system-* stuff without
being aware of the consequences and run into problems later.  Usually
it's enough to set the systems locale or use
`set-language-environment' in Emacs.

> because [having used emacs / gnus only a week and not knowing much
> configuration options yet] i simply pasted the fragment with unicode
> arrows into my .gnus and it worked right away.

This depends only on the coding used for reading the .gnus.el file
(using a cookie as suggested, or putting the Unicode arrows stuff in a
separate file including a cookie).  

The locale and coding settings in Emacs are independent of this.  You
can use Unicode arrows in the summary with any locale and coding
system settings (e.g. I use a Latin-1 locale).

> hmm... that sounds useful: many of my russian friends prefer letters
> in koi8, i guess i can make it 
>
>   (setq mm-coding-system-priorities '(iso-8859-1 koi-8 utf-8))
>
> then... or i have to find how to say "koi8" in emacsish...

In the Summary buffer, `1 g koi TAB TAB' will give you a list of
available charsets.  I guess you want "koi8-r".  In
`mm-coding-system-priorities' you can use MIME charsets (in Gnus 5.10,
not in earlier Oort versions and 5.8/5.9) or Emacs coding systems.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/


  parent reply	other threads:[~2004-02-12 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87smhjj8hi.fsf@rechner1.ddorf.de>
     [not found] ` <87ekt3m5cp.fsf@users.sourceforge.net>
2004-02-11 21:39   ` nice summary-format Ted Zlatanov
     [not found]   ` <4noes5lid9.fsf@collins.bwh.harvard.edu>
     [not found]     ` <878yj98s8e.fsf@users.sourceforge.net>
     [not found]       ` <87fzdgeit8.fsf@caracolito.lan>
2004-02-12 10:32         ` Reiner Steib [this message]
2004-02-12 14:27           ` Gnus doesn't load with Unicode chars in .gnus.el Fabian Braennstroem
     [not found]             ` <v9n07ofkbx.fsf@marauder.physik.uni-ulm.de>
     [not found]               ` <87bro4dnhp.fsf@rechner1.ddorf.de>
2004-02-12 20:00                 ` Reiner Steib
     [not found]                   ` <873c9fhnxo.fsf@rechner1.ddorf.de>
2004-02-13  8:58                     ` Reiner Steib
     [not found]                       ` <87d68j41it.fsf@rechner1.ddorf.de>
2004-02-14 16:47                         ` Fabian Braennstroem
     [not found]           ` <4nfzdg4ipu.fsf@collins.bwh.harvard.edu>
2004-02-12 14:30             ` Reiner Steib

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v9hdxwd1wf.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).