Re: latest rfc2231-parse-string broken in multiple ways

[Joe Wells]

address@hidden (Lars Magne Ingebrigtsen) writes:

> Joe Wells <address@hidden> writes:
>
>> Bug #1: The invocation
>>
>>   (mail-header-parse-content-type "message/external-body;
>>    name*1*=plugh%2fhello-sailor%2fbing.pdf;
>>    name*0*=us-ascii''~%2ffoo%2fbar%2fbaz%2fxyzzy%2f;
>>    access-type=LOCAL-FILE")
>>
>> raises an error with this message:
>>
>>   Invalid coding system: plugh%2fhello-sailor%2fbing\.pdfus-ascii
>
> This has already been fixed.

Hurray!

>> Bug #2: The invocation
>>
>>   (mail-header-parse-content-type "message/external-body;
>>    name*0*=us-ascii''~%2ffoo%2fbar%2fbaz%2fxyzzy%2f;
>>    access-type=LOCAL-FILE;
>>    name*1*=plugh%2fhello-sailor%2fbing.pdf")
>>
>> returns this result:
>>
>>   ("message/external-body"
>>    (name . "~/foo/bar/baz/xyzzy/")
>>    (access-type . "LOCAL-FILE")
>>    (name . "plugh/hello-sailor/bing.pdf"))
>
> I've now fixed this in the development version of Gnus, but I don't
> think it's a serious enough problem as to warrant fixing in Gnus
> 5.10.  (That is, these types of encodings are rarely seen in the
> wild.)

Seems reasonable.

-- 
Joe