@@ -237,7 +237,7 @@ The Syncfusion
® Blazor UI component support
}
```
-## Using HTML attributes and DOM events in the root element
+## Use HTML attributes and DOM events on the root element
The HTML attributes and DOM events can be applied directly to the component's root element.
diff --git a/blazor/common/input-validation.md b/blazor/common/input-validation.md
index df80cec15d..3c91e6e5a9 100644
--- a/blazor/common/input-validation.md
+++ b/blazor/common/input-validation.md
@@ -1,9 +1,9 @@
---
layout: post
-title: Input Form Validation in Blazor - Syncfusion
-description: Check out the documentation for Input Form Validation using data annotation attributes with supported Blazor component list.
+title: Input form validation in Blazor - Syncfusion
+description: Learn how to validate Syncfusion Blazor input components using data annotations with EditForm, DataAnnotationsValidator, ValidationMessage, ValidationSummary.
platform: Blazor
-component: Common
+control: Common
documentation: ug
---
@@ -13,7 +13,7 @@ The Syncfusion
® Blazor UI input and editor
## How to validate Syncfusion
® Blazor UI components
-1. Create a model class and set [DataAnnotation attributes](https://learn.microsoft.com/en-us/aspnet/core/mvc/models/validation?view=aspnetcore-8.0) to its properties.
+1. Create a model class and apply [data annotation attributes](https://learn.microsoft.com/en-us/aspnet/core/mvc/models/validation?view=aspnetcore-8.0) to its properties.
```cshtml
@using System.ComponentModel.DataAnnotations;
@@ -35,7 +35,7 @@ The Syncfusion
® Blazor UI input and editor
}
```
-2. Add the `EditForm` component in the view page and assign the model object to its `Model` property. Also, declare the `DataAnnotationsValidator` and `ValidationSummary` components inside the `EditForm` component.
+2. Add the `EditForm` component to the page and assign the model object to its `Model` property. Include the `DataAnnotationsValidator` and `ValidationSummary` components inside `EditForm`.
```cshtml
@@ -44,10 +44,10 @@ The Syncfusion® Blazor UI input and editor
```
- N> [DataAnnotationsValidator](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.dataannotationsvalidator?view=aspnetcore-8.0) - Attaches validation support to an `EditContext` using data annotations.
-
[ValidationSummary](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.validationsummary?view=aspnetcore-8.0) - Used to display a summarized list of all validation messages.
+N> [DataAnnotationsValidator](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.dataannotationsvalidator?view=aspnetcore-8.0): Attaches validation support to the `EditContext` using data annotations.
+
[ValidationSummary](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.validationsummary?view=aspnetcore-8.0): Displays a summarized list of all validation messages.
-3. Add any desired [Syncfusion
® components](#blazor-form-validation-supported-components) inside the `EditForm` and provide the values through `@bind-` property.
+3. Add any desired [Syncfusion
® components](#blazor-form-validation-supported-components) inside the `EditForm` and provide values via the appropriate `@bind-` parameter.
```cshtml
@@ -65,9 +65,9 @@ The Syncfusion® Blazor UI input and editor
```
- N> Refer to [this table](#blazor-form-validation-supported-components) for the Syncfusion
® Blazor components which supports the form validation and its `@bind` property details.
+N> Refer to [this table](#blazor-form-validation-supported-components) for Blazor components that support form validation and their corresponding `@bind` parameter details.
-4. The `EditForm` validates the input values based on its edit context and displays the validation message on the `ValidationSummary` component when submitting the form.
+4. The `EditForm` validates input values based on its `EditContext` and displays validation messages in the `ValidationSummary` component when the form is submitted.
**Validation Failure:**
@@ -100,7 +100,7 @@ The Syncfusion
® Blazor UI input and editor
-6. The `EditForm`'s submit events [OnValidSubmit](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.editform.onvalidsubmit?view=aspnetcore-8.0) and [OnInvalidSubmit](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.editform.oninvalidsubmit?view=aspnetcore-8.0) can be used to get the validation success and failure `EditContext` details.
+6. The `EditForm` submit events [OnValidSubmit](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.editform.onvalidsubmit?view=aspnetcore-8.0) and [OnInvalidSubmit](https://learn.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.editform.oninvalidsubmit?view=aspnetcore-8.0) provide the `EditContext` on validation success or failure.
```cshtml
@@ -145,11 +145,11 @@ The Syncfusion® Blazor UI input and editor
}
```
- W> You shouldn't use the `OnSubmit` handler along with `OnValidSubmit` and `OnInvalidSubmit` event handlers in the `EditForm` component. It will throw a runtime error.
+W> Do not use the `OnSubmit` handler together with `OnValidSubmit` and `OnInvalidSubmit` in the same `EditForm`. This causes a runtime error.
## Blazor form validation supported components
-The following section provides the details about the Syncfusion® Blazor UI components that are supported with form validation, corresponding `@bind` properties, and validation examples.
+The following section lists the Syncfusion® Blazor UI components that support form validation, the corresponding `@bind` parameters, and validation examples.
@@ -283,11 +283,11 @@ The following section provides the details about the Syncfusion Razor Component`. Specify the component name and create it.
-2. Add Syncfusion® Blazor component in the new component and assign the `Value`, `ValueChanged`, and `ValueExpression` properties. Refer [here](https://learn.microsoft.com/en-us/aspnet/core/blazor/components/data-binding?view=aspnetcore-8.0#binding-with-component-parameters), to know more about data binding in component parameters.
+2. Add a Syncfusion® Blazor component in the new component and assign the `Value`, `ValueChanged`, and `ValueExpression` parameters. Refer to the [data binding with component parameters](https://learn.microsoft.com/en-us/aspnet/core/blazor/components/data-binding?view=aspnetcore-8.0#binding-with-component-parameters) documentation for details.
```cshtml
@using System.Linq.Expressions;
diff --git a/blazor/common/localization.md b/blazor/common/localization.md
index 167f0661aa..e0af46a0ab 100644
--- a/blazor/common/localization.md
+++ b/blazor/common/localization.md
@@ -1,43 +1,43 @@
---
layout: post
title: Localization (Multi-Language) in Blazor components | Syncfusion
-description: Localization of Syncfusion Blazor UI components in Blazor Server and WebAssembly (WASM) apps and much more.
+description: Learn how to localize Syncfusion Blazor UI components in Blazor Web App, WASM, Server, and .NET MAUI apps using resource files and dynamic culture switching.
platform: Blazor
-component: Common
+control: Common
documentation: ug
---
# Localization of Blazor Components
-[Localization](https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization?view=aspnetcore-8.0) is the process of translating the application resources into different languages for specific cultures. You can localize the Syncfusion® Blazor components by adding a resource file for each language.
+[Localization](https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization?view=aspnetcore-8.0) is the process of translating application resources into different languages for specific cultures. Syncfusion® Blazor components can be localized by adding a resource file for each language.
## Localization of Syncfusion® Blazor Components
-The following two steps can be used to localize Syncfusion® Blazor components based on culture. You can find the example codes in the below repository,
+Use the following steps to localize Syncfusion® Blazor components based on culture. Example code is available in the repository below.
-N> [View Sample in GitHub](https://github.com/SyncfusionExamples/blazor-localization)
+N> [View sample on GitHub](https://github.com/SyncfusionExamples/blazor-localization)
-### Adding culture based resx files
+### Adding culture-based .resx files
-Syncfusion® components can be localized using the Resource `.resx` files. You can find the default and culture based localization files in the following GitHub repository.
+Syncfusion® components can be localized using Resource `.resx` files. Default and culture-specific localization files are available in the following GitHub repository.
-N> You can get default and culture based resource files from [GitHub](https://github.com/syncfusion/blazor-locale).
+N> Download default and culture-based resource files from [GitHub](https://github.com/syncfusion/blazor-locale).
-Copy the default resx file (`SfResources.resx`) and the other required resx files based on the culture to be localized and add them to the **Resources** folder. If you are implementing in a .NET MAUI Blazor app, create a **LocalizationResources** folder and add them into it.
+Copy the default `.resx` file (`SfResources.resx`) and any required culture-specific `.resx` files to the **Resources** folder. For a .NET MAUI Blazor app, create a **LocalizationResources** folder and add them there.
-N> Update the localization files whenever you upgrade the Syncfusion® NuGet packages in the application to avoid the issues occur due to localization strings.
+N> Update the localization files whenever upgrading Syncfusion® NuGet packages to prevent mismatches in localization strings.
-After adding the resource file in the application, double click default resx (`SfResources.resx`) file and open **Resource Editor**. In the Resource Editor, change **Access Modifier** option as **Public** .
+After adding the resource files, open the default resource file (`SfResources.resx`) in the **Resource Editor** and set **Access Modifier** to **Public**.
### Create and register localization service
-[ISyncfusionStringLocalizer](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html) which acts as a middleware to connect the Syncfusion® Blazor UI components and resource files, uses [ResourceManager](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html#Syncfusion_Blazor_ISyncfusionStringLocalizer_ResourceManager) to provide culture specific resources at runtime. Create a class implementing `ISyncfusionStringLocalizer`. In the newly created class, return the `ResourceManager` created in the above step for [ResourceManager](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html#Syncfusion_Blazor_ISyncfusionStringLocalizer_ResourceManager) property and change [GetText](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html#Syncfusion_Blazor_ISyncfusionStringLocalizer_GetText_System_String_) method to return localized string using resource manager.
+[ISyncfusionStringLocalizer](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html) acts as middleware between Syncfusion® Blazor UI components and resource files and uses the [ResourceManager](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html#Syncfusion_Blazor_ISyncfusionStringLocalizer_ResourceManager) to provide culture-specific resources at runtime. Create a class that implements `ISyncfusionStringLocalizer`. In the class, return the `ResourceManager` created in the previous step for the [ResourceManager](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html#Syncfusion_Blazor_ISyncfusionStringLocalizer_ResourceManager) property and update [GetText](https://help.syncfusion.com/cr/blazor/Syncfusion.Blazor.ISyncfusionStringLocalizer.html#Syncfusion_Blazor_ISyncfusionStringLocalizer_GetText_System_String_) to return the localized string.
-In the following code, `SyncfusionLocalizer` class implements `ISyncfusionStringLocalizer` interface and `ResourceManager` configured to return the cached ResourceManager instance of default resource file created in **Adding culture based resx files** step.
+In the following code, the `SyncfusionLocalizer` class implements the `ISyncfusionStringLocalizer` interface, and the `ResourceManager` is configured to return the cached `ResourceManager` instance of the default resource file created in the “Adding culture-based .resx files” step.
{% tabs %}
@@ -70,11 +70,10 @@ public class SyncfusionLocalizer : ISyncfusionStringLocalizer
{% endtabs %}
-Register the `ISyncfusionStringLocalizer` and `Syncfusion® Blazor Service` in the **~/Program.cs** file of your app.
+Register `ISyncfusionStringLocalizer` and the Syncfusion® Blazor service in the **~/Program.cs** file of your app.
-* If you create a Blazor Web App with an **Interactive render mode** such as `WebAssembly or Auto`, you need to ensure the registration of the `SyncfusionLocalizer` and Syncfusion® Blazor services in both **~/Program.cs** files.
-
-* For **MAUI Blazor App**, register the Syncfusion® Blazor Service in the **~/MauiProgram.cs** file.
+* For a Blazor Web App using an **Interactive render mode** (WebAssembly or Auto), register `SyncfusionLocalizer` and the Syncfusion® Blazor services in both **Server** and **Client** `~/Program.cs` files.
+* For a **.NET MAUI Blazor** app, register the Syncfusion® Blazor service in **~/MauiProgram.cs**.
{% tabs %}
@@ -93,19 +92,18 @@ builder.Services.AddSingleton(typeof(ISyncfusionStringLocalizer), typeof(Syncfus
## Statically set the culture
-If you don't want to change culture dynamically, you can set it statically by following the procedures below.
+If culture changes are not required at runtime, set the culture statically using the options below.
### Blazor Web App and Blazor WASM App
-In Blazor Web App and Blazor WASM app, you can set culture statically in Blazor's start option or in C# code.
-
-#### Setting the culture Blazor's start option
+In Blazor Web App and Blazor WebAssembly (WASM) apps, set culture either in Blazor’s start options or in C# code.
-The app's culture can be set in JavaScript by setting `applicationCulture` in Blazor's start option by following the steps below,
+#### Setting the culture in Blazor’s start option
-* For **.NET 8 and .NET 9** Blazor Web Apps using any render mode (Server, WebAssembly, or Auto), prevent Blazor autostart by adding `autostart="false"` attribute to the Blazor `