Skip to main content
All docs
V24.2

DevExpress UI Localization Service

  • 4 minutes to read

This topic describes how to use the DevExpress Localization Service to obtain and edit translated resources (strings) for 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.

Localization add translation

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 in 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.

Localization2

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 states.

  • 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.

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

    Localization3

Download Your Translations

Once you make changes to translations, click the Download button. Note that this button does not start the download immediately.

The Localization Service first builds required resources and then sends an email to the address associated with your DevExpress.com account. Open the email and click the link that will direct you to a signed self-extracting archive:

Localization Service - Translation Download Link in 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  

The archive contains a folder with localization resources you requested (satellite assemblies and JSON files).

Platform-Specific Information

Localize DevExpress Controls of Versions Prior to v12.1

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

Modify Satellite Assemblies in Versions Prior to v12.1

Follow the steps below to modify satellite assemblies:

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

Sign Satellite Assemblies as 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.