The NetarchiveSuite web pages are internationalized, that is they are ready to be translated into other languages. The default distribution contains a default (English) version and Danish, Italian, French and German versions, but adding a new language does not take any coding. All translatable strings are collected in four resource bundles. The default (English) files are

./common/common-core/src/main/resources/dk/netarkivet/common/Translations.properties
./monitor/monitor-core/src/main/resources/dk/netarkivet/monitor/Translations.properties
./archive/archive-core/src/main/resources/dk/netarkivet/archive/Translations.properties
./harvester/harvester-core/src/main/resources/dk/netarkivet/harvester/Translations.properties

under the source root.

To translate to a new language, first copy each of these files to a file in the same directory, but with _XX after Translations, where XX is the Unicode language code for the language you're going to translate into, e.g. if you're translating into Limburgish, use `Translations_li.properties`. If you're translating into a language that has different versions for different countries, you may need to use _XX_YY, where XX is the language code and YY is the ISO country code, e.g. `Translations_fr_CA.properties` for Canadian French. Then edit each of the new files to have your translation instead of the English translation for each line. According to the Java documentation (specifically the Javadoc of the Properties class) resource bundles should use iso-8859-1 with escaped Unicode for all other characters. It is good practice to use escaped Unicode for all non-ASCII characters as this results in files which are more-easily shared between different text-editing environments.

The translation has not been done throughout the code, only in the web-related parts. Thus log messages, error messages and javadoc are in English and cannot be translated through the resource bundles.