Real Studio makes it very easy to create localized applications. When you use Dynamic Constants and create strings based on language the application will switch, at runtime, to the proper language. It’s pretty easy and straightforward.
In Windows, the only thing you have to do to set the language to something other than the default language is to change the Date/Time format settings in the control panel in Windows 7 to the language (and variation) of choice. This makes it very easy to test since you can have a different OS language than your apps (even if you can’t read the language).
This week, however, we had a client take our Spanish (and English) localized apps to a country in South America for installation only to find out that their default configuration is to leave everything in English. That meant the apps wouldn’t run in Spanish. I have no idea why they do this, but it certainly wasn’t what my client expected!
Major bummer and we all went into panic mode. We went through various ideas on how to get work around the situation (and all of them ugly) until we stumbled upon the idea that the en.mo and es.mo files (located in the Resources directory next to the executable) could be swapped. So, we deleted the en.mo file and then renamed the es.mo to en.mo.
Voila! Problem solved. The client is happy, the folks on site are happy, and ultimately that makes me happy. The only minor issue is that the apps won’t run in English without swapping the files around again.