...
Some of the string values and date formats that appear in client’s navigator browser are taken by Bedework from the locale management of the OS of server sideoperating system on the server. The JVM on which Bedework runs on, takes some of the string values and date formats from the underlying OS using java locale and , date and time classes. So it is quite important that both, JVM and OS, are configured correctly.
...
Code Block |
---|
$ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= |
In this case “English “en_US" (English – United States” seems to be States) is the default language configuration. To change it to “Spanish – Spain”."es_ES" (Spanish – Spain) use the following commands:
Code Block |
---|
$ export LC_ALL=es_ES.UTF-8 $ export LANG=es_ES.UTF-8 |
...
For Unix boxes: Your server could may not have all possible locale configurations installed. Some Unix(es) gives you some information about it with non-priviledged commands. In Linux (Fedora, CentOS, etc) the command “set” gives you some info.
Code Block |
---|
..... SUPPORTED=eu_ES.UTF-8:eu_ES:eu:en_US.UTF-8:en_US:en:fr_FR.UTF-8:fr_FR:fr:de_DE.UTF-8:de_DE:de:es_ES.UTF-8:es_ES:es ..... |
Note | ||
---|---|---|
| ||
Be aware that you can configure and issue the “$export LC_ALL=<locale>” even when that locale is not really supported on your installation. Even more, after that unsupported configuration, the “locale” command shows supposed current locale even when the OS does not really manage it if it is not installed. |
JVM Checks
JVM takes some environment values from the OS ones by default. To check the default locale (among others) your JVM is using you can use this class:
...