From: NAKAJI Hiroyuki <nakaji@jp.freebsd.org>
To: ding@gnus.org
Subject: Re: long encoded filename in mime part is truncated and not decoded
Date: Tue, 12 Jun 2007 22:05:15 +0900 [thread overview]
Message-ID: <86odjlmigk.fsf@ra333.heimat.gr.jp> (raw)
In-Reply-To: <b4mejkhbig2.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 12 Jun 2007 19:01:01 +0900")
>>>>> In <b4mejkhbig2.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> Here is a program that tries fixing of corrupted B encoded words:
Thanks. This helps very much.
> Use this with care. It will not necessarily fix such ones,
> moreover it might break correct ones. To disable this, type
> `M-x ad-unadvise RET rfc2231-parse-qp-string RET'.
I'll use with care.
--
NAKAJI Hiroyuki
prev parent reply other threads:[~2007-06-12 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 2:29 NAKAJI Hiroyuki
2007-06-12 4:27 ` Katsumi Yamaoka
2007-06-12 8:29 ` NAKAJI Hiroyuki
2007-06-12 10:01 ` Katsumi Yamaoka
2007-06-12 13:05 ` NAKAJI Hiroyuki [this message]
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=86odjlmigk.fsf@ra333.heimat.gr.jp \
--to=nakaji@jp.freebsd.org \
--cc=ding@gnus.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).