Re: de .* and gnus-group-posting-charset-alist

[Florian Weimer <fw@s.netic.de>]

Per Abrahamsen <abraham@dina.kvl.dk> 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.