You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Localization of Plugins

This page documents how well the reporting plugins have been localized.

Reporting Plugin

de

fr

sv

es

pt_BR

l10n report

SVN

Changelog

(tick)

(error)

MCHANGELOG-105

(error)

(error)

not published

SVN

Changes

(tick)

(tick)

(tick)

(error)

(error)

l10n report

SVN

Checkstyle

(tick)

(tick)

(tick)

(error)

(tick)

l10n report

SVN

Dependency

(tick)

(error)

MDEP-248

(error)

(error)

not published

SVN

DOAP

(tick)

(tick)

(error)

(tick)

(error)

l10n report

SVN

Javadoc

(tick)

(tick)

MJAVADOC-277

(error)

(error)

l10n report

SVN

JXR

(tick)

(tick)

JXR-77

(error)

(error)

not published

SVN

PMD

(tick)

(tick)

MPMD-111

(error)

(error)

not published

SVN

Plugin

(tick)

(tick)

MPLUGIN-166

(error)

(error)

not published

SVN

Surefire report

(tick)

(error)

SUREFIRE-585

(error)

(error)

not published

SVN

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 to src/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.

Tools

  • No labels