Skip to content

Localization

Peter Gill edited this page Jun 8, 2026 · 4 revisions

Localization

Designer language

The report designer UI supports multiple display languages. To change the language:

  1. Open the designer.
  2. Go to Tools → Options → Language.
  3. Select the desired language and click OK.
  4. Restart the designer for the change to take effect.

Currently shipped languages:

Language Status
English Default
Russian Included

Adding a translation

The designer uses resource files (.resx) for UI strings. To add a new language:

  1. Copy the existing English .resx files in the RdlDesign project.
  2. Name the copies with the appropriate culture suffix — e.g. strings.de.resx for German.
  3. Translate the string values.
  4. Submit a pull request. See Contribute for the development setup.

Report content

Report field values, parameter labels, and header/footer text are data-driven — localization of the report content itself is handled by your application and data layer, not by the reporting engine. Use Report Parameters or dataset queries to supply translated text at run time.

Number and date formatting

Format report values using .NET format strings in expressions:

=Format({Amount}, "C2")             ' uses the report's culture setting
=Format({OrderDate}, "d")           ' short date, culture-aware

The culture used for formatting follows the thread culture of the process rendering the report. Set Thread.CurrentThread.CurrentCulture before calling RunRender to control number separators, currency symbols, and date formats for a specific locale.

Clone this wiki locally