Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
> * rfc2047.el: Renamed file.
> * gnus-art.el (gnus-article-decode-mime-words): Use 1522.
Won't it be easier to use a name that does not incluse any standard/RFC
(revision)numbers otherwise you are screwed again if another RFC
supercedes the current ones? Especially given that, hopefully, the
mime support will evolve into a general mime library.
RFC1522/RFC2047 define how characters in headers are to be encoded
this week. If someone comes up with a new scheme next week, it would
be not-all-that-nice to have two libraries called
mime-header-encoding.el (or whatever). By clearly stating what each
library does (rfc2047.el encodes according to that RFC), there's less
possibility of confusion. I think.
The 1522/2047 thing is almost purely a cosmetic change, so if
rfc1522.el has already existed, rfc2047.el wouldn't have been
(domestic pets only, the antidote for overdose, milk.)
larsi(a)ifi.uio.no * Lars Magne Ingebrigtsen