Acumatica provides the functionality to use different languages for different companies, making it easy to translate user interface and wikis in multiple languages. For companies operating in different countries, this reinforces the benefit of involving all users (without per-seat licensing premium) and delivering a better user experience.
A locale is a standard language identifier. Acumatica uses US English as the default locale (en for English, US for the country) and taps into the list of locales provided by Microsoft .NET.
The first step is to add a new locale for the language of choice and activate it. In my example, I added Japanese (ja-JP). I can also set preferences such as date/time format and decimal symbol for the locales.
Figure 1. Add a new locale
Next, we need to create a translation dictionary. In Translation Dictionaries, Acumatica displays labels, UI elements, error messages, reports, etc. that it uses throughout the system. In simplistic terms, translation is a lookup or search/replace of a phrase from one language to another.
To setup translation for a few phrases, I added the Japanese phrases as showed below.
Figure 2. Add translated phrases matching the source values
With thousands of phrases and labels in Acumatica, it is easier to export the default values to Excel and import the list of translation. As new reports or customization projects are added, Acumatica allows users to scan the system for new phrases using the ‘Collect Strings’ function and establish translation for the new additions.
To see the translation, first I lookup where the source phrases are used.
Figure 3. View usage details
Here is a before-after comparison.
Figure 4a. Before translation
Figure 4b. After translation