Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Missing QP encoding of header?
Date: 07 Aug 1999 03:56:20 -0400	[thread overview]
Message-ID: <2n907ogh23.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "07 Aug 1999 09:30:42 +0200"

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

KG> Hm?  I set message-default-headers in ~/.gnus, but the problem isn't
KG> that there is a \201 or something.  The problem is that I expected

KG>     From: address (Kai =?iso-8859-1?q?Gro=DFjohann?=)

KG> and what I got was

KG>     From: address (Kai Großjohann)

KG> Please note the missing quoted printable encoding.

KG> Does Gnus behave differently in news and mail groups?

You are right. 

In message-send-mail, headers are encoded by
	    (mail-encode-encoded-word-buffer)

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.

-- 
Shenghuo ZHU


  reply	other threads:[~1999-08-07  7:56 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 [this message]
1999-08-08  1:45       ` Kai Großjohann
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=2n907ogh23.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).