[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pine-info
Subject:    Re: [Pine-info] RFC-2047 for attachment's "name=" and "filename="
From:       Jeff Franklin <jpf () cac ! washington ! edu>
Date:       2005-07-13 22:19:54
Message-ID: Pine.LNX.4.63.0507131442330.23684 () pigeon ! cac ! washington ! edu
[Download RAW message or body]

On Wed, 13 Jul 2005, Pierre Thibaudeau wrote:

> Although the release notes suggest that non-ASCII filenames are encoded as 
> per RFC-2047 (*), pine does the following

> which is not recognized by other applications.
>
> By the same token, pine does not recognize RFC-2047-encoded filenames. For 
> example:

> It would be most helpful to have pine use this same notation for attachment 
> file names instead of doing "name*=" and "filename*=" that only pine 
> understands.

Hi Pierre,

RFC 2047 only defines how headers are supposed to be encoded, and what we 
are dealing with here are MIME parameters, which have their own definition 
of how non-ascii characters should be encoded.  For this definition, I 
refer you to RFC 2231.  Clients that send RFC 2047 encoded filenames are 
broken, and pine does go to some lengths to tolerate this brokenness. 
For instance if in your example the "name=" value had begun with the "=?", 
pine would have decoded it.  We could very well just try decoding all 
mime-params with 2047, but I am a little leery of possibly breaking 
working clients to appease the broken ones.

The issue of having pine send 2047-encoded filenames is a definite no-no, 
for reasons which should now be apparent.  In fact, I would say that 
clients that can't receive 2231-encoded filenames have a pretty severe bug 
that they should be made aware of.  The makers of apps that send 
2047-encoded filenames should be alerted to their bugs as well.

Hope that helps,
Jeff
_______________________________________________
Pine-info mailing list
Pine-info@u.washington.edu
http://mailman1.u.washington.edu/mailman/listinfo/pine-info
[prev in list] [next in list] [prev in thread] [next in thread]