From: Ulrich Schwarz <uschwarz@gmx.net>
Cc: ding@gnus.org
Subject: Re: 8Bit Header encoding with Gnus: qp - rfc2047
Date: 17 Jun 1999 17:38:37 +0200 [thread overview]
Message-ID: <87n1xy3khu.fsf_-_@fruli.ddns.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "16 Jun 1999 22:05:44 +0200"
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.
Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
>> What settings are necessary to make Gnus 5.6.45 and pgnus 0.87
>> automatically encode 8bit headers using qp; i.e. encode 8 bit
>> headers using RFC2047-header-encoding ?
Gnus 5.6.45 does this automatically with mime-support enabled
(tm-edit 7.108), however pgnus hat its own native mime support
and rfc2047 header encoding is not enabled by default.
>> e.g. if I write a header line like
>> "Subject: 8Bit·Header·encoding·with·Gnus: qp"
>> then Gnus should automatically encode it to
>> "Subject:=?ISO-8859-1?Q?8Bit=B7Header=B7encoding=B7with=B7Gnus=3A=20qp?="
> Whatever you did was correct. I typed C-u g on your article and saw
> that the header was encoded in this way.
I created the original header *manually* ;-)
> Pgnus does this by default :-)
Not for my setup (plain Debian xemacs 20.4 and pgnus <= 0.87 - without
any additional setttings in my .emacs and .gnus configuration
x-post & f'up ding@gnus.org mailing list
--
So long.
Ulrich
next parent reply other threads:[~1999-06-17 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874sk8icup.fsf@fruli.ddns.org>
[not found] ` <vaflndjgbc7.fsf@petty.cs.uni-dortmund.de>
1999-06-17 15:38 ` Ulrich Schwarz [this message]
1999-06-20 22:10 ` Ulrich Schwarz
[not found] ` <whvhci82mv.fsf@viffer.oslo.metis.no>
1999-06-22 15:14 ` Ulrich Schwarz
1999-06-22 16:06 ` Per Abrahamsen
1999-06-22 19:07 ` Bjørn Mork
1999-07-03 10:21 ` 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=87n1xy3khu.fsf_-_@fruli.ddns.org \
--to=uschwarz@gmx.net \
--cc=ding@gnus.org \
/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).