Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Balker Rasmussen <gnort@daimi.aau.dk>
Subject: Mime unreadable stuff in headers?
Date: 04 Jul 1996 17:07:24 +0200	[thread overview]
Message-ID: <0fbuhw9hw3.fsf@fraxinus.daimi.aau.dk> (raw)

What happened to the decoding of the horrible "=?iso-8859-1?Q?Bj=F8rn?="
stuff, that some tortured and misguided souls put in headers?

I remember putting `gnus-mime-decode-quoted-printable' in
`gnus-article-prepare-hook' and `gnus-parse-headers-hook' to decode it,
but had to remove them again at some point as I got errors entering
summaries and viewing articles :-/

So, what alternative do I have to get rid of them?  Why isn't the
decoding of them standard behaviour (it being the most convenient for
all parties), or if it is the default, what did I somehow overwrite?
-- 
Lars Balker Rasmussen
<URL:http://www.daimi.aau.dk/~gnort/>  <URL:mailto:lars@rasmussen.org>


             reply	other threads:[~1996-07-04 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-04 15:07 Lars Balker Rasmussen [this message]
1996-07-04 15:33 ` Unknown
1996-07-05  7:29   ` Steinar Bang
1996-07-13 20:37     ` Unknown
1996-07-04 19:43 ` Steven L Baur
1996-07-05  1:17 ` Lars Magne Ingebrigtsen
1996-07-05 11:18   ` Lars Balker Rasmussen
1996-07-06  2:32     ` 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=0fbuhw9hw3.fsf@fraxinus.daimi.aau.dk \
    --to=gnort@daimi.aau.dk \
    /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).