language

Creating an intelligent language pack

For quite some time I have been maintaining the Dutch language pack for SugarCRM while working at Madcap. A number of users turned out to have a simple request: Change the name of a module throughout the application. However simple this may sound, it proves to be a tiresome job when using Sugar's flat language files. This article shows a solution for this common problem which requires a lot less effort to implement.

Custom language files

Translating Sugar and adding custom language strings and/or dropdown arrays can be a bit tricky. Basically, the problem is: When there's an error, you're on your own. This means that fields without a translation, or undefined dropdowns will usually just stay empty. So, we dig in.

Syndicate content