From: Steven Woody <anti-spam.narkewoody@gmail.com.dont-post-to>
Subject: Re: How Do I Suppress Header Encoding For Some Groups?
Date: Tue, 12 Jul 2005 11:43:56 +0800 [thread overview]
Message-ID: <871x64pu2r.fsf@narke.yellow.line> (raw)
In-Reply-To: <17106.63522.196493.233668@parhasard.net>
Aidan Kehoe <kehoea@parhasard.net> writes:
> 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 ".")))
this method is not practical for what i mentioned no-ascii characters are
actually chinese, my native language. ;-(
>
> But I can’t read minds. What you should be doing is telling the maintainers
> of the web archive software to fix their program.
they refused to do that and provided a 'good' reason, microsoft outloop
express, which is a popluar newsreader, does not encode the header (actually
the subject line), so their web archive works fine with it.
-
narke
next prev parent reply other threads:[~2005-07-12 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 4:25 Steven Woody
2005-07-11 21:02 ` Steven Woody
2005-07-11 22:52 ` Aidan Kehoe
2005-07-11 22:54 ` Aidan Kehoe
2005-07-12 3:43 ` Steven Woody [this message]
2005-07-12 20:19 ` Aidan Kehoe
2005-07-13 10:11 ` Steven Woody
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=871x64pu2r.fsf@narke.yellow.line \
--to=anti-spam.narkewoody@gmail.com.dont-post-to \
/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).