Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Cc: astro@sbor.ru, bugs@gnus.org
Subject: Re: mime-charset determination
Date: 20 Aug 2000 14:38:59 -0400	[thread overview]
Message-ID: <5bya1rn5fg.fsf@finch.cs.rochester.edu> (raw)
In-Reply-To: Andrei Elkin's message of "20 Aug 2000 22:21:45 +0400"

Andrei Elkin <astro@sbor.ru> writes:

> Current (5.8.7 for me) version provides the definitions of
> `mm-find-mime-charset-region','mm-mime-charset' that seems to be incorrect.
> 
> For example my C-h L RET gives:
> 
>      Cyrillic-KOI8 language environment
> 
>      Support for Cyrillic KOI8-R.
> 
>      Sample text:
>      Russian (Русский)	Здравствуйте!
> 

[...]

> I found out that `select-message-coding-system' works correctly
> (resulting with cyrillic-koi8). So the situation becomes nice for me
> with a redefinition of  
> 
> (defun mm-find-mime-charset-region (b e)
>   (let ((mime-charset  
>          (coding-system-get (select-message-coding-system) 'mime-charset)))
>     (if (listp mime-charset) mime-charset (list mime-charset))))
> 
> that dont need for 'mm-mime-charset' at all.

select-message-coding-system might not be the answer for all
situations, especially when a message contains characters in the
charset other than the default one.

Anyway, the solution for KOI8-R encoding is

 (if (fboundp 'put-charset-property)
    (put-charset-property 'cyrillic-iso8859-5
                          'preferred-coding-system 'koi8-r))


ShengHuo



  reply	other threads:[~2000-08-20 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-20 18:21 Andrei Elkin
2000-08-20 18:38 ` ShengHuo ZHU [this message]
     [not found] <m37l9b2o5t.fsf@himmel.dune.ru>
2000-08-21 12:22 ` elkin
2000-08-21 13:29   ` Roman Belenov
2000-08-21 18:43   ` Andrei Elkin

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=5bya1rn5fg.fsf@finch.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    --cc=astro@sbor.ru \
    --cc=bugs@gnus.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).