6 Translations

The Translations Setup screen present in the desktop application enables you to maintain translations for Operations UI (desktop UI) client side keys such as UI labels and error messages as well as Server side translations like Context Type, Carrier, Reason codes, Notifications, server side error messages and so on, for all the supported locales.

The system supports the following locales:

Arabic

Chinese (Simplified)

Chinese (Traditional)

Croatian

Dutch

English (American)

French (Parisian)

German

Greek

Hungarian

Italian

Japanese

Korean

Polish

Portuguese (Brazilian)

Russian

Spanish (Standard)

Swedish

Turkish

Apart from these, extension hooks are added for following new locales in the system:

Albanian

Armenian

Azerbaijani

Belarusian

Bengali

Bosnian

Bulgarian

Burmese

Czech

Danish

Estonian

Filipino

Finnish

Georgian

Hebrew

Hindi

Indonesian

Kazakh

Khmer

Lao

Latvian

Lithuanian

Malay

Norwegian

Romanian

Serbian

Slovak

Slovene

Thai

Ukrainian

Urdu

Uzbek

Vietnamese

For these additional languages, the retailer should add translations for the keys. If there are no translations available in a particular language, the keys will be displayed in English. For server side keys, new translation records can only be added via Data setup screens like Inventory Adjustment Reason, Shipment Reason, Carrier, Carrier Service and so on. Addition of records is not allowed on the Translation Setup screen. If a new record gets added via Data setup screens, the translation record for it gets displayed in the Translation setup screen automatically. These translation records will have a translated value for the locale that data record was created in. You need to provide values for other locales for which you can use the translation setup screen.

You can look up the translation record and update it with the translation. The translation setup screen does not support deletion of translation records.

Figure 6-1 Bundle Selection

If the user selects Bundle Type as Operations UI, the list of client side keys will be listed for the locale selected and the user will be able to maintain them.

If the user selects Bundle Type as Server, the list of server side keys will be listed for the locale selected and the user will be able to maintain them.

Figure 6-2 Translation Setup Screen

The screen is accessed via the menu: Admin / Translations / Translation Setup. The user must have Access Translations permission for the Translations and Translations setup menu option to display. The screen displays an empty table by default. Choose a locale in order for the table to be populated with the translation records for that locale.

You can select a record to edit. You can update both the translation and description. Any changes made to the translation records from this screen will reflect both in the mobile application and the desktop application. The changes made will reflect in the applications immediately.

Export / Import File

The user will also be able to update translations in bulk using the Export/ Import feature provided in this screen. This is achieved by importing a file which has the updated translations for a particular language.

Figure 6-3 Import Translation File Popup

To help the user with preparing the file with the translations, there is an option to download the existing translations for the language. The file downloaded will be for the locale selected. The translation records downloaded in the file will be for both the Bundle Types that is, Server and Operations UI, irrespective of the Bundle Type selected.

Only the translation keys will be updated into the system. Descriptions are common for all languages and will not be updated if any changes are made.

If there are any errors encountered during the import processing of the file, an error file is generated which lists the errors along with the records that caused the error.