[jira] Commented: (MSITE-287) Clarify/fix documentation about encoding for translated resource bundles.

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MSITE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=137762#action_137762 ] 

Dennis Lundberg commented on MSITE-287:
---------------------------------------

So where do we stand on this?

1. Submissions should use UTF-8 encoding.
2. Submissions should use ISO-8859-1 encoding and can make use of all accented characters in there. Characters not in there must use unicode escape sequences.
3. Submissions should use ISO-8859-1 encoding, but can only use US-ASCII characters. Any other characters, including accented characters included in Latin 1, must use unicode escape sequences.

I vote for 2.

> Clarify/fix documentation about encoding for translated resource bundles.
> -------------------------------------------------------------------------
>
>                 Key: MSITE-287
>                 URL: http://jira.codehaus.org/browse/MSITE-287
>             Project: Maven 2.x Site Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0-beta-6
>            Reporter: Benjamin Bentmann
>            Priority: Minor
>
> According to http://maven.apache.org/plugins/maven-site-plugin/i18n.html translators are expected to provide their properties files in UTF-8 encoding. However, the JRE reads properties files using ISO-8859-1 encoding (see [class javadoc for PropertyResourceBundle|http://java.sun.com/javase/6/docs/api/java/util/PropertyResourceBundle.html]).
> Either the documentation should be fixed to state ISO-8859-1 or it should be made clear why Maven requires another encoding than usual.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira