Re: 0.26: Bug in text of button

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

Hrvoje Niksic <hniksic@srce.hr> writes:

> Does this perhaps come under the `phrase' in the context you quoted:
> 
>    + An 'encoded-word' MUST NOT be used in parameter of a MIME
>      Content-Type or Content-Disposition field, or in any structured
>      field body except within a 'comment' or 'phrase'.
>                                               ^^^^^^

No, the C-T value parameter section consists of
"token / quoted-string".  The former is not a phrase, and the latter
is forbidden to contain encoded words by this:

   + An 'encoded-word' MUST NOT appear within a 'quoted-string'.

So I guess there is no way to specify parameters that contain
non-ascii characters.

Quoth RFC2045:

     parameter := attribute "=" value

     attribute := token
                  ; Matching of attributes
                  ; is ALWAYS case-insensitive.

     value := token / quoted-string

     token := 1*<any (US-ASCII) CHAR except SPACE, CTLs,
                 or tspecials>


(Some days ago I fetched the complete RFC collection, so I can now
reference *everything*.  :-)  I didn't know that it had grown to
110Mb, though.  (Hm.  Some big Postscript files in there as well.  The
rfc*.txt files only take 94Mb.  :-) ))

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