From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/28353 Path: main.gmane.org!not-for-mail From: Florian Weimer Newsgroups: gmane.emacs.gnus.general Subject: Re: de .* and gnus-group-posting-charset-alist Date: 21 Dec 1999 00:22:35 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: <87puw1yz7o.fsf@deneb.cygnus.argh.org> References: <87ogbwjtpw.fsf@deneb.cygnus.argh.org> <87so15xmug.fsf@deneb.cygnus.argh.org> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035165217 29436 80.91.224.250 (21 Oct 2002 01:53:37 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 01:53:37 +0000 (UTC) Return-Path: Original-Received: from spinoza.math.uh.edu (spinoza.math.uh.edu [129.7.128.18]) by mailhost.sclp.com (Postfix) with ESMTP id 402B0D051E for ; Tue, 21 Dec 1999 00:55:01 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by spinoza.math.uh.edu (8.9.1/8.9.1) with ESMTP id XAB13272; Mon, 20 Dec 1999 23:54:34 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Mon, 20 Dec 1999 23:54:21 -0600 (CST) Original-Received: from mailhost.sclp.com (postfix@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id XAA02718 for ; Mon, 20 Dec 1999 23:54:10 -0600 (CST) Original-Received: from mail.cid.net (unknown [212.172.21.2]) by mailhost.sclp.com (Postfix) with ESMTP id 6F576D051E for ; Tue, 21 Dec 1999 00:53:50 -0500 (EST) Original-Received: from uucp by mail.cid.net (Exim 3.11) with local-bsmtp id 120IEw-0003VJ-00; Tue, 21 Dec 1999 06:53:42 +0100 Original-Received: from deneb.cygnus.argh.org ([192.168.1.2] ident=root) by cygnus.argh.org with esmtp (Exim 3.02 #1) id 120I7i-0000Kw-00 for ding@gnus.org; Tue, 21 Dec 1999 06:46:14 +0100 Original-Received: from fw by deneb.cygnus.argh.org with local (Exim 3.02 #1) id 120C8R-0003f4-00 for ding@gnus.org; Tue, 21 Dec 1999 00:22:35 +0100 Original-To: ding@gnus.org In-Reply-To: Per Abrahamsen's message of "20 Dec 1999 12:24:51 +0100" Original-Lines: 50 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:28353 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:28353 Per Abrahamsen writes: > The current (5.8.2) solution, to make the behaviour depend on > hierarchy, is close to perfect. No, it isn't. Currently, you've got two choices: Either you encode the whole article with quoted-printable (which causes pain with clueless newsreaders), or you use 8-bit in the article *and* the header, which is against RFC 822, RFC 1036, RFC 2047 (and probably more...) I'm currently testing the following extension (of course, a bit of additional code is required): (defcustom gnus-group-posting-charset-alist '(("^\\(no\\|fr\\|dk\\)\\.[^,]*" iso-8859-1 (iso-8859-1)) (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 tha nil for HEADER infringes some RFCs, so use this option with care." :type '(repeat (list (choice :tag "Where" (regexp :tag "Group") (const :tag "Mail message" :value message-this-is-mail) (const :tag "News article" :value message-this-is-news)) (choice :tag "Header" (const :tag "Always encoded" nil) (symbol :tag "Permitted charset")) (choice :tag "Body" (const :tag "Any charset" :value t) (const :tag "Always encoded" :value nil) (repeat :tag "Permitted charsets" (symbol :tag "Charset"))))) :group 'gnus-charset) The idea is that you can chose the header charset and the charsets which will not be encoded in the body in a completely independent manner. It seems that my current implementation is nearly complete and mostly correct, but I don't have Internet access at the moment and it's about time to go to bed anyway ;), so I haven't committed the changes yet.