From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/5364
Path: news.gmane.org!not-for-mail
From: Aidan Kehoe <kehoea@parhasard.net>
Newsgroups: gmane.emacs.gnus.user
Subject: Re: How Do I Suppress Header Encoding For Some Groups?
Date: Mon, 11 Jul 2005 23:52:18 +0100
Organization: 1&1 Internet AG
Message-ID: <17106.63522.196493.233668@parhasard.net>
References: <87pstrl22o.fsf@narke.yellow.line> <873bql2gzm.fsf@narke.yellow.line>
NNTP-Posting-Host: main.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Trace: sea.gmane.org 1138671096 27118 80.91.229.2 (31 Jan 2006 01:31:36 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Tue, 31 Jan 2006 01:31:36 +0000 (UTC)
Original-X-From: nobody Tue Jan 17 17:35:10 2006
Original-Path: quimby.gnus.org!newsfeed.gazeta.pl!news.nask.pl!newsfeed.pionier.net.pl!news-fra1.dfn.de!npeer.de.kpn-eurorings.net!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail
Original-Newsgroups: gnu.emacs.gnus
Original-NNTP-Posting-Host: p54bea8f1.dip0.t-ipconnect.de
Original-X-Trace: online.de 1121118432 12133 84.190.168.241 (11 Jul 2005 21:47:12 GMT)
Original-X-Complaints-To: abuse@einsundeins.com
Original-NNTP-Posting-Date: Mon, 11 Jul 2005 21:47:12 +0000 (UTC)
X-NS5-file-as-sent: t
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b21 (corn, NetBSD-i386)
Cancel-Lock: sha1:TAIJ/+IBTIckwbpXye2QjiIM9M0=
Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:5506
Original-Lines: 46
X-Gnus-Article-Number: 5506   Tue Jan 17 17:35:10 2006
Xref: news.gmane.org gmane.emacs.gnus.user:5364
Archived-At: <http://permalink.gmane.org/gmane.emacs.gnus.user/5364>


 Ar an dara lá déag de mí Iúil, scríobh Steven Woody: 

 > Steven Woody <anti-spam.narkewoody@gmail.com.dont-post-to> writes:
 > 
 > > if I type in non-ascii characters in the Subject line, gnus will
 > > automatically encode it as something like ?gb2312?Q%##@%# when the
 > > article is really sent out.  this is okay for most cases and absolutely
 > > necessary for email.
 > >
 > > but, i need to access some private groups, which got a bi-direction
 > > interface between web and usenet, so every article i posted will get
 > > display on web, and vice versa.  the problem is that, their web
 > > engineer can not render the encoded header correctly, hence my subject
 > > line will not get read by other users who prefer to web.

There is no other way standard way to encode those headers, for non-ASCII
text, besides RFC 2047 encoding, the process you’ve asked how to
suppress. (And even that standard is only applied to Usenet by a process of
widespread looking-the-other-way.)  So, what you’re asking is “this text is
illegible because some web archiving software is broken. How do I make it
illegible (perhaps in a different way, but I haven’t specified if that’s
necessary)?” Not a very constructive question.

This piece of advice will transform all non-ASCII characters in the relevant
headers to a full stop, and may be enough for you if you add it to your
initialisation file:

(defadvice rfc2047-encode-message-header 
  (before my-rfc2047-encode-message-header-change activate)
  "Replace non-ASCII characters in the headers with . if the region contains
soc.culture.china.  "
  (goto-char (point-min))
  (while (re-search-forward "[^\001-\177]" nil t)
    (replace-match ".")))

But I can’t read minds. What you should be doing is telling the maintainers
of the web archive software to fix their program. 

 > > [...]
 > is there anyone get a clue? please.

-- 
Russian has no phoneme that corresponds directly to Germanic /h/. As a 
result, for a not-insignificant number of people, the Second World War 
involved the Soviet Union defeating Адольф Гитлер, “Adolf Gitler.”