From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: rfc2231 bug
Date: Tue, 18 Apr 2006 08:27:29 +0900 [thread overview]
Message-ID: <b4mzmijvl3y.fsf@jpl.org> (raw)
Hi,
The most recent changes in rfc2231-parse-string cause a bug.
This is the test case:
(rfc2231-parse-string
(concat "Content-Disposition: attachment;"
(rfc2231-encode-string
"filename"
"一二三四五六七八九零一二三四五六七八九零.pdf")))
=> ("content-disposition:attachment"
(filename . "一二三四五六七八九零一二三四8^O;<7H,6eNm\e(B.pdf"))
It is because each segmented encoded text is decoded before
concatenating them. I once fixed this problem as follows:
2004-12-21 Katsumi Yamaoka <yamaoka@jpl.org>
* rfc2231.el (rfc2231-parse-string): Decode encoded value after
concatenating segments rather than before concatenating them.
Suggested by ARISAWA Akihiro <ari@mbf.ocn.ne.jp>.
next reply other threads:[~2006-04-17 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 23:27 Katsumi Yamaoka [this message]
2006-04-18 0:06 ` Katsumi Yamaoka
2006-04-18 8:00 ` Katsumi Yamaoka
2006-04-18 16:28 ` 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=b4mzmijvl3y.fsf@jpl.org \
--to=yamaoka@jpl.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).