Prev   Next

2.9. Translation server configuration

This special section describes how to configure a server that acts as a translation server. If you don't want to translate a language you can skip this section.

If you want to create a new language and translate it, please contact us first. The OLAT team operates a public translation server where all bundled languages are translated. You don't have to configure and operate your own translation server, we do this all for you!

So, this chapter is only relevant for people who want to translate their own languages and don't want to contribute the language to the OLAT project.

Here is what you have to do:

  1. Configure the OALT application to run properly, if everything works, proceed with next

  2. Check out the OLAT source code project (olat3) from CVS or unzip the sources from a ZIP. If you build OLAT in step 1, you can also reuse this OLAT sources.

    Configure the OLAT project source path to this olatcore project in your olat.local.properties:

    i18n.application.src.dir=/opt/olat3/webapp/WEB-INF/src

  3. Check out the application i18n project (olat3_i18n) from CVS or unzip the sources from a ZIP

    Maybe this project is stored in your private CVS and not named like the example below. You could also use any other path to an existing directory here, this directory will contain the new created languages from your server. Configure the i18n path for the application files in your olat.local.properties:

    i18n.application.opt.src.dir = /opt/olat3_i18n/src/main/java

  4. Check out the olatcore project (olatcore) from CVS or unzip the sources from a ZIP

    Configure the OLAT-Core source path to this olatcore project in your olat.local.properties. Alternatively you can set it to ${olatcore.dir} if this variable is set to the core source.:

    i18n.core.src.dir=/opt/olatcore/src/main/java

  5. Check out the olatcore i18n project (olatcore_i18n) from CVS or unzip the sources from a ZIP

    This could well point to the same directory as the i18n application source dir! Configure the i18n path for the olatcore files in your olat.local.properties:

    i18n.core.opt.src.dir = /opt/olatcore_i18n/src/main/java

  6. Configure the system as a translation server

    Set is.translation.server=true in your olat.local.properties file

  7. Remove the bundled language jar files from your webapp/lib directory to reduce conflicts (in olat/target/webapp...)

    webapp/WEB-INF/lib/olatcore_i18n_all-SNAPSHOT.jar

    webapp/WEB-INF/lib/olat3_i18n_all-SNAPSHOT.jar

  8. Run ant config-all and restart tomcat.

When loggin in as administrator you will now see a menu item Administration > Translation Tool. Create a new language first as described above and then start the translation tool to translate your new language.

Prev Up Next
 Home