Localization of Plugins
This page documents how well the reporting plugins have been localized, and how you can help us by providing translations in your own language.
Reporting Plugin |
de |
es |
fr |
pt_BR |
sv |
l10n report |
SVN |
---|---|---|---|---|---|---|---|
Changelog |
|
|
|
|
|
||
Changes |
|
|
|
|
|
||
Checkstyle |
|
|
|
|
|
||
Dependency |
|
|
|
|
not published |
||
DOAP |
|
|
|
|
|
||
Javadoc |
|
|
|
|
|
||
JXR |
|
|
|
|
|
||
PMD |
|
|
|
|
|
||
Plugin |
|
|
|
|
|
||
Project Info Reports |
|
|
|
|
|
||
Surefire report |
|
|
|
|
|
||
Site |
|
|
|
|
|
You can see the localization progress of Maven Site Plugin and Maven Project Info Reports Plugin on the Site Plugin site.
Localizing a Plugin
- Check out the source code for the plugin you want to add a translation for.
- Find the resource bundles that needs to be translated. They are often found in the
src/main/resources
folder. - Copy the basefile for the bundle, i.e. the one without a language extension. The copy should have the same name as the original file, except for the addition of a language extension. If, for example, you want to translate the Changes Plugin into Spanish, you would copy
src/main/resources/scm-activity.properties
tosrc/main/resources/scm-activity_es.properties
. - Edit the new file and translate all the properties.
- Convert the new file so that all non-US-ASCII characters are transformed into Unicode escapes, see below for tools that can help with this.
- Create an issue in JIRA for the plugin in question, with a description like: "Add Spanish translation". Take note of the issue number.
- Create a patch file that contains your new translation.
svn diff > MYISSUE-123.patch
Tools
There is a command line tool called native2ascii that can be used to convert a text file to use Unicode-encoded characters instead of native-encoded characters. This is part of the Java SDK and you can read more about it here. You use it like this:
native2ascii scm-activity_es.properties scm-activity_es-encoded.properties