Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: \201 problem reproduced
Date: 12 Sep 1998 18:24:28 +0400	[thread overview]
Message-ID: <m3ww799zoj.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "12 Sep 1998 08:24:08 +0200"

"LMI" == Lars Magne Ingebrigtsen writes:

 >> I do not know, but there are e.g. three cyrillic language
 >> environments defined in MULE: Cyrillic-KOI8, Cyrillic-ISO,
 >> Cyrillic-ALT. May be, person who uses Cyrillic-ISO would prefer
 >> his letters to be sent encoded iso-8859-5, but those of us using
 >> Cyrillic-KOI8, would like to send messages encoded with
 >> koi8-r. Semi-gnus somehow knew about this, and did not try to use
 >> iso-8859-5 at all. :-)
 LMI> Could you try to investigate how semi-gnus finds this out?

I'll try, but for now, i'd like to ask one question. ;-)

The mm-util.el from pgnus contains the following:

(defvar mm-mime-mule-charset-alist
  '((us-ascii ascii)
    (iso-8859-1 latin-iso8859-1)
    (iso-8859-2 latin-iso8859-2)
    (iso-8859-3 latin-iso8859-3)
    (iso-8859-4 latin-iso8859-4)
    (iso-8859-5 cyrillic-iso8859-5)
    (koi8-r cyrillic-iso8859-5)
    (iso-8859-6 arabic-iso8859-6)
    (iso-8859-7 greek-iso8859-7)
[the rest skipped]

Note the presence of two lines corresponding to cyrillic-iso8859-5
mule charset:

    (iso-8859-5 cyrillic-iso8859-5)
    (koi8-r cyrillic-iso8859-5)

I wonder, does the first line override the second one??? I suppose
that if i'll remove the line

    (iso-8859-5 cyrillic-iso8859-5)

then gnus will use koi8-r by befault (and btw koi8-r is a de-facto
standard for russian e-mail exchange anyway; the presence of two
mappings for one mule encoding does not seem useful anyway btw, --- is
it a bug?).

	Best regards, -- Vladimir.
-- 
Stability itself is nothing else than a more sluggish motion.


  reply	other threads:[~1998-09-12 14:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-08 19:35 Lars Magne Ingebrigtsen
1998-09-09 18:04 ` Vladimir Volovich
1998-09-10  0:28   ` Lars Magne Ingebrigtsen
1998-09-10  9:27     ` Vladimir Volovich
1998-09-11  6:29       ` Lars Magne Ingebrigtsen
1998-09-11 22:33         ` Vladimir Volovich
1998-09-12  6:24           ` Lars Magne Ingebrigtsen
1998-09-12 14:24             ` Vladimir Volovich [this message]
1998-09-12 15:05               ` Vladimir Volovich
1998-09-12 19:07             ` Vladimir Volovich
1998-09-12 21:32               ` Hallvard B Furuseth
1998-09-13  5:55                 ` Lars Magne Ingebrigtsen
1998-09-13  9:00                   ` Vladimir Volovich
2002-10-20 23:16                     ` Lars Magne Ingebrigtsen
1998-09-13 13:19                       ` Vladimir Volovich
1998-09-14  6:17                         ` Lars Magne Ingebrigtsen
1998-09-14 18:45                           ` Vladimir Volovich
1998-09-16  9:14                             ` Lars Magne Ingebrigtsen

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=m3ww799zoj.fsf@vvv.vsu.ru \
    --to=vvv@vvv.vsu.ru \
    /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).