I've already started working on this...
Jeff
On 28 May 2001 23:16:00 +0500, Dan Winship wrote:
> > 1. Elm and Evolution:
> > filename="�� ���.txt"
>
> I agree that that's illegal and we shouldn't do it.
>
> > 2. Mozilla:
> > filename="=?iso-8859-1?Q?=E1=F3=20=E9=ED=F1=2Etxt?="
> > 3. Outlook
> > filename="=?iso-8859-1?B?4fMg6e3xLnR4dA==?="
>
> This is just depressing, because like, they went out of their way to do
> it wrong. Sigh. Anyway, what are the odds that someone would actually
> name their file "=?iso-8859-1?blahblahblah", so yeah, I guess we can
> decode that. Sigh.
>
> > 4. Pine
> > The correct way would be:
> > filename*=X-UNKNOWN''%E1%F3%20%E9%ED%F1.txt
>
> > Evolution should generate the correct version, and accept the incorrect
> > versions (ie, interpret all versions above as "�� ���.txt")
>
> 4 cannot be interpreted that way generically because you don't know what
> character set it's in.
>
> Anyway, yes, we should generate RFC2184-compliant headers in this case.
> It looks like probably no other mailer on the planet except maybe Pine
> will recognize them, but that's ok, because as you mentioned, the
> filename parameter is only advisory anyway, so it's not a big deal if
> the recipient can't parse it.
>
> -- Dan
>
> _______________________________________________
> evolution maillist - [EMAIL PROTECTED]
> http://lists.helixcode.com/mailman/listinfo/evolution
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution
