Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Localization #58

Open
No1e opened this issue Jun 3, 2021 · 1 comment
Open

Localization #58

No1e opened this issue Jun 3, 2021 · 1 comment
Labels
needs clarification More context needed to understand the problem.

Comments

@No1e
Copy link

No1e commented Jun 3, 2021

Dear Hardcodet Team,

First I want to say thanks for you amazing work, you really did great job, especially supporting .net core.

I have small project targeting .Net 5, where I took advantage of Microsoft.Extensions.Localization to implement localization.
On the one hand, in some places I use IStringLocalizer directly from the code. On the other hand, I have implemented markup extension, that also relies on IStringLocalizer, and I am using that markup extension in XAML, also for WPF Notify Icon.

The problem is that, when I change the language in the app, WPF Notify Icon stays on the previous language configuration.
Is there some method that will be called before context many of WPF Notify Icon appears, that I can override where I can set the CurrentUICulture on that thread according to configuration, so that the context menu (through above mentioned markup extension) can be localized without restarting the whole app?

Thank you and best regards,
Nole

@Lakritzator
Copy link
Collaborator

Is it possible that you supply a small example project? I'm actually not acquainted to Microsoft.Extensions.Localization, so I do not really understand the issue. This seems to be related to #63

@Lakritzator Lakritzator added the needs clarification More context needed to understand the problem. label Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs clarification More context needed to understand the problem.
Projects
None yet
Development

No branches or pull requests

2 participants