[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
 [Expand]Product Information
 [Expand]Get Started with DevExpress Reporting
 [Expand]Create Popular Reports
 [Expand]Detailed Guide to DevExpress Reporting
 [Expand]Visual Studio Report Designer
 [Collapse]Create End-User Reporting Applications
   Cross-Platform Reporting
  [Expand]WinForms Reporting
  [Expand]WPF Reporting
  [Collapse]Web Reporting
   [Expand]General Information
   [Collapse]ASP.NET WebForms Reporting
    [Expand]Print and Export
    [Collapse]Document Viewer
     [Expand]Quick Start
      Mobile Mode
     [Expand]API and Customization
    [Expand]End-User Report Designer
     Application Deployment
   [Expand]ASP.NET MVC Reporting
   [Expand]ASP.NET Core Reporting
   [Expand]JavaScript Reporting
   [Expand]Application Security
    End-User Documentation
  [Expand]WCF Report Service
  [Expand]Discontinued Platforms
   Redistribution and Deployment
 [Expand]API Reference
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)


This document provides information on how to localize the Web Document Viewer using the built-in localization mechanisms and programmatically fine-tune the localization by substituting particular localization strings.

You can use one of the following approaches or both approaches simultaneously:

Expanded Use Satellite Resource Assemblies

You can localize the Web Document Viewer using Satellite Resource Assemblies (libraries that contain translated resources), which is a common approach to localizing .NET applications.

Refer to Localizing ASP.NET Controls via Satellite Resource Assemblies for more information.

Expanded Substitute Localization Strings

Call the ASPxClientWebDocumentViewer.UpdateLocalization method in the client-side ASPxClientWebDocumentViewer.CustomizeLocalization event to manually substitute a particular localization string with a custom one. This method receives an object containing key-value pairs that define localization for the specified strings.

Note that you can use this approach in conjunction with Satellite Resource Assemblies.


Localization strings are case sensitive. A string is only translated if you specified it in the correct case.

On a web page, specific strings look different from their actual values. For instance, the 'Search result' string is actually displayed as 'SEARCH RESULT'.

You can know the actual string value by finding the corresponding UI element in the page markup (for example, using your browser's Developer Tools).

Is this topic helpful?​​​​​​​