[HELP WANTED] Add / Fix Localization

[iammukeshm]

It would be great if someone from the community can take up this task.

Basically, all you need to do is fix / add localization resources.

Most of the texts in the Blazor components are not localization-ready. You have to add something like

@inject IStringLocalizer<NavMenu> L

to the component where NavMenu is the component name.

Now, you can use @L["Text"] for implementing localization.

For Example

Convert

<MudNavLink Href="/dashboard" Match="NavLinkMatch.All" Icon="@Icons.Material.Outlined.Dashboard">Dashboard</MudNavLink>

into

<MudNavLink Href="/dashboard" Match="NavLinkMatch.All" Icon="@Icons.Material.Outlined.Dashboard">@L["Dashboard"]</MudNavLink>

Similarly, go through each and every component of the project and do the required changes. Even if you could do this change for a single component, I would appreciate it :)

Once that's done, Navigate to the Client project to Client/Resources

Here is where you can find the RESX files arranged in a folder view.

For example,

the NavMenu.razor component resides under Client/Shared/NavMenu.razor

and the RESX file for this component resides under Client/Resources/Shared/NavMenu.{lang}.resx where {lang} is the LanguageKey.

In this RESX file, add the Name and Values, where Name is what you mentioned under @l["Dashboard"] and Value will be the localizes string.

Also note that the existing RESX files are copied over from BlazorHero. Thus, there can be chances that RESX files are in different directories altogether for certain components. So, Re-arrangement of RESX might also be necessary to properly load Localization files.

Thanks for the support! I will leave a sample commit for your reference.

[xlogex]

it need move in right resource path ...
otherwise these resource cannot loaded

[iammukeshm]

Yes, RESX re-arrangement is also needed.

[CanMehmetK]

Changing all Label="..." with Label="@l["..."]"

       Label=\"([^@].*?)\"
       Label="@L["$1"]"

May be done with check
just an idea

[kallievz]

Could the option to re-use the localization for the api module not be investigated? Don see the need to create regx on ui, and maintain on api? Single source of localization