[
https://issues.apache.org/jira/browse/MIME4J-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701540#action_12701540
]
Markus Wiederkehr edited comment on MIME4J-130 at 4/22/09 7:30 AM:
-------------------------------------------------------------------
I'm not sure what would be the best approach for this problem. Is it possible
and reasonable to modify the existing JavaCC address list parser
(AddressListParser.jjt) to accept both forms? Or does a new parser have to be
written (maybe by copying and adapting AddressListParser.jjt)?
was (Author: wmax):
I'm not such what would be the best approach for this problem. Is it
possible and reasonable to modify the existing JavaCC address list parser
(AddressListParser.jjt) to accept both forms? Or does a new parser have to be
written (maybe by copying and adapting AddressListParser.jjt)?
> Add parse method for e-mail addresses that contain special characters in the
> display name
> -----------------------------------------------------------------------------------------
>
> Key: MIME4J-130
> URL: https://issues.apache.org/jira/browse/MIME4J-130
> Project: JAMES Mime4j
> Issue Type: New Feature
> Affects Versions: 0.6
> Reporter: Markus Wiederkehr
> Assignee: Markus Wiederkehr
> Fix For: 0.7
>
>
> Address.parse(), Group.parse() and Mailbox.parse() can only parse addresses
> in their raw (encoded) form. They are capable of decoding encoded words (RFC
> 2047) but they do not accept already decoded special characters.
> In other words, they can parse the result of Address.getEncodedString() but
> not Address.getDisplayString().
> Mime4j should have a means to parse an address such as "Hans Müller
> <[email protected]>" for generating new messages or manipulating existing
> ones.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
