From: Katsumi Yamaoka <yamaoka@jpl.org>
To: emacs-pretest-bug@gnu.org
Cc: ding@gnus.org
Subject: Gnus doubles MIME tags
Date: Mon, 22 Jun 2009 21:11:49 +0900 [thread overview]
Message-ID: <b4mws7479iy.fsf@jpl.org> (raw)
Hi,
You might have ever seen a MIME tag in the Gnus article buffer
like this:
[2.
non-ascii-filename.pdf --- application/pdf; non-ascii-filename.pdf]...
Note that the tag is broken into two lines.
In such a case, typing the `E' command there to display
the attachment externally doubles the tag like:
[2.
non-ascii-filename.pdf --- application/pdf; non-ascii-filename.pdf]...
non-ascii-filename.pdf --- application/pdf; non-ascii-filename.pdf]...
or
[2.
[2.
non-ascii-filename.pdf --- application/pdf; non-ascii-filename.pdf]...
I found this is due to M$'s MIME encoder. In the raw form,
the MIME header it made looks like this:
Content-Description:
=?iso-8859-1?Q?non-ascii-filename.pdf?=
It's ugly but is not a bug. Gnus decodes it including the first
newline and displays it in the MIME tag as is. However, Gnus
works properly only with a MIME tag drawn in a single line.
The following patch solves it. It uses `message-fetch-field'
that strips newlines instead of `mail-fetch-field'.
(I don't know how I commit it to the Emacs trunk and also
the branches, so I post it here.)
2009-06-22 Katsumi Yamaoka <yamaoka@jpl.org>
* mm-decode.el (mm-dissect-buffer): Use message-fetch-field instead of
mail-fetch-field to fetch Content-Description header in order to
exclude newlines.
--- mm-decode.el~ 2009-01-22 08:09:02 +0000
+++ mm-decode.el 2009-06-22 11:52:50 +0000
@@ -563,7 +563,7 @@
ctl (and ct (mail-header-parse-content-type ct))
cte (mail-fetch-field "content-transfer-encoding")
cd (mail-fetch-field "content-disposition")
- description (mail-fetch-field "content-description")
+ description (message-fetch-field "content-description")
id (mail-fetch-field "content-id"))
(unless from
(setq from (mail-fetch-field "from")))
Regards,
reply other threads:[~2009-06-22 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b4mws7479iy.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.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).