From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: mm-coding-system-priorities per hierarchy
Date: Sun, 24 Sep 2006 15:21:07 +0200 [thread overview]
Message-ID: <v9slihtn7g.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4md59oxpmy.fsf@jpl.org>
On Fri, Sep 22 2006, Katsumi Yamaoka wrote:
>>>>>> Reiner Steib wrote:
>> When using this expression...
>
>> (add-to-list 'gnus-newsgroup-variables 'mm-coding-system-priorities)
>
>> ... `gnus-summary-make-local-variables' sets the global value of
>> `mm-coding-system-priorities' to nil. I'd guess nil leads to utf-8
>> instead of iso-2022-jp in your environment.
>
> No, it is not caused by the nil value.
IIRC, if `mm-coding-system-priorities' is nil, Gnus uses Emacs'
`sort-coding-systems' to find the suitable charset. So my guess was
that utf-8 is preferred to iso-2022-jp...
,----
| $ LC_ALL=C emacs -nw -Q -f ielm
|
| ELISP> current-language-environment
| "ASCII"
| ELISP> (sort-coding-systems '(iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8))
| (iso-8859-1 iso-2022-jp shift_jis utf-8 iso-2022-jp-2)
|
| ELISP> (set-language-environment "Japanese")
| t
| ELISP> (sort-coding-systems '(iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8))
| (iso-2022-jp shift_jis iso-8859-1 utf-8 iso-2022-jp-2)
`----
But maybe...
,----
| $ LC_ALL=jp_JP.utf8 emacs -nw -Q -f ielm
|
| ELISP> (sort-coding-systems '(iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8))
| (utf-8 iso-2022-jp shift_jis iso-8859-1 iso-2022-jp-2)
`----
>> Do you get the expected behavior with this expression?
>
>> (add-to-list 'gnus-newsgroup-variables
>> '(mm-coding-system-priorities . global))
>
> That is not good for me. It should be the following:
>
> (add-to-list
> 'gnus-newsgroup-variables
> '(mm-coding-system-priorities
> . '(iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8)))
>
> The value here is the default value of `mm-coding-system-priorities'
> in the Japanese language environment.
My understanding is that `global' is supposed to take this value. Is
it a bug (in gnus-sum.el) or am I missing something?
> Though it is insufficient for me even if I do so.
>
> If I set `gnus-parameters' (as you suggested) in addition to
> this, the value of `mm-coding-system-priorities' is changed into
> (iso-8859-1 iso-8859-15 utf-8) when I enter to a DE newsgroup.
> It is useful for posting German messages there (it is highly
> unlikely with me, though ;-). However, I should not send
> Japanese mails in there even if I recall an urgent business. It
> is because `iso-2022-jp', which is used for Japanese messages
> traditionally, is not preferred when encoding Japanese text.
>
> It is possible to send Japanese messages safely after I exit the
> DE group, isn't it? *No*. `mm-coding-system-priorities' still
> has the value (iso-8859-1 iso-8859-15 utf-8) at that time. The
> value will not contain `iso-2022-jp' until I enter to a FJ group
> or a group that is not listed in `gnus-parameters'.
>
> What I'd like to say is that a similar problem will probably
> happen with people who are not in the Japanes language
> environment as well. Group parameter is useful to things
> associated to group, however messages are not always associated
> to group.
I think it is (also?) a bug if entering a group modifies the
default-value of a variable. It probably should only modify the local
values in the summary, article and message buffers for the matching
groups.
The code of `gnus-summary-make-local-variables' seems to be correct.
Maybe `gnus-set-global-variables' or some other function is the
culprit?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-09-24 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 16:42 Reiner Steib
2006-09-20 22:55 ` Katsumi Yamaoka
2006-09-21 14:01 ` Reiner Steib
2006-09-22 8:38 ` Katsumi Yamaoka
2006-09-24 13:21 ` Reiner Steib [this message]
2006-09-25 11:36 ` Katsumi Yamaoka
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=v9slihtn7g.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--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).