[
https://issues.apache.org/jira/browse/MIME4J-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566811#action_12566811
]
Robert Burrell Donkin commented on MIME4J-34:
---------------------------------------------
Thanks Stefano :-)
RFC2047 covers international encoding in detail. The strictly correct approach
would be to create a charset implementation that understood how to encode and
decode this syntax. Otherwise round tripping will fail. This would be a
reasonable amount of work. It's also a shame that it's not widely supported.
For email, it's important that the original byte sequence is retained to ensure
that round tripping works correctly. This probably means some additional work
in the parser.
But having had talking around this point, IMHO a patch that allows flexbility
is important. IMHO should be ok to commit a patch as outlined by Oleg.
Robert
> o.a.j.m.message.Header#writeTo violates RFC 822
> -----------------------------------------------
>
> Key: MIME4J-34
> URL: https://issues.apache.org/jira/browse/MIME4J-34
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.3
> Reporter: Oleg Kalnichevski
> Attachments: mimeheader.patch, mimeheader.patch
>
>
> The Header#writeTo method uses the content charset instead of US-ASCII
> required by the RFC 822. Same problem exists in the Multipart#writeTo.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
