[
https://issues.apache.org/jira/browse/MIME4J-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744492#action_12744492
]
Aron Wieck edited comment on MIME4J-138 at 8/18/09 6:17 AM:
------------------------------------------------------------
Attached svn diff and full DecoderUtil.java with the changes.
This differs from my previously uploaded RegexDecoderUtil.java in the following
points:
- the regular expression pattern has been changed to be more tolerant on wrong
encoding data. It now assumes that no "?" sign may be in the encoded word other
than these four: =?charset?enc?text?=
- the log output now includes the encoded word again
- added comments
was (Author: eunice):
Attached svn diff and full DecoderUtil.java with the changes.
This differs from my previously uploaded RegexDecoderUtil.java in the following
points:
- the regular expression pattern has been changed to be more tolerant on wrong
encoding data. It now assumes that no "?" sign may be in the encoded word.
- the log output now includes the encoded word again
- added comments
> 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, 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.
