WPF l10n with bindings

gistfile1.cs

using System.ComponentModel;
using System.Globalization;
using System.Resources;
using System.Windows.Data;

public class TranslationSource
        : INotifyPropertyChanged
{
    private static readonly TranslationSource instance = new TranslationSource();

    public static TranslationSource Instance
    {
        get { return instance; }
    }

    private readonly ResourceManager resManager = Properties.Resources.ResourceManager;
    private CultureInfo currentCulture = null;

    public string this[string key]
    {
        get { return this.resManager.GetString(key, this.currentCulture); }
    }

    public CultureInfo CurrentCulture
    {
        get { return this.currentCulture; }
        set
        {
            if (this.currentCulture != value)
            {
                this.currentCulture = value;
                var @event = this.PropertyChanged;
                if (@event != null)
                {
                    @event.Invoke(this, new PropertyChangedEventArgs(string.Empty));
                }
            }
        }
    }

    public event PropertyChangedEventHandler PropertyChanged;
}

public class LocExtension
    : Binding
{
    public LocExtension(string name)
        : base("[" + name + "]")
    {
        this.Mode = BindingMode.OneWay;
        this.Source = TranslationSource.Instance;
    }
}

@KaiserWerk: It doesn't really matter where it is, as long as you use correct ResourceManager to get the strings (provided that it is being generated, i.e. the file has correct type in MSBuild). The common location is to put it in Resources directory.

I already got it working, google helped. Thanks a lot to you, too!

Unfortunately this method does not support binding to property,I found a better code that also supports binding
You can use the Handycontrols package to use it
github.com/ghost1372/handycontrols

Works like a charm!! Thanks man.

everything (property binding) works but it is (da vinci code = to run You must replace one element : ) ) ...
VIEW:

1. xmlns:local="clr-namespace:MyNamespace.UserInterface.Common.Localization"
2. <TextBlock Text="{local:LocK name}"/>
3. the Resource files in the code above default are placed in the PROPERTIES folder(but You can adjust the ResourceManager
   
   ):

Since I had a bit of trouble figuring out how to actually use the class, heres examples to help others:

XAML:
xmlns:local="clr-namespace:MyNamespace.LocalizationNamespace"
The namespace for xaml is whatever you set it in the class.

Usage:
"{local:Loc <PropertyName>}"

C#:
Properties.Resources.ResourceManager.GetString(nameof(Properties.Resources.<PROPERTYNAME>), Localization.TranslationSource.Instance.CurrentCulture);

And for switching to the actual culture:
C#:
Localization.TranslationSource.Instance.CurrentCulture = CultureInfo.GetCultureInfo("en-example");

@nevaran - you can check the blog post that I wrote about this. It explains how it works a little bit better (although it might not be fully explanatory).

I *just* figure it out, but thanks anyway; going to update the comment to help others

…

On Mon, Nov 23, 2020 at 11:17 AM Jakub Fijałkowski ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ @nevaran <https://github.com/nevaran> - you can check the blog post <https://www.codinginfinity.me/posts/localization-of-a-wpf-app-the-simple-approach/> that I wrote about this. It explains how it works a little bit better (although it might not be fully explanatory). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/0771bfbd26ce68456d3e#gistcomment-3537134>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG6OGGFXLLIISHBXY6BMQ3SRISEPANCNFSM4IZTM5WQ> .

@jakubfijalkowski, thanks for your code. Is there a way to allow something like this?
{ns:Loc {Binding ViewModelProperty}}

@lszczygielek If my memory is not mistaken, that is possible with some changes to the code (i.e. you need to handle the binding somewhat yourself). Unfortunately, I haven't touched it in years and won't be able to help what needs to be changed.