[
https://issues.apache.org/jira/browse/EMAIL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Corey Scott updated EMAIL-79:
-----------------------------
Attachment: EMAIL-79-patch.txt
Edvin,
I am not sure this is what you wanted but the changes contained are making the
simple (and HTML) email classes utilize the charset and content type settings
better than they were. (in some cases they werent being used previously)
You still have to do a email.setCharset() call in order to ensure both the
subject and message bodies have the encoding set but I personally feel this is
acceptable. Perhaps because I dont see how the encoding can be reliably
determined dynamically or even if it could, it is in side the scope of this
library.
> SimpleEmail#setMsg() with UTF-8 content honors correct charset in header, but
> doesn't encode the content correctly
> ------------------------------------------------------------------------------------------------------------------
>
> Key: EMAIL-79
> URL: https://issues.apache.org/jira/browse/EMAIL-79
> Project: Commons Email
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Windows Vista, JDK 1.6.0_06
> Reporter: Edvin Syse
> Priority: Minor
> Attachments: EMAIL-79-patch.txt, EmailTest.zip
>
>
> When I create a new SimpleEmail and use setMsg(some-utf8-text), the
> Content-Type header of the generated email correctly changes to UTF-8, but
> the content is not encoded correctly.
> Adding setCharset("UTF-8") solves the problem, but that shouldn't be needed,
> as the change of Content-Type header indicates.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
