Localize Reporting Applications
- 3 minutes to read
This topic contains information about the localization specifics of each supported platform.
Tip
You can localize text strings displayed in the report, the report control’s size and location, and other report attributes. For more information, review the Localize Reports topic.
Localize DevExpress Controls with Satellite Resource Assemblies
You can localize your end-user reporting applications with the Satellite Resource Assemblies (libraries that contain translated resources).
Tip
See Localization Service to learn how to download and modify the satellite assemblies required to localize applications created with DevExpress .NET controls.
Review the following topics for information on how to use this technique to localize end-user applications:
- Localize WinForms Controls with Satellite Resource Assemblies
- Localize WPF Controls with Satellite Resource Assemblies
- Localize ASP.NET Controls with Satellite Resource Assemblies
- Localize Blazor Controls with Satellite Resource Assemblies
Localize DevExpress Controls with Localizer Objects
The following table lists the localizer objects used to localize XtraReports UI elements on different platforms:
| Platform | Localizer | Resource String Enumeration | Namespace | Additional Information |
|---|---|---|---|---|
| All Platforms | DataAccessUILocalizer | DataAccessUIStringId | DevExpress.DataAccess.UI.Localization | |
| ASP.NET (including ASP.NET MVC) | ASPxReportsLocalizer | ASPxReportsStringId | DevExpress.XtraReports.Web.Localization | |
| Print Preview for Windows Forms | PreviewLocalizer | PreviewStringId | DevExpress.XtraPrinting.Localization | Localize the Print Preview (WinForms Reporting) |
| End-User Report Designer for Windows Forms | ReportLocalizer, ReportResLocalizer | ReportStringId | DevExpress.XtraReports.Localization | Localize the End-User Report Designer (WinForms Reporting) |
| Document Preview for WPF | PrintingLocalizer | PrintingStringId | DevExpress.Xpf.Printing | Localize the Print Preview (WPF Reporting) |
| Report Designer for WPF | ReportDesignerLocalizer | ReportDesignerStringId | DevExpress.Xpf.Reports.UserDesigner.Localization | Localize the End-User Report Designer (WPF Reporting) |
Review the following topics for information on how to use this approach to localize end-user applications:
- Localize WinForms Controls with Localizer Objects
- Localize WPF Controls with Localizer Objects
- Localize ASP.NET Controls with Localizer Objects
Localize DevExpress Controls with UI Localization Client
The UI Localization Client is a cross-platform utility that allows you to quickly identify non-translated strings of DevExpress UI controls and translate them during a debug session. The utility automatically generates a RESX file(s) with translated resources and adds it to the project.
For more information refer to the following topic: UI Localization Client.
Localize DevExpress Controls for Web with String Substitution
You can substitute localization strings to change the reporting controls’ UI text strings displayed on web pages. The following topics describe how to implement this technique on different platforms:
| Platform | Topic |
|---|---|
| ASP.NET Web Forms | Localize the Web Document Viewer Localize the Web End-User Report Designer |
| ASP.NET MVC | Localize the Web Document Viewer Localize the Web End-User Report Designer |
| ASP.NET Core | Localization |
| JavaScript | Localization |
| Blazor | Localization |
Identify Non-Translated Strings
- Use our 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 strings that require translation in your application.