[
http://jira.codehaus.org/browse/MSITE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120207
]
Benjamin Bentmann commented on MSITE-287:
-----------------------------------------
bq. My guess is that it was a known limitation due to the old MSITE-19.
Scary...
bq. Anyway, I am in favour to change it to ISO-8859-1 with unicode escapes.
"ISO-8859-1 with unicode escapes" *is* ISO-8859-1. If that's OK, there's no
need to introduce those ugly Unicode escapes for a German bundle (the German
alphabet is part of Latin-1). Or did you mean ASCII? While this would require
Unicode escapes for quite every language except English, it would be quite a
bullet-proof encoding in case Maven still has problems with such a thing.
> 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
