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

[Reiner Steib <reinersteib+gmane@imap.cc>]

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

Hi,

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:

,----
| Content-Type: message/external-body; 
|  name*0*=us-ascii''%2ftmp%2fste%2fgnus%2fattachment-external-body-test-directory;
|  name*1*=%2ftest-file-2.txt; access-type=local-file
`----

Here is an external body part:


[-- Attachment #2: /tmp/ste/gnus/attachment-external-body-test-directory/test-file-2.txt --]
[-- Type: message/external-body, Size: 117 bytes --]

[-- Attachment #3: Type: text/plain, Size: 534 bytes --]


When I eval revision 6.11.2.2 of rfc2231.el (evaluation the defun
`rfc2231-parse-string' is sufficient) everything is displayed fine:

,----
| [2. message/external-body; test-file-2.txt]...
`----

When I eval revision 6.11.2.4 (latest revision in v5-10 branch) of
rfc2231.el, I get:

,----
| [2. message/external-body; us-ascii''%2ftmp%2fste%2fgnus%2fattachment-external-body-test-directory%2ftest-file-2.txt]...
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/