Re: Mime types and attached files

[gdt@work.lexort.com]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> However, I must evaluate the form[1]
>>
>> (defalias 'mail-header-encode-parameter 'rfc2047-encode-parameter)
>>
>> when sending files with Japanese names in business.  That's very
>> annoying, though I never want to make it the default (so, I
>> restore it into `rfc2231-encode-string' after sending a mail).
>
> Well -- why not make it the default?  We know that a large number of
> mail readers out there don't support RFC2231, and we know that most
> mail readers support RFC2047 parameter decoding.  (Are there any that
> don't?  I mean, that don't support RFC2047 parameter encoding, but do
> support RFC2231?)
>
> So to make life easier for everybody I propose making
> `rfc2047-encode-parameter' the default.

It would be cool to have BBDB notice MUAs used by correspondents and
record them all, and have a function to choose an encoding based on
that.  That way the standards could still be followed by default, with
accomodation for lame/unstandard MUAs.  But not everyone uses BBDB.

-- 
	Greg Troxel <gdt@work.lexort.com>