Introduction

These are some guidelines to help you with Bedework internationalization. Internationalization of a calendaring system is not only a question of translations of the names and literals, there are also some other differences from one country or culture to another on how time is named or handled. For example, for some the weeks start on Sunday, for others on Monday.   

Nevertheless, Bedework is designed to easily manage language and calendaring internationalization issues.   

In order to handle your locale needs correctly, all the members in the chain from browser to the backend DB must be configured accordingly. This section, as an example, will show how Spanish localization is accomplished.  The same procedure can be used for any language.

Overview for the impatient

The advice found in the remainder of this chapter can be summarized by the following checklist:

1.   Check that the Operating System (OS) has your locale configured

(For example, setting LC_ALL=es_ES.UTF-8  and  LANG=es_ES.UTF-8 ,  check control panels in windows).

2.    Check that your JVM is running with the right locale configuration.

(For example, look at your JAVA_OPTS for -Duser.timezone=Europe/Madrid -Duser.country=ES -Duser.language=es )

3.    Check your DB can handle multilingual data.  

(Details depends on your DBMS (Oracle, MySql, etc.), but usually DB must be configured  UTF-8)

4.    Check you have included your locale pages (xsl, css, etc) in the correct application directory.

(Bedework has english, spanish and german translations included. These translations handle the translation of literals (‘save’, ‘cancel’, etc.) for your language.  If you need other language than these, take a look at a folder like jboss-5.1.0.GA\server\default\deploy\ROOT.war\calrsrc.MainCampus\es_ES\ and there you can find the files used for spanish translation as an example.  You should add a new folder  ./ROOT.war/calrsrc.MainCampus/YOUR_LANG  with your translation)

5.    Ensure that the Bedework administrative client includes the languages you intend to deploy on the "Manage System Preferences" page

(In the admin client, visit System --> Manage System Preferences, and enter the locales (e.g. en_US,es_ES ) in the "Supported Locales" field.)

6.    If client does not get the proper locale pages, check he has correctly configured the language options of his navigator.

(Bedework, tries to show the calendar using the preferred language set in the browser; check your browser's language settings.)

Summarizing, for example, you can make a custom script to start Bedework on your language as this:

# Custom script for launching quickstart in spanish. 

JAVA_HOME=/home/bedework/jdk160_27
PATH=$PATH:$JAVA_HOME/bin

export JAVA_HOME PATH

LC_ALL=es_ES.utf8
LANG=es_ES.utf8
export LC_ALL LANG

JAVA_OPTS="$JAVA_OPTS -Duser.timezone=Europe/Madrid -Duser.country=ES -Duser.language=es -Dfile.encoding=UTF-8 -Duser.variant=ES "
export JAVA_OPTS

cd /home/bedework/quickstart-3.7

echo "Starting Apache DS in the background..."

./bw -quickstart dirstart >/home/bedework/last_bedework_startup.log &

echo "Starting Bedework in the background..."

./startjboss -heap 512M >>/home/bedework/last_bedework_startup.log &