In <200204241802(_dot_)g3OI2Ce14111(_at_)astro(_dot_)cs(_dot_)utk(_dot_)edu>
Keith Moore <moore(_at_)cs(_dot_)utk(_dot_)edu> writes:
similarly, I recommend against implementing automatic rfc 2047
decoding for parameters in general - partly because there's a small
chance that you'll misinterpret a parameter that way, partly because
it conflicts with standard usage, and partly because 2047 is a poor
mechanism for this purpose (which is why the standard doesn't use it).
I think the small chance that he really meant 'file it in a file with the
name "=?koi8-r?B?Q8/XxdQuZG9j?="' is a resonable risk to take.
However, I would like to know why 2047 is thought to be a "poor mechanism"
for this purpose (i.e. why was it not standardized that way - it seems to
work in a wide variety of situations).
--
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(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)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