[
https://issues.apache.org/jira/browse/MIME4J-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014890#comment-13014890
]
Rustam Aliyev edited comment on MIME4J-109 at 4/2/11 12:02 AM:
---------------------------------------------------------------
Attached patch adds RFC 2231 implementation against trunk (1087933). It's
basically ported JavaMail implementation but was cleaned up.
Some notes/limitations:
* Was implemented as a part of
org.apache.james.mime4j.field.ContentDispositionFieldImpl and thus applicable
only for Content-Disposition parameters. This should be further made abstract
to cover Content-Type as well. (not clear whether any other fields should have
this)
* Decoding done inside ContentDispositionFieldImpl. I don't see how this could
be taked outside since there could be encoded and not encoded segments of one
parameter.
* This patch does not cover section 5 of RFC (Language specification in Encoded
Words)
* Tested on Java 6, may not be compatible with previous versions.
was (Author: rstml):
rfc2231 implementation for content-disposition field only
> Support for MIME Parameter Value and Encoded Word Extensions
> ------------------------------------------------------------
>
> Key: MIME4J-109
> URL: https://issues.apache.org/jira/browse/MIME4J-109
> Project: JAMES Mime4j
> Issue Type: New Feature
> Affects Versions: 0.5
> Reporter: Markus Wiederkehr
> Assignee: Markus Wiederkehr
> Fix For: 0.8
>
> Attachments: rfc2231.patch
>
>
> See RFC 2231.
> Mime4j should be capable of correctly decoding and encoding these extensions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
