From: Florian Weimer <fw@s.netic.de>
Subject: Re: de .* and gnus-group-posting-charset-alist
Date: 21 Dec 1999 21:23:40 +0100 [thread overview]
Message-ID: <87r9ggm4ab.fsf@deneb.cygnus.argh.org> (raw)
In-Reply-To: Florian Weimer's message of "21 Dec 1999 00:22:35 +0100"
Okay, here it is:
1999-12-21 Florian Weimer <fw@s.netic.de>
* gnus-msg.el (gnus-group-posting-charset-alist): New layout.
(gnus-setup-message): No longer make `message-posting-charset'
buffer-local.
(gnus-setup-posting-charset): Reflect the new layout of
`gnus-group-posting-charset-alist' and `message-posting-charset'.
* message.el (message-send-mail): Bind `message-this-is-mail' and
`message-posting-charset'.
(message-send-news): Dito, and honour new layout of
`message-posting-charset'.
(message-encode-message-body): Ignore `message-posting-charset'.
* mm-bodies.el (mm-body-encoding): Consider
`message-posting-charset' when deciding whether to use 8bit.
* rfc2047.el (rfc2047-encode-message-header): Back out change.
(rfc2047-encodable-p): Now solely for headers; use
`message-posting-charset'.
`message-posting-charset' is now a list of the form
(HEADER-CHARSET BODY-CHARSETS...). It's still taken from
`gnus-group-posting-charset-alist'. If HEADER-CHARSET is nil, 8-bit
characters are always encoded in the header. Otherwise, HEADER-CHARSET
is a symbol which denotes the charset which is to be left unencoded
(blechhh!). BODY-CHARSETS is either t (which means: always use 8-bit
encoding) or a list of symbols naming charsets which can be encoded
using 8-bit (other charsets will be encoded as quoted-printable).
The special value nil indicates that quoted-printable should be used
for all charsets.
I sincerely hope that this will find its way into 5.8.3. Some stuff like
this is certainly required to solve this nasty problem once and for all.
next prev parent reply other threads:[~1999-12-21 20:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-07 20:45 Karl EICHWALDER
1999-12-08 6:50 ` Florian Weimer
1999-12-11 20:20 ` Kai Großjohann
1999-12-12 6:39 ` Karl EICHWALDER
1999-12-12 9:22 ` Florian Weimer
1999-12-12 11:46 ` Bjørn Mork
1999-12-13 12:04 ` Christophe Cuq
1999-12-12 10:47 ` Kai Großjohann
1999-12-12 15:54 ` Karl EICHWALDER
1999-12-12 11:07 ` Per Abrahamsen
1999-12-12 11:15 ` Florian Weimer
1999-12-13 9:08 ` Per Abrahamsen
1999-12-13 23:51 ` Karl EICHWALDER
1999-12-14 8:48 ` Per Abrahamsen
1999-12-21 20:06 ` Kai Großjohann
1999-12-21 20:30 ` Florian Weimer
1999-12-21 21:32 ` Kai Großjohann
1999-12-23 20:30 ` Florian Weimer
1999-12-21 20:47 ` Per Abrahamsen
1999-12-22 0:07 ` Russ Allbery
1999-12-22 0:52 ` Stainless Steel Rat
1999-12-14 20:18 ` smarkacz
1999-12-14 20:56 ` Florian Weimer
1999-12-17 11:49 ` Toby Speight
1999-12-18 19:33 ` Florian Weimer
1999-12-19 10:47 ` Per Abrahamsen
1999-12-19 18:23 ` Karl EICHWALDER
[not found] ` <ug0x1bxde.fsf@lanber.ca <shvh5uhjsf.fsf@tux.gnu.franken.de>
1999-12-20 11:24 ` Per Abrahamsen
1999-12-20 23:22 ` Florian Weimer
1999-12-21 20:23 ` Florian Weimer [this message]
1999-12-20 18:20 ` Karl EICHWALDER
1999-12-15 7:20 ` Per Abrahamsen
1999-12-17 8:53 ` Hrvoje Niksic
1999-12-21 20:08 ` Kai Großjohann
1999-12-21 20:29 ` Florian Weimer
1999-12-21 21:31 ` Kai Großjohann
1999-12-22 10:10 ` Hrvoje Niksic
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=87r9ggm4ab.fsf@deneb.cygnus.argh.org \
--to=fw@s.netic.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).