From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: posting-charset abolition
Date: Wed, 30 Oct 2002 22:15:56 +0900 [thread overview]
Message-ID: <yotlof9c9ier.fsf@jpl.org> (raw)
Hi,
I'm planning to make a proposal to abolish the group parameter
posting-charset-alist and the variable message-posting-charset.
I write a story from the beginning:
Gnus always puts the ``Content-Transfer-Encoding: 8bit'' header
into news articles to be sent by default. Since Japanese news
articles use the iso-2022-jp charset normally, putting CTE: 8bit
is nonsense (iso-2022-jp never uses 8-bit data). It is caused by
the default value for the posting-charset-alist group parameter,
which contains the element (message-this-is-news nil t). See
the docstring for the variable gnus-group-posting-charset-alist
for details.
By default, the iso-8859-1 charset is used for posting news
articles to Norwegian or French newsgroups. However, please
consider. Though it is unlikely to post a Japanese article to a
Norwegian group, a posting-charset should be determined by
article contents rather than a newsgroup name. Even if there is
a candidate of two or more charsets for article contents, we can
decide the priorities by the option mm-coding-system-priorities.
I am anxious about the following info description:
When posting, `gnus-group-posting-charset-alist' is used to
determine which charsets should not be encoded using the MIME
encodings. For instance, some hierarchies discourage using
quoted-printable header encoding.
Do such newsgroups exist even now?
By the way, now I'm using the following code not to add the
CTE: 8bit header to news articles:
(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 reply other threads:[~2002-10-30 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 13:15 Katsumi Yamaoka [this message]
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
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=yotlof9c9ier.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).