From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Wed Sep 18 2002 - 06:40:24 CDT
In <8X2X$lkJcDB@3247.org> list-ietf-wg-apps-usefor@faerber.muc.de (Claus Färber) writes:
>Charles Lindsey <chl@clw.cs.man.ac.uk> schrieb/wrote:
>> So you can say
>> Content-Disposition: attachment; filename="utf8-æ?å" (in UTF-8)
>> and it you send it via email as well as news you encode using RFC 2231.
>And existing gateways already do that?
I would hope that existing user agents would do it when sending email.
I.e. you would type in that filename (in whatever local charset was in
use) and the user agent, if it was emailing the message, would do the RFC
2231 encoding (just as such agents currently do RFC 2047 encoding without
the user being aware of it). If that same agent were posting it as a news
article, then it might or might not use RFC 2231.
BTW, can someone tell me to what extent current MUAs support RFC 2231? I
have never encountered an example in real life, but I presume they do
exist.
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl Email: chl@clw.cs.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5