Skip to content

Commit 9b48770

Browse files
kb(localization): partially localized components
1 parent 2e21979 commit 9b48770

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: Paritally Localized Components
3+
description: What to do when not all texts in the Telerik components are translated based on the localization
4+
type: troubleshooting
5+
page_title: Not all texts are translated
6+
slug: common-kb-partial-localization
7+
position:
8+
tags:
9+
ticketid: 1494633
10+
res_type: kb
11+
---
12+
13+
14+
15+
## Description
16+
I am using [localization]({%slug globalization-localization%}) for my components, but some strings (texts) are not translated. For example, the column menu stays in English, or is missing its texts altogether. Or, the filter option messages are not translated. Basically, localization is enabled but the messages for Grids (or other components) are not localized.
17+
18+
## Cause\Possible Cause(s)
19+
The most common reason for such behavior is that the application uses old localization files that do not contain the necessary keys and their translations.
20+
21+
The second most common reason for the problem is that these particular keys are not present in the current translation (localization) even if they are present in the default (English) list.
22+
23+
Depending on the particular service implementation, an empty string or the English text may be returned for such keys that don't have translations.
24+
25+
## Solution
26+
Ensure that all the keys used by the Telerik components are present and translated in your application.
27+
28+
You can find an up-to-date list of those keys in the `demos` folder of your local installation (both [automated]({%slug installation/msi%}) and the [zip archive]({%slug installation/zip%})) - this is our online demos solution and the `Resources` folder in it contains a few sample localization files. We add the new keys for every release in the default translation file.
29+
30+
## Notes
31+
32+
The Telerik UI for Blazor suite grows rapidly, and we constantly add new features and components, so the localization file receives more and more keys with each release. You may want to review it for changes every time you upgrade the Telerik version or include a new component that you haven't used before.
33+
34+
The following repository contains translations provided by the community. You can use them as base and also contribute your own - both new translations, and updates to older ones that contain new keys. We welcome contributions and pull requests. Repository link: [https://github.com/telerik/blazor-ui-messages](https://github.com/telerik/blazor-ui-messages)

0 commit comments

Comments
 (0)