Skip to main content
All docs
V23.2

DevExpress Products: UI Localization Overview

  • 3 minutes to read

Localization allows you to translate DevExpress UI controls and components into different languages. From straightforward localization with pre-built satellite resource assemblies to manual translation of the UI, DevExpress Subscriptions include everything you need to quickly develop multicultural enterprise applications and websites.

DevExpress UI Localization

Satellite Resource Assemblies

DevExpress controls can be localized using satellite resource assemblies. DevExpress delivers satellite assemblies for a large variety of languages and cultures.

Install Pre-Built Localized Resources (DE, JA, ES)

DevExpress Unified Component Installer includes an option to install community-sourced localized resources for certain languages: German (DE), Japanese (JA), and Spanish (ES).

With v22.2+, these resources are not installed by default. The Unified Component Installer does not add “de”, “ja”, and “es” community-sourced localized assemblies to the Global Assembly Cache (GAC). You can install them at your discretion:

  1. Run the Unified Component Installer in “Modify” mode.
  2. Enable the Community-Sourced Localization (for de, es, ja) option.

    DevExpress Unified Installer - Community Sourced Localization

  3. Click Next.
  4. Click Accept & Continue.

You can find localized resources in the following folders:

  • C:\Program Files\DevExpress 23.2\Components\Bin\Framework (for a 64-bit Windows OS)

    C:\Program Files (x86)\DevExpress 23.2\Components\Bin\Framework (for a 32-bit Windows OS)

  • C:\Program Files\DevExpress 23.2\Components\Bin\NetCore (for a 64-bit Windows OS)

    C:\Program Files (x86)\DevExpress 23.2\Components\Bin\NetCore (for a 32-bit Windows OS)

Store Localized Resources in a Version Control System

To store localized satellite assemblies in the version control system, do the following:

  1. Include localized satellite assemblies into your executable project within corresponding language-specific folders (for example, “de”).
  2. In the Solution Explorer, set file properties as follows:
    • Build Action = Content
    • Copy To Output Directory = Copy always

Store Localized Resources in a Version Control System

Platform-Specific Localization

Read the following topics for platform-specific information:

Tip

Use DevExpress Online Localization Service to modify our shipping resources or create satellite assemblies for a different language.

Localization of Single-File Applications

If you publish your project (for example, WinForms) as a single-file application (see Single-file deployment), you need to use the solution described in the Store Localized Resources in a Version Control System section to localize your application. Otherwise, your single-file application will not be able to resolve satellite assemblies (even if you put them in correct subdirectories after you publish the application).

DevExpress controls use Localizer objects to obtain strings for UI elements. Localization-related APIs (Localizer objects) take priority over satellite resource assemblies.

You can create custom localizer objects for specific UI controls or use the global XtraLocalizer class to localize all DevExpress UI controls in your application.

Read the following topics for platform-specific information:

Identification of Non-Translated Resources

  • Use our cross-platform DevExpress UI Localization Client tool shipped as part of your DevExpress subscription. This tool streamlines the entire localization process. You can quickly find non-translated strings and translate them during a debug session.
  • Handle the XtraLocalizer.QueryLocalizedStringNonTranslated event to collect non-localized resource strings for further translation. The event allows you to focus on the strings that require translation in your application.

See Also