Posts Tagged ‘Localization’

Localization of AR applications in BMC Remedy ARSystem

July 1st, 2009

When my client asked me work on localizing the existing application to Spanish, I felt challenging only because I don’t know how to read/write Spanish.

Even though I haven’t worked on Localizations before, I have an understanding how to achieve this. But the customization of error messages which are generated by AR System are tough to do, because some of the messages are generated by API.

How to Check Server Language:
– V6.3/7.0 – Admin Tool, File >> Server Information >> Configuration >> Server Language
– v7.1/7.5 – User Tool
, Admin Panel >> Server Information >> Configuration >>Server Language

How to Check/Change User Locale:
– User Tool, Tools >> Options >> Locale

How to turn on Localization of Error Messages:
– V6.3/7.0 – Admin Tool, File >> Server Information >> Advanced >> Localize Server (check box)
– v7.1/7.5 – User Tool
, Admin Panel >> Server Information >> Advanced >> Localize Server (check box)

All the system messages are called “COre” messages with message numbers less than 1000, the process of the messages is done in differenr ways, like some of the messages are generated AR Server itself, some by API(With out server involvement) and others based on AR locale of the logged in user.

These are categorized as,
1. Core Messages – Returned by AR Server itself
ex: message #307 – Required Field musst have a value during Submit
2. API Based – Returns a message based on server language
ex: message #303 – “No such form on Server”

The thing with localization is not many clients require one, but this particular client has helpdesks in more than 15 countries. Even though most of them are English speaking countries, but few have spanish, portugeese and xxxxxxx

Locale keyword syntax is $LOCALE$. ex: en_US. The first two characters gives the language of the user logged in and last two characters are the country. Ar system localization is good in areas like using same locale for several countries which use same language. For example, English is the common language across several countries, but there are variations in it.
English in great britan is different from USA. We can differentiate it if we want and use the same locale.

If we make a form view with just the language part like en(English) or es(Spanish), we can use for all the Countries which has english(en) or Spanish(es) as their language.

Regarding the localization of AR system messages, the AR system message catalog option should be selected at the server level. When this option is enabled, all the system messages will be read from “AR System Message catalog” form entries. One can directly change the messages in this form which will be used for all system messages.

For any other language than sever language we need to add entries in this form with the name of the AL or Filter and specify the locale for which it will be used.

Feel free to ask if any of you need some info regarding Localizations, will be happy to help.

Till then, Njoy


<!– AddThis Button BEGIN –>
<a href=”” onmouseover=”return addthis_open(this, ”, ‘[URL]’, ‘[TITLE]’)” onmouseout=”addthis_close()” onclick=”return addthis_sendto()”><img src=”” width=”125″ height=”16″ alt=”Bookmark and Share” style=”border:0″/></a><script type=”text/javascript” src=””></script>
<!– AddThis Button END –>

Bookmark and Share

%d bloggers like this: