Re: rfc2231-parse-string: Decode encoded value after concatenating segments

[Katsumi Yamaoka <yamaoka@jpl.org>]

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

>>>>> In <v9ll3tiia5.fsf@marauder.physik.uni-ulm.de> Reiner Steib wrote:

> this change...

> ,----
>| 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>.
> `----

> ... breaks displaying of external body parts for me if the file name
> spans more than one line, like this one:

Thanks for pointing it out.  I've fixed it in the v5-10 branch
and the trunk.  The change I'd made at the end of last year was
insufficient; I should have taken care that not only a segmented
parameter but also other parameters might be there.  Here's a
report I sent then:


[-- Attachment #2: Type: message/rfc822, Size: 895 bytes --]

From: Katsumi Yamaoka <yamaoka@jpl.org>
To: bugs@gnus.org
Cc: semi-gnus-ja@meadowy.org
Subject: Fixed: rfc2231.el decoder bug
Date: Tue, 21 Dec 2004 18:38:15 +0900
Message-ID: <b9yu0qgt2ig.fsf_-_@jpl.org>

Hi,

ARISAWA Akihiro reported there is a bug in the rfc2231 decoder.
He wrote that the decoder doesn't decode encoded long values
correctly as follows:

(rfc2231-parse-string
 (concat "Content-Disposition: attachment;"
	 (rfc2231-encode-string
	  "filename"
	  "一二三四五六七八九零一二三四五六七八九零.pdf")))
("content-disposition:attachment"
 (filename . "一二三四五六七八九零一二三四五六七八6eNm^[(B.pdf"))

I've fixed it in both the trunk and the v5-10 branch.

Regards,