i18n of attachment names
Brought to you by:
tony-kay
i18n of attachment names is specified in RFC 2231, but it is not followed by everyone (certainly not Microsoft). So it seems wise to be liberal here and decode both RFC 2231- and RFC 2047-encoded file names.
And then there's another problem -- how to present decoded file name to browser. Some research: http://www.motobit.com/help/ScptUtl/pa97.htm
Logged In: YES
user_id=1651837
Originator: NO
Hi Sergey.
Thanks for the research. I remember this issue being a pain both to research and to do correctly, because you have to guess what every mail client in the world might send you, and what every browser will actually accept (which is complicated by the fact that standards are not always followed or perhaps didn't even exist when those programs were written).
This information will help be helpful.
If you have any interest in patching the code, let me know. I'd be glad to point you in the right direction.