Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Missing QP encoding of header?
Date: 08 Aug 1999 03:45:04 +0200	[thread overview]
Message-ID: <vafemhfhwpr.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Shenghuo ZHU's message of "07 Aug 1999 03:56:20 -0400"

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> while in message-send-news, headers are encoded by
>             (let ((mail-parse-charset message-posting-charset))
>               (mail-encode-encoded-word-buffer))
> 
> Therefore, if message-posting-charset is iso-8859-1, then your name
> will not be encoded in news. message-posting-charset is a local
> variable in message buffer.  You can use
> gnus-group-posting-charset-alist to configure it. For example, if you
> always want your name encoded, you can set it to ((".*" nil)) or just
> nil.

You say `headers are encoded', but the documentation seems to imply
that header encoding and body encoding are always the same (for any
given message).  Hm.  Can Gnus be told to, say, QP-encode the headers
but send the body as-is?

I think I'll have to ask the guys from/for the de.* newsgroups what's
supposed to be done there.

kai
-- 
I like BOTH kinds of music.


  reply	other threads:[~1999-08-08  1:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-06 18:41 Kai Großjohann
1999-08-06 21:16 ` Kai Großjohann
1999-08-06 23:29 ` Shenghuo ZHU
1999-08-07  7:30   ` Kai Großjohann
1999-08-07  7:56     ` Shenghuo ZHU
1999-08-08  1:45       ` Kai Großjohann [this message]
1999-08-08 13:40         ` Florian Weimer
1999-09-24 17:46         ` Lars Magne Ingebrigtsen
1999-09-24 21:42           ` Kai Großjohann
1999-09-25 10:18             ` Lars Magne Ingebrigtsen
1999-09-26 16:58               ` Kai Großjohann
1999-09-27 17:42                 ` Lars Magne Ingebrigtsen

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=vafemhfhwpr.fsf@petty.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.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).