From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: posting-charset abolition
Date: Fri, 01 Nov 2002 21:33:21 +0900 [thread overview]
Message-ID: <yotl8z0d8o6m.fsf@jpl.org> (raw)
In-Reply-To: <yotl3cql7lc5.fsf@jpl.org>
>>>>> In <yotl3cql7lc5.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>>>>>> In <m37kfxsryu.fsf@defun.localdomain>
>>>>>> Jesper Harder <harder@ifa.au.dk> wrote:
>> What do you think about this fix?
> Wow! That's just the thing, maybe. Since I didn't have time to
> look at a code recently, I will confirm your change later and
> use it. Thanks a lot!
I've confirmed that it is perfect. I've just committed it.
However, the variable gnus-group-posting-charset-alist became
important in another viewpoint in Japanese news articles.
Hey Japanese folks, look at this!
In GNUS v3 or v4 era, posting 8-bit news articles was considered
to be evil in Japanese newsgroups because newsreaders or news
servers were not supporting it. Though it won't be in such a
condition today, 8-bit news articles still tend to be base64
encoded. If you don't desire to send 8-bit news articles and
there is an opportunity of writing katakana-jisx0201 (may be
called as hankaku-katakana) or any other special characters, the
following setting is also effective even now:
(eval-after-load "gnus-msg"
'(if (boundp 'gnus-group-posting-charset-alist)
(let ((news (assq 'message-this-is-news
gnus-group-posting-charset-alist)))
(if news
(setcdr news '(nil nil))))))
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2002-11-01 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 13:15 Katsumi Yamaoka
2002-10-31 9:12 ` Katsumi Yamaoka
2002-10-31 11:34 ` Ted Zlatanov
2002-10-31 12:38 ` Katsumi Yamaoka
2002-10-31 14:30 ` Ted Zlatanov
2002-11-01 2:43 ` Katsumi Yamaoka
2002-11-01 3:07 ` Ted Zlatanov
2002-11-01 6:51 ` Jesper Harder
2002-11-01 8:20 ` Katsumi Yamaoka
2002-11-01 12:33 ` Katsumi Yamaoka [this message]
2002-11-01 14:18 ` Jesper Harder
2002-11-01 15:54 ` Katsumi
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=yotl8z0d8o6m.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).