From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: mm-coding-system-priorities per hierarchy
Date: Fri, 22 Sep 2006 17:38:13 +0900 [thread overview]
Message-ID: <b4md59oxpmy.fsf@jpl.org> (raw)
In-Reply-To: <v9odt92u9c.fsf@marauder.physik.uni-ulm.de>
>>>>> In <v9odt92u9c.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib wrote:
> On Thu, Sep 21 2006, Katsumi Yamaoka wrote:
>> This has to be used with care. I verified that the Japanese
>> mail message written when the de.test group was selected or just
>> after exiting the de.test group was sent with the utf-8 encoding
>> even if iso-2022-jp is better to be used.
> I think the documentation of `gnus-newsgroup-variables' should
> actually be improved and it should describe what
> `gnus-summary-make-local-variables' does [1] (or maybe I just didn't
> read the doc string carefully enough [2]):
I had learned how those group-local variables work by reading
the source code.
> 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.
> 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. 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.
Regards,
next prev parent reply other threads:[~2006-09-22 8:38 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 [this message]
2006-09-24 13:21 ` Reiner Steib
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=b4md59oxpmy.fsf@jpl.org \
--to=yamaoka@jpl.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).