[
https://issues.apache.org/jira/browse/MIME4J-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796170#action_12796170
]
Stefano Bagnara commented on MIME4J-138:
----------------------------------------
Nevin, there is no "appendReplacement" method call in the committed fix, so I
guess you are referring to an older fix. If you have a string that show the
problem I can add it to the test suite to prove that the bug does not exist
anymore.
That said, FYI in Java 5 you can use Pattern.quote() to get an escaped version
of the string (but there is no more need for escaping in the new code, so this
is just for your interest).
> DecoderUtil.decodeEncodedWords() fails if encoded-text starts with an equals
> sign
> ---------------------------------------------------------------------------------
>
> Key: MIME4J-138
> URL: https://issues.apache.org/jira/browse/MIME4J-138
> Project: JAMES Mime4j
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Markus Wiederkehr
> Assignee: Markus Wiederkehr
> Fix For: 0.7
>
> Attachments: DecoderUtil.diff, DecoderUtil.java, mime4j-138.patch,
> RegexDecoderUtil.java
>
>
> For example "=?utf-8?Q?=20test?=" should be decoded as " test". Instead it
> does not get decoded at all.
> The problem is that DecoderUtil.decodeEncodedWords() falsely identifies
> =?utf-8?Q?= as the encoded word which cannot be decoded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
