Documentation Center

Troubleshooting issues related to language codes and custom cultures

WorldServer supports a very large number of custom cultures. In certain situations, this might lead to language code inconsistencies or to compatibility issues with other SDL tools, such as SDL Trados Studio. This section aims to help you prevent such issues or to provide quicker resolutions.

The most common issues related to custom cultures include:
  1. Inconsistent language codes between WorldServer and Studio.
  2. WorldServer not recognizing a certain culture.
  3. Custom cultures not being installed at all or an older version being installed.
  4. Windows not supporting a certain culture.

Inconsistent language codes

As more and more cultures are added into Studio or existing language codes are changed, WorldServer needs to align with these changes.

If you notice that your version of WorldServer uses a different language code compared to your version of Studio, map the Studio culture to the WorldServer one by adding an entry to the exchange.properties file. You can find more information about mapping custom cultures in this topic, as part of the description of the studioLocaleMapping property.

WorldServer does not recognize a certain culture

For WorldServer versions earlier than 11.4.3, the stack trace might indicate an error thrown by WorldServer:
An error occurred while saving the asset into AIS. 
Details: com.idiominc.wssdk.asset.WSAssetSegmentationException: Culture is not supported. 
Parameter name: name en-MO is an invalid culture identifier.

If this is the case, please create a ticket to further investigate the issue and to find solutions. Make sure you specify the WorldServer version, the .NET Framework version, and the Windows Server version that you are running.

Starting with WorldServer 11.4.3, this error is no longer thrown and the code will continue to be executed.

Custom cultures were not installed or an older version was installed

SDL custom cultures are used by the File Type Support (FTS) Server and by SDL Trados Studio. When you execute SDLCustomCultures.msi, a number of .nlp files are added under C:\Windows\Globalization. When SDL Custom Cultures are installed, the Globalization folder should contain more than 400 files.

Windows does not support the specified culture

If Windows does not recognize a language and that language is not defined in the Globalization folder as an .nlp file, the FTS Server will throw an error. There are two possible errors:
  • One is thrown when the unrecognized language is used as the source locale in a project and the error occurs during the segmentation process. For example: System.Globalization.CultureNotFoundException: Culture is not supported. Parameter name: name hat-HT is an invalid culture identifier. at System.Globalization.CultureInfo.GetCultureInfo(String name).
  • The other one is thrown when the unrecognized language is used as the target locale and the error occurs during the asset saving process. For example: Culture is not supported. Parameter name: name my_MM is an invalid culture identifier.
In this case, you should do the following:
  • Make sure that you have the latest version of SDL Custom Cultures installed on your machine.
  • Check the logs and make sure that the language code and the mapping entry in the exchange.properties file are correct (for example, fr_FR instead of fr-FR).
  • Make sure that you have the appropriate Windows Server and .NET Framework versions.
  • Check the Windows documentation and see whether the language is defined in Windows.
Any FTS Server errors will most likely occur on Windows Server 2012 or earlier. Newer versions of Windows Server (starting with Windows Server 2016) seem to no longer throw an unsupported culture error; they will continue the execution of the step with the unrecognized culture.

Contacting Support

In case none of these troubleshooting steps helped you identify and fix the issue, log a ticket to SDL Technical Support. Make sure you include the following details:
  • The WorldServer version that you encountered the issue on.
  • The Windows Server and .NET Framework versions that you are running on the FTS Server machine.
  • Any information regarding the SDLCustomCultures.msi installation.