First check whether the SDL custom cultures
are installed on the Application
server (available starting from version 10.4.x.). If they are already installed then follow the below workaround.
Add a mapping to the Worldserver
configuration file exchange.properties
, to map the above generic locale to a locale that is supported by the Studio File Types, for example, map as below (make sure the studioLocaleMapping ID is unique
studioLocaleMappingHM = Hmong, de-DE
studioLocaleMappingRU-MD = Russian (Moldova), ru-RU
studioLocaleMappingTG = Tigrigna (Eritrea), ti-ER
studioLocaleMappingTG2 = Tigrigna (Ethiopic), ti-ET
studioLocaleMappingNO = Norwegian, nb-NO
studioLocaleMappingMK = Macedonian, mk-MK
studioLocaleMappingBurmese = Burmese, my-MM
If you are not sure about the language code supported by SDL Trados Studio
- Open any test file with the affected target language as a standalone file in SDL Trados Studio.
- Do a Save: this action will create a bilingual Studio file in SDLXLIFF format.
- Open the SDLXLIFF file in Notepad and next to target-language= you will find the language code supported by SDL Trados Studio.
- Use that language code for mapping.
After adding the property to exchange.properties
file, save your changes. Restart WorldServer
and complete the Autoerror or try again to export ot a WSXZ package format.