On Mon, 7 Oct 2002, Dan Kogai wrote:
As I said, Encode::MIME::Header has those restrictions;
* the Encode API
* RFC 2047
I'm not sure if Encode::MIME::Header is the best place to
implement RFC 2231 because RFC 2231 encoding/decoding involves two
parameters, 'MIME charset' and 'language'. RFC 2231 is used not only
for email/news messages but also in http header.
Implementing RFC 2231 in Encode::MIME::Header would help
dynamically-generated-attachment (on the web) have the standard-compliant
Content-Disposition header(RFC 2183). Currently, most C-D headers
generated by CGI programs use either raw 8bit characters in an unspecified
encoding or RFC 2047-encoding for the value of 'name' parameter of
C-D header. Neither of these behaviors are standard-compliant.
Jungshik
