Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: moderator@faqteam.org (Vasily Korytov)
Subject: Re: reading cyrillic with gnus
Date: Wed, 14 Aug 2002 21:25:42 +0400	[thread overview]
Message-ID: <874rdxs67d.fsf@unix.home> (raw)
In-Reply-To: <s93vg6d69gh.fsf@cheusov.scnsoft.com>

>>>>> "c" == cheusov  writes:

 >> for _sent_ messages, use gnus-group-posting-charset-alist.

 c> Doesn't matter.

 c> After (setq gnus-group-posting-charset-alist
 c> (quote (("fido7" koi8-r (koi8-r)) (message-this-is-mail (koi8-r)
 c> (koi8-r)) (message-this-is-news nil t))))

 c> the message has been sent in UTF-8 again.

Strange. I have good expierence of using Gnus in Emacs 21.1/Mule and
XEmacs 21.1 and 21.4 non-Mule, while setting really a few variables (I
am a Russian user and I do read and post in fido7.* every morning along
with my cup of coffee).

I believe, all my related settings are:

(setq gnus-group-charset-alist '((".*" koi8-r))

      gnus-group-posting-charset-alist
      '((message-this-is-news koi8-r (koi8-r))
	(message-this-is-mail nil (koi8-r)))

      mm-body-charset-encoding-alist '((koi8-r . 8bit))
      message-default-charset 'koi8-r)

Plus this construction to make Mule happy:
(put-charset-property 'cyrillic-iso8859-5
                      'preferred-coding-system 'koi8-r)

NB: My setup does not include any references to other charsets (I don't
use them) or Mule-specific stuff to force KOI-8 (I have set up KOI8-R
env. in Mule by default, so I don't need to override it -- I even don't
know, if it's needed).

-- 
	Vas.


  reply	other threads:[~2002-08-14 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m31y93bre3.fsf@gmx.net>
     [not found] ` <87n0rrutpw.fsf@unix.home>
     [not found]   ` <s93adnqn1ho.fsf@cheusov.scnsoft.com>
2002-08-13 17:41     ` Vasily Korytov
2002-08-14 10:06       ` cheusov
2002-08-14 17:25         ` Vasily Korytov [this message]
2002-08-14 15:15 ` Ted Zlatanov

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=874rdxs67d.fsf@unix.home \
    --to=moderator@faqteam.org \
    /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).