Repository navigation
Localization
The report designer UI supports multiple display languages. To change the language:
- Open the designer.
- Go to Tools → Options → Language.
- Select the desired language and click OK.
- Restart the designer for the change to take effect.
Currently shipped languages:
| Language | Status |
|---|---|
| English | Default |
| Russian | Included |
The designer uses resource files (.resx) for UI strings. To add a new language:
- Copy the existing English
.resxfiles in theRdlDesignproject. - Name the copies with the appropriate culture suffix — e.g.
strings.de.resxfor German. - Translate the string values.
- Submit a pull request. See Contribute for the development setup.
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.
Format report values using .NET format strings in expressions:
=Format({Amount}, "C2") ' uses the report's culture setting
=Format({OrderDate}, "d") ' short date, culture-awareThe 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.
If the RDL defines a <Language> element (a BCP 47 tag, e.g. en-US, fr-FR, pt-BR), that value takes precedence over the client/thread culture for formatting expressions in that report — it is no longer silently ignored. Omit <Language> from the RDL if you want the report to always follow the rendering process's thread culture instead.