Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: changing gnus-group-posting-charset-alist
Date: Fri, 15 Oct 2004 19:30:00 +0900	[thread overview]
Message-ID: <b9yoej4ff4n.fsf@jpl.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]

Hi,

I'm wondering for years about the default value for the
gnus-group-posting-charset-alist variable.

| gnus-group-posting-charset-alist's value is
| (("^\\(no\\|fr\\)..." iso-8859-1 (iso-8859-1))
|  ("^\\(fido7\\|relcom\\)..." koi8-r (koi8-r))
|  (message-this-is-mail nil nil)
|  (message-this-is-news nil t))
|
| Alist of regexps and permitted unencoded charsets for posting.
| Each element of the alist has the form (TEST HEADER BODY-LIST), where
| TEST is either a regular expression matching the newsgroup header or a
| variable to query,
| HEADER is the charset which may be left unencoded in the header (nil
| means encode all charsets),
| BODY-LIST is a list of charsets which may be encoded using 8bit
| content-transfer encoding in the body, or one of the special values
| nil (always encode using quoted-printable) or t (always use 8bit).
|
| Note that any value other than nil for HEADER infringes some RFCs, so
| use this option with care.

Is it still necessary not to encode text by qp or something to
post news articles to no, fr, fido7 and relcom newsgroups?  I
don't use Norwegian, French or Russian, so it isn't my business,
though.

As for other newsgroups, Gnus forces the 8bit encoding especially
to news articles' body by default.  Isn't it a vestige of the
time when Gnus had not been multiligualized?  It is hard for me
to imagine there's a difference between mail and news.  What I'd
like to say is: let's change the default value to:

(message-this-is-news nil nil)

Almost Japanese text which I write can be encoded by iso-2022-jp
and 7bit.  So, those text will be posted as 7bit articles.
However, I sometimes followup to articles containing characters
which cannot be encoded by 7bit.  In those cases, text will be
encoded by shift_jis, utf-8 and so forth and fed to the server
without being encoded with qp or base64.  A newsreader posting
such articles may be only Gnus nowadays.  Therefore, I make it a
rule to recommend Japanese users to modify the value as follows:


[-- Attachment #2: Type: application/emacs-lisp, Size: 211 bytes --]

[-- Attachment #3: Type: text/plain, Size: 7 bytes --]


WDYT?

             reply	other threads:[~2004-10-15 10:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15 10:30 Katsumi Yamaoka [this message]
2004-10-15 16:51 ` Jesper Harder
2004-10-15 23:30   ` Katsumi Yamaoka
2004-10-17 23:57     ` Katsumi Yamaoka
2004-10-18 20:35 ` Jesper Harder
2004-10-19  0:51   ` 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=b9yoej4ff4n.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).