Internationalization/Localization Language Properties

Compatibility :	3.5.0
Editions :
Platforms :

This property specifies the output language of the Wrapper. Please note that on UNIX based systems, this value has to be the valid name of an installed locale.

In order to get the installed and available locales on an UNIX system, please run "locale -a"

$ locale -a
C
de_AT.utf8
de_BE.utf8
de_CH.utf8
de_DE.utf8
de_LI.utf8
de_LU.utf8
en_AG
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_DK.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_IN
en_NG
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US.utf8
en_ZA.utf8
en_ZW.utf8
ja_JP.eucjp
ja_JP.shiftjis
ja_JP.utf8
POSIX

You only need to put the language_Country abbrevention for this property. The encoding will be set in the wrapper.lang.encoding property.

wrapper.lang=ja_JP

Compatibility :	3.5.0
Editions :
Platforms :

This property specifies the encoding of the Wrapper process. The selected property has to be installed in order to make use of it. If no encoding has been specified, the Wrapper tries to use the encoding of the console, which launched the Wrapper.

wrapper.lang.encoding=eucJP

Compatibility :	3.5.0
Editions :
Platforms :

This property sets the location of the language files. The default value is "../lang".

wrapper.lang.folder=lang

Please note that relative pathes are relative to the location of the Wrapper binary, not the location from where the command has been launched nor the location of the configuration file.

Compatibility :	3.5.0
Editions :
Platforms :

This property sets the domain of the binary and the library mo files. If you want to rename the wrapper_XX.mo and wrapperjni_XX.mo file, you need to set this property accordingly.

wrapper.lang.domain=myapp

This will cause the Wrapper to look for myapp_XX.mo or myappjni_XX.mo file when loading the language resources.