You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: globalization/localization.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,10 @@ Using your own names is possible and will affect:
40
40
41
41
[Enable Blazor localization and set the application's culture](https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization), depending on the business requirements and the hosting model or render mode.
42
42
43
+
The purpose of this step is to supply the correct application culture to the `ResourceManager.GetString()` method in your [Telerik localization service](#step-3-implement-itelerikstringlocalizer-service). This is turn will obtain the localized string from the correct resource file with a matching locale in its file name.
44
+
45
+
>tip This step is optional if your Blazor application will always use the same culture and a single Telerik resource file without a locale in its name.
46
+
43
47
### Step 2: Add Resouce Files
44
48
45
49
Create and add localization resource `resx` files to your app, based on the languages that the app must support. Use the following links for reference:
0 commit comments