Gnus development mailing list
 help / color / mirror / Atom feed
* Re: 8Bit Header encoding with Gnus: qp - rfc2047
       [not found] ` <vaflndjgbc7.fsf@petty.cs.uni-dortmund.de>
@ 1999-06-17 15:38   ` Ulrich Schwarz
  1999-06-20 22:10     ` Ulrich Schwarz
  0 siblings, 1 reply; 6+ messages in thread
From: Ulrich Schwarz @ 1999-06-17 15:38 UTC (permalink / raw)
  Cc: ding

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 8Bit Header encoding with Gnus: qp - rfc2047
  1999-06-17 15:38   ` 8Bit Header encoding with Gnus: qp - rfc2047 Ulrich Schwarz
@ 1999-06-20 22:10     ` Ulrich Schwarz
       [not found]       ` <whvhci82mv.fsf@viffer.oslo.metis.no>
  0 siblings, 1 reply; 6+ messages in thread
From: Ulrich Schwarz @ 1999-06-20 22:10 UTC (permalink / raw)


Ulrich Schwarz <uschwarz@gmx.net> writes:

pgnus does not automatically encode 8 bit headers using rfc2047 (qp).

(pgnus up to 0.88, xemacs 20.4 Debian 2.1 / emacs 19.3 Suse 6.1)

How can I activate this feature?

I browsed the ding mailing lists and couldn't find an answer.


Thanks a lot for your help.

-- 
So long.
Ulrich


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 8Bit Header encoding with Gnus: qp - rfc2047
       [not found]       ` <whvhci82mv.fsf@viffer.oslo.metis.no>
@ 1999-06-22 15:14         ` Ulrich Schwarz
  1999-06-22 16:06           ` Per Abrahamsen
  0 siblings, 1 reply; 6+ messages in thread
From: Ulrich Schwarz @ 1999-06-22 15:14 UTC (permalink / raw)


Steinar Bang <sb@metis.no> writes:

>> pgnus does not automatically encode 8 bit headers using rfc2047
>> (qp).

> I think it is supposed to do so for mail, but not for news.

That's a real problem. Accoring to offical Usenet RFCs, usenet headers
have to be 8bit clean - 8bit chars may only occur in rfc2047 (qp)
format.


> My Pterodactyl Gnus v0.84 uses RFC 2047 encoding for mail, and I
> haven't yet been flamed for using RFC 2047 in news, so I don't think
> it does so there.

I've been flamed multiple times for 8 bit headers not being rfc
2047-encoded in my pgnus usenet headers. According to my
investigations, the flamers were right.

Thus, Gnus should use RFC2047 header encoding for news, too.

-- 
So long.
Ulrich


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 8Bit Header encoding with Gnus: qp - rfc2047
  1999-06-22 15:14         ` Ulrich Schwarz
@ 1999-06-22 16:06           ` Per Abrahamsen
  1999-06-22 19:07             ` Bjørn Mork
  0 siblings, 1 reply; 6+ messages in thread
From: Per Abrahamsen @ 1999-06-22 16:06 UTC (permalink / raw)


Ulrich Schwarz <uschwarz@gmx.net> writes:

> Thus, Gnus should use RFC2047 header encoding for news, too.

Unencoded 8-bit headers are prefered in the dk.* hierarchy, because
that is supported by most news agents in use.  I suspect the situation
is the same in the no.* hierarchy.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 8Bit Header encoding with Gnus: qp - rfc2047
  1999-06-22 16:06           ` Per Abrahamsen
@ 1999-06-22 19:07             ` Bjørn Mork
  1999-07-03 10:21               ` Lars Magne Ingebrigtsen
  0 siblings, 1 reply; 6+ messages in thread
From: Bjørn Mork @ 1999-06-22 19:07 UTC (permalink / raw)


Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Ulrich Schwarz <uschwarz@gmx.net> writes:
> 
> > Thus, Gnus should use RFC2047 header encoding for news, too.
> 
> Unencoded 8-bit headers are prefered in the dk.* hierarchy, because
> that is supported by most news agents in use.  I suspect the situation
> is the same in the no.* hierarchy.

Correct. I believe the same goes for relcom and a few other
hierarchies. The header charset must of course also be specified.

I must say that I am surprised to hear about flaming based on 8bit
chars in Usenet headers. I've posted hundreds of articles in comp,
rec, alt, news and a few other hierarchies, and never been flamed
(well, at least not for the header encoding :-). All of the articles
have had at least one header with 8bit chars (because of my name...)
and a working mail address.

The reason is of course that 8bit headers don't cause any problems for
anybody. The chars may not always look like they were supposed to,
but that's not important (I don't care whether people call me Bjørn,
Bjxrn, Bj|rn, Bjorn, or Bj¤rn). What's important is that rfc2047
really fucks up readers that don't understand it, and makes the text
unreadable. I do not like being called =?iso-8859-1?q?Bj=F8rn?=. You
will really need your flameproof suit if you post something like that
in no.*

Therefore 8bit for news and rfc2047 for mail (where you have more
control over the client software in the other end) is a reasonable
default. But it should be possible to change it based on hierarchy,
and IIRC it is. I just don't remember how. Anybody?


Bjørn


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: 8Bit Header encoding with Gnus: qp - rfc2047
  1999-06-22 19:07             ` Bjørn Mork
@ 1999-07-03 10:21               ` Lars Magne Ingebrigtsen
  0 siblings, 0 replies; 6+ messages in thread
From: Lars Magne Ingebrigtsen @ 1999-07-03 10:21 UTC (permalink / raw)


"Bjørn Mork" <bmork@dod.no> writes:

> Therefore 8bit for news and rfc2047 for mail (where you have more
> control over the client software in the other end) is a reasonable
> default. But it should be possible to change it based on hierarchy,
> and IIRC it is. I just don't remember how. Anybody?

It's controlled by `gnus-group-posting-charset-alist', but I don't
really like that variable.  

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~1999-07-03 10:21 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <874sk8icup.fsf@fruli.ddns.org>
     [not found] ` <vaflndjgbc7.fsf@petty.cs.uni-dortmund.de>
1999-06-17 15:38   ` 8Bit Header encoding with Gnus: qp - rfc2047 Ulrich Schwarz
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

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).