From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Mon Sep 16 2002 - 09:06:49 CDT
In <ylu1kts3tk.fsf@windlord.stanford.edu> Russ Allbery <rra@stanford.edu> writes:
>Charles Lindsey <chl@clw.cs.man.ac.uk> writes:
>> Yes, that is the position we are at, more or less. It is up to the guy
>> who implements the injector to decide whether to encapsulate, or whether
>> to encode everything regardless, or to leave things alone where he knows
>> that it will get through the mail transport intact (e.g. by looking for
>> characters in 0x80-9f as you suggest, and by not bothering in the case
>> of headers within deeply nested MIME multiparts).
>Thankfully, headers within deeply nested MIME multiparts aren't a problem
>by definition since by definition they cannot contain 8-bit characters.
On the contrary, from 6.21.1
The RFCs listed are deemed to be incorporated into this standard to
the extent necessary to facilitate their usage within Netnews,
subject to the revised syntax of parameter given in this standard
(which permits UTF-xtra-chars to appear within quoted-strings used as
values), and subject to curtailment of that usage as described in the
following sections. ....
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.
You can do that at any level within nested multiparts. The point that I
was making is that, for transport purposes, within such multiparts UTF-8
can hardly fail to get delivered by any transport that supports 8BITMIME.
-- 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