Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

How can I create a new ILocalizationService for a new language #46

Closed
Charmatzis opened this issue Feb 24, 2016 · 5 comments
Closed

How can I create a new ILocalizationService for a new language #46

Charmatzis opened this issue Feb 24, 2016 · 5 comments
Assignees
Milestone

Comments

@Charmatzis
Copy link

Charmatzis commented Feb 24, 2016

Hi, I want to replace the events, the messages and the scopes strings inside the
Resources classes.
How can I do it?

@leastprivilege
Copy link
Member

We haven't implemented localization in 4 yet. We probably will use the asp.net core built-in capabilities - but not before rc2.

@klanglie
Copy link

klanglie commented Aug 5, 2016

I like the new localization features of .NET 462. Hopefully that will be ported to Core. Of course, it depends on .resx which means it is compiled as part of the assembly. Maybe it can be dynamically loaded too somehow? https://blogs.msdn.microsoft.com/dotnet/2016/08/02/announcing-net-framework-4-6-2/

@brockallen
Copy link
Member

some notes: I investigated the new i18n APIs in core. IStringLocalizer is mainly meant for the host to allow overriding of localizable strings. IdSvr would have to allow/inject this for its resources to allow the host to override. If the host does not, then there's a flag that shows that there's no override, so then we'd need to code for a default value. For the default value, we could then have our own set of localized resx files to provide default localized messages.

So in short, a bit of work to support this.

@brockallen
Copy link
Member

We removed it, as it was not needed in the core. The only main place that needs to localize data from the core would be on the error UI. This could then be done via the new IStringLocalizer in ASP.NET Core.

@lock
Copy link

lock bot commented Jan 15, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants