Re: 0.26: Bug in text of button

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Jean-Yves Perrier <perrier@nagra-kudelski.ch> writes:

> Therefore that is not a bug in Gnus which is behaving correctly there.

Stop press!  RFC2184 updates how parameter lists are supposed to be
dealt with.  Not only are they now allowed to contain words encoded in
yet a scheme, but you can also split long values thusly:

     Content-Type: message/external-body; access-type=URL;
      URL*0="ftp://";
      URL*1="cs.utk.edu/pub/moore/bulk-mailer/bulk-mailer.tar"

The encoding is a doozy:

     Content-Type: application/x-stuff;
      title*=us-ascii'en-us'This%20is%20%2A%2A%2Afun%2A%2A%2A

Eek.

Anyway, after reading the rest of the document, it turns out that I
was right after all -- the params are still not allowed to contain
RFC2047-encoded words.  They can only be encoded using this new
scheme, and the attribute name has to end with an "*" to signal this.

Stop press again!  RFC2184 has been obsoleted by RFC2231.  (Scan,
scan.)  Oh, it just clarifies a few things, and adds more beautiful
examples:

   Content-Type: application/x-stuff
    title*0*=us-ascii'en'This%20is%20even%20more%20
    title*1*=%2A%2A%2Afun%2A%2A%2A%20
    title*2="isn't it!"

I really should consult the rfc-index.txt file more...

Anyway (yet again), I'll write functions to parse this.  rfc2231.el,
here I come.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen