Listed in the TODO section of STATUS is this: - Implement (some of) RFC 2047 in the multipart parser.
e.g. Content-Disposition: name="foo" filename="=?iso-8859-1?q?foo.txt?=" Should we try and decode filename to "foo.txt", or leave it encoded? I think we need to settle this issue before doing a non-dev release, since IMO this would be a major API change (not something we could roll into a minor or patchlevel bump). Thoughts? -- Joe Schaefer
