Welcome to our official discussion site. You’ll find topics on features, bugs, development, and general support here
https://www.noesisengine.com/forums/
Our LocExtension relies on ResourceDictionaries to get the values of the specified keys. There is no way to support other formats in our extension, but you can implement your own MarkupExtension if you need a different approach.The localization tutorial seems straightforward, but I was wondering if there's a way to have it accept other formats like xliff or json.
It can be achieved by merging the default language in the specific language dictionary. For example, if you have a Language-en.xaml (the default language), then you can have a Language-fr.xaml that merges it:Also does the system work with a fallback language. Like if the key just isn't in the dictionary will it fall back to the default language?
<ResourceDictionary
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
<ResourceDictionary.MergedDictionaries>
<ResourceDictionary Source="Language-en.xaml"/> <!-- Default language is merged -->
</ResourceDictionary.MergedDictionaries>
<!-- Entries for the FR language -->
</ResourceDictionary>Yes, our LocExtension can point to any resource defined in the Source dictionary, even a FontFamily resource:Also is there a way to switch fonts as well.
<ResourceDictionary
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
<FontFamily x:Key="TheFont">Fonts/#Arial</FontFamily>
</ResourceDictionary><TextBlock Text="Title" FontFamily="{noesis:Loc TheFont}"/><TextBlock>
<TextBlock.Style>
<Style TargetType="TextBlock">
<Setter Property="Text" Value="{noesis:Loc ItemCountPlural}"/>
<Style.Triggers>
<DataTrigger Binding="{Binding Items.Count}" Value="1">
<Setter Property="Text" Value="{noesis:Loc ItemCountSingular}"/>
</DataTrigger>
</Style.Triggers>
</Style>
</TextBlock.Style>
</TextBlock>
"You have {NumCats} {NumCats}|plural(one=cat,other=cats)"
We decided not to support that scenario, as the ViewModel could return the localized string directly in the bound property. So instead of using the Loc extension, you would do a normal binding:I'd like to do something like:
<Label Content={noesis:Loc {Binding TitleKey}} />
But it doesn't seem to work, is there a way to make this work?
<Label Content="{Binding TitleKey"/>public string Title => Localization.Resources[_titleKey];public class LanguageConverter : IMultiValueConverter
{
public object Convert(object[] values, Type targetType, object parameter, CultureInfo culture)
{
if (values[0] is ResourceDictionary resourceDictionary && values[1] != null)
{
var key = values[1];
if (resourceDictionary.Contains(key))
{
return resourceDictionary[key];
}
}
return DependencyProperty.UnsetValue;
}
public object[] ConvertBack(object value, Type[] targetTypes, object parameter, CultureInfo culture)
{
throw new NotImplementedException();
}
}
<Label Foreground="White" FontSize="40" >
<Label.Content>
<MultiBinding Converter="{StaticResource LanguageConverter}">
<Binding Path="SelectedLanguage.ResourceDictionary" />
<Binding Path="SelectedLanguageId" />
</MultiBinding>
</Label.Content>
</Label>