We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
App: WPF .Net 4.6.1
I set the language of the main window to Language = System.Windows.Markup.XmlLanguage.GetLanguage(CultureInfo.GetCultureInfo("de").IetfLanguageTag);
Language = System.Windows.Markup.XmlLanguage.GetLanguage(CultureInfo.GetCultureInfo("de").IetfLanguageTag);
In any IValueConverter i get 'de-DE' as culture, which has 'de' as parent. So translating like
internal class CultureReturningConverter : IValueConverter { private static ITranslation SomeTranslation = Translation.GetOrCreate(Properties.Resources.ResourceManager, nameof(Properties.Resources.SomeTranslation)); public object Convert(object value, Type targetType, object parameter, CultureInfo culture) { return SomeTranslation.Translate(culture); } public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture) { throw new NotImplementedException(); } }
is not possible, because the Translator doesn't know 'de-DE'.
Is it a wanted behavior or a bug? Should the Translator also check the parent culture on Translate(culture)?
Or is it simply a fault of mine?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
App: WPF .Net 4.6.1
I set the language of the main window to
Language = System.Windows.Markup.XmlLanguage.GetLanguage(CultureInfo.GetCultureInfo("de").IetfLanguageTag);
In any IValueConverter i get 'de-DE' as culture, which has 'de' as parent.
So translating like
is not possible, because the Translator doesn't know 'de-DE'.
Is it a wanted behavior or a bug?
Should the Translator also check the parent culture on Translate(culture)?
Or is it simply a fault of mine?
The text was updated successfully, but these errors were encountered: