DevExpress UI Localization Service

• Jun 06, 2024
• 4 minutes to read

This topic describes how to use the DevExpress Localization Service to obtain and edit translated resources (strings) for the DevExpress UI Controls.

Log into the DevExpress website to get started.

Add a Translation

Open the DevExpress Localization Service. Click Add a Translation. Specify the DevExpress version and the language in the pop-up dialog.

Modify, Delete or Copy Translation

You can perform the following actions for every translation that you create:

• Modify translated strings

  Pre-defined translations are available for several languages. The DevExpress Localization Service displays the total number of strings, all the translated strings, and your changes. Click the Modify link associated with the language and version to review each translation and make changes.

• Delete a translation from your language set

  Click Delete to remove a language from your set. When you delete a translation, you lose all modifications.

• Copy a translation

  You can copy your existing translations and apply them to a different release version to simplify the transition from one version to another. When you click the Copy link for a given translation, you should specify the target version for copied translations.

Customize Localization Resources

If you choose to Modify a translation, you are directed to the Customize Localization Resources page. This page allows you to do the following:

• Filter the values in the translation table

  Use the filter bar to restrict the set of resources to those you wish to view within the translation table. You can restrict values by platform, module, and translation state.

• Modify and Save individual translations

  The translation table includes the English version of a resource, the suggested translation (if translated), and an empty field for your custom translation. Click Save to record your changes if you make changes to a translation.

  Important

  The suggested translation is not included into the downloaded localization resources. To include it, copy the Suggested Translation to the Your Translation field.

• Download your translations

  When you made the changes to a translation, click the Download button to download all modified localization resources. Once the build process is completed, the Localization Service sends you a link to a signed self-extracting archive to your email.

  To unpack a self-extracting archive on your Mac/Linux PC, you can use the same CLI as with regular archives:

  7z x windowsfile.exe
  OR  
  unzip windowsfile.exe  
  

  When you unpack the downloaded executable file, you find a folder with the localization resources (satellite assemblies and JSON files).

• To navigate to the list of languages you selected in Step 2, click Return to Your Translations List.

  

What’s Next

• Localization for ASP.NET Controls
• Localization for Blazor Components
• Localization for WinForms Controls
• Localization for WPF Controls
• Localization for Dashboard Controls
• Localization for Reporting
• Localization for eXpressApp Framework

Localize DevExpress Controls of Versions Prior to v12.1

Localization Service supports DevExpress .NET components starting with v12.1. If you use an older version, you can use the following links to download the default satellite assemblies:

• DXperience_v11.2_(2012-07-25)
• DXperience_v11.1_(2011-12-09)
• DXperience_v10.2_(2011-09-19)
• DXperience_v10.1_(2011-06-16)
• DXperience_v9.3_(2010-10-08)
• DXperience_v9.2_(2010-10-28)
• DXperience_v9.1_(2009-09-10)
• DXperience_v8.3_(2009-09-10)
• DXperience_v8.2_(2009-01-13)
• DXperience_v8.1_(2009-01-13)
• DXperience_v7.3_(2008-10-22)
• DXperience_v7.2_(2008-02-25)
• DXperience_v7.1_(2008-02-29)
• DXperience_6.3_(2007-06-19)
• DXperience_6.2_(2007-02-27)
• DXperience_6.1_(2007-02-09)
• WinForms_2.2.5_(2006-03-17)
• WinForms_1.3.1_(2005-12-09)

Modify Satellite Assemblies in Versions Prior to v12.1

Follow the steps below to modify satellite assemblies:

1. Download archive for the version of the suite you use.
2. Modify the *.resx files.
3. Build the assemblies and sign them at DevExpress as described below.

Sign Satellite Assemblies at DevExpress

Satellite assemblies must be signed with the same strong key as DevExpress main assemblies. After you re-build the satellite assemblies, assemblies are signed with a different key (since DevExpress do not share their strong key). To resolve this issue, do the following to perform “delayed signing”:

1. Extract a public key token (use the Strong Name Tool (Sn.exe)):

   sn -e [Path to a DevExpress assembly] [Path to the output file]

2. Follow instructions in the following Microsoft topic: Delay-sign an Assembly.
3. Create a new Support Center ticket and attach your partially signed assemblies. We will sign your assemblies with our strong key.