Forum Problems Installing LAMS: LAMS in English on non-English operating systems problem

By: Ernie Ghiglione

[ Reply | Forward ]

In the past few weeks, we've been receiving reports of LAMS installations that were behaving a bit funny with languages.

The problem was that in Author, some activities in the activity list (the tools in the left hand side of the screen) would appear in a difference language even when LAMS server was set to be running on English. (see attached picture as an example- Notebook, noticeboard, Submit and others appear in Spanish, however the server is set to be in English)

Lily from China was the first to raise this report and we weren't able to replicate this in Sydney. Later on, Ximena from Spain pointed out that she was having a similar problem when she installed LAMS in an Spanish OS and LAMS was set to run in English.

We realized that the language these activities were showing was the OS language. So in the case of Lily, the tools would appear in Chinese and for Ximena, in Spanish.

(Note that this problem does not occur if you are running LAMS in the same language as your OS. Which is why this was a really uncommon issue for other people)

Dapeng and Fiona looked into this and we realize there's an issue with the how Spring and Struts deal with the translationd file (read the whole extend in the bug tracker).

The good news is that this is now fixed

The solution involves applying the Language Pack for those of you who have used the Windows installer. The Language Pack will be available next week.

For those of you who installed LAMS from source or have customized installation (or even for those who used the Windows installer and want to be a bit adventurous) then here are the instructions:

LAMS 2.0 stores all the dictionary files in the follow directory:

(your-jboss-dir)/server/default/deploy/lams.ear/lams-dictionary.jar/org/lamsfoundation/lams

In there you will see ApplicationResource_xx_YY.properties files for each of the modules in LAMS (the directories in this folder).

All you would need to do is to copy the ApplicationResources.properties file to a file called ApplicationsResources_en_AU.properties in each of the directories of this folder. For instance, you need to get to the admin directory and copy the ApplicationResources.properties to a ApplicationsResources_en_AU.properties in the *same* directory. The ApplicationsResources_en_AU.properties does not exist so you'll be creating it from teh ApplicationsResources.properties file.

Keep doing this for all the other directories. Then restart LAMS and that should solve this problem straight away.

If you have any problems, just post your questions here.

Thanks,

Ernie

Posted by Ernie Ghiglione