From: Andrei Elkin <astro@sbor.ru>
Cc: bugs@gnus.org
Subject: mime-charset determination
Date: 20 Aug 2000 22:21:45 +0400 [thread overview]
Message-ID: <m3k8dbn686.fsf@himmel.dune.ru> (raw)
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 (Русский) Здравствуйте!
Input methods (default, cyrillic-jcuken):
Character sets:
cyrillic-iso8859-5: ISO8859-5 (Cyrillic)
Coding systems:
cyrillic-koi8 (`R' in mode line):
KOI8 8-bit encoding for Cyrillic (MIME: KOI8-R)
(alias: koi8-r koi8)
And my evelope has
Content-Type: text/plain; charset=iso8859-5
insteed of my precious =koi8-r
If fact `mm-find-mime-charset-region','mm-mime-charset' try to find
out mime-charset value via `Character sets' one.
But should do it thru coding-system (as it said in mule.el).
Yes, my charset is cyrillic-iso8859-5. But
(coding-system-get
(mm-preferred-coding-system charset) 'mime-charset)
in 'mm-mime-charset' body get that wrong Content-Type as
`mm-prefer-coding-system' value is cyrillic-iso8859-5.
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.
Emacs ver GNU Emacs 20.5.1 (i386-redhat-linux-gnu, X toolkit)
of Tue Feb 22 2000 on porky.devel.redhat.com
is run on Linux kernel 2.2.14 in unibyte mode.
______________
Andrei.Elkin
P.S this message was posted with the new definition, so should have
Content-Type: text/plain; charset=koi8-r
next reply other threads:[~2000-08-20 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-20 18:21 Andrei Elkin [this message]
2000-08-20 18:38 ` ShengHuo ZHU
[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=m3k8dbn686.fsf@himmel.dune.ru \
--to=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).