Repository navigation
Native localization #37
Replies: 4 comments 3 replies
|
In general every component supports localization already. In your Project you can add any Localization as you want like *resx different razor files or what you like. I use simple Yaml localization in mine. Automatically a IStringLocalizer is injected and if available it tries to localize all texts. So with this behaviour its total flexible and the whole responsibility for localization is in the project you build. In my opinion this is a clever idea :-) .. In my application I use my dotnet tool ResourceTranslator.CLI and create all all translations automatically before build. Not sure if it make sense to have localizations nativ in the component library then. |
|
Okay, thanks! |
|
hello, I have localization via .resx resource files, I cannot understand how to translate the MudExFileDisplay literals. |
|
In general because I do everything alone in my freetime its hard to have everything documented. You need to add localization in your project I do this with combining multiple localizers on my own but however in general its just registering a service that implements Then you can just use the current value for a string as Key and translate it as you want, or implement your own Localizer as you want |
Uh oh!
There was an error while loading. Please reload this page.
Do you interested in providing embedded localization for components that have text in them (file preview, file download, etc)?
If yes, can I contribute to creating Russian localization?
If yes, how can I do it?
All reactions