Child pages
  • LAMS Language Packs

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

LAMS 2.0 allows the language files to be updated separately to the software.

For installations done using the Windows Installer, this will be done via Windows Language Packs. In some cases you will get new languages, other times it will just be an update to existing languages. The updates are cumulative - so you should always install the latest language pack. The date of release is included in the language pack name, in the format YYYY-MM-DD.

For other installations, a manual version of the language update is available as Unix Language Packs. It is designed for Unix/Linux but as it is a manual process hopefully you should be able to use the same files for a Windows or Macintosh version of LAMS that was built from the source code.

The language packs can be downloaded from our Downloads page.

We only release languages that have all the Flash components translated - other languages currently under translation are not included. The Flash clients doesn't cope well if the translations are missing and the languages are fully translated for the Flash modules tend to be the languages that are either complete or almost complete for LAMS overall.

Windows Language Packs


You must have LAMS installed via the Windows installer. The Language Pack installer requires information that was recorded in the registry when the Windows Installer was run.

This language pack works just like an installer. Just download it (LAMSLanguagePack-YYYY-MM-DD.exe), double click on it, follow the instructions and voila!

You can have LAMS either running or shutdown when you run the installer. If you have left LAMS running, then after you completed applying the language pack you must re-start LAMS to see all the new language updates.

If you are unsure of whether or not you have installed a language pack, then running the installer will check the installation date. If you have already installed this version or a new version, then the installer won't make any changes. The installer will replace the existing language files and update the list of languages (if appropriate).

If something goes wrong, the original language files are backed up to: $INSTDIR\jboss-4.0.2\server\default\deploy\lams.ear\lams-dictionary.jar\backup.

The flash language files are also backed up in this same archive. To retrieve the flash files you will need to extract the files, then move the flashxml folder to: $INSTDIR\jboss-4.0.2\server\default\deploy\lams.ear\lams-central.war\
then restart lams. This applies only to language packs released after the original (LAMSLanguagePack-2006-12-22)

Unix Language Packs

This language pack is in the form of a .tar.gz archive. You will be required to extract the files to the correct locations and run a script in order to install the language pack successfully.

Below are some steps you can follow to ensure that the language pack installs correctly. If you have any problems or questions, please post them at

1) Back up existing language files. You need to backup files in the following directories

Code Block
(jboss directory)/server/default/deploy/lams.ear/lams-dictionary.jar
(jboss directory)/server/default/deploy/lams.ear/lams-central.war/flashxml

2) In your lams-unix-language_pack-yyyy-mm-dd directory there should be two folders, one named lams-dictionary.jar and one named flash xml. You will need to copy the files in these directories to the         following existing directories respectively, overwiting any existing files:

Code Block
(jboss directory)/server/default/deploy/lams.ear/lams-dictionary.jar
(jboss directory)/server/default/deploy/lams.ear/lams-central.war/flashxml

3) Go to the lams-unix-language_pack-yyyy-mm-dd directory. Run the sql script on your
lams database:

Code Block
$ mysql (database name) \-u(username) \-p(password) < updateLocales.sql

If successful, the console should print output similar to the output below:

learning_library_id    title
12                           Resources and Forum
13                           Chat and Scribe
14                           Forum and Scribe

4) This output is important. You will it need to check the directory names in the location:

Code Block
(jboss directory)server/default/deploy/lams.ear/lams-dictionary.jar/org/lamsfoundation/lams/library

Currently, there should be three directories with names resourceforum, chatscribe and forumscribe. The files from these three directories have to go into directories named "llid[learning_library_id]" where the learning_library_id is the number obtained from the result of the SQL script.

In the above example, the files from the resourceforum directory need to go in a directory called llid2, giving a full path:

Code Block
(jboss directory)/server/default/deploy/lams.ear/lams-dictionary.jar/org/lamsfoundation/lams/library/llid2

So, for each entry in the sql output from Step 3, work out the required directory name.

If the directory already exists then copy the files from the resourceforum/chatscribe/forumscribe directory to the existing llid<number> directory and delete the resourceforum/chatscribe/forumscribe directory.
e.g. if the llid12 directory already exists then copy the files from the resourceforum directory to the llid12 directory and delete the resourceforum directory.

If the directory doesn't exist, you can just rename the resourceforum/chatscribe/forumscribe directory to the llid<number>.

5) Now the language pack should be ready. Restart LAMS to allow the changes to take effect