Wednesday, February 17, 2010

Localization Made Easy In WPF


In this blog I will talk about localization in WPF applications. XAML is a great tool for declaratively create application interfaces and we shall use this declarative power to leverage globalization / localization capabilities of .NET. While designing this feature following considerations were paramount:

  1. Localizing applications must be declaratively done in XAML with no code behind
  2. XAML code must be easy to read and maintain
  3. Runtime culture change support must be in place so applications need not reboot for culture change to take place (note: this may or may not be a feature you would want)
  4. Solution must be efficient both in terms of memory and CPU time since operations are performed on UI thread
  5. Design time experience must not be altered, so developers can develop UI based on default language without worrying about how it is localized at runtime


I took inspiration / ideas from the following posts:

Code for the article

You can download the code for the article here

Step 1 – Create Localized Resource Files

First step is to create resource files that hold localized resources. I created a WPF application and under Property folder I open Resources.resx and enter a string with key “Hello” and value “Hello”. This is my English resource file. Also what is most important is to pick Access Modifier as Public for this resource file or else XAML will not be able to access it.

I also created another resource file called and added it to the Property folder. In this resource file I added a string with key “Hello” and value “Здравствуйте” which obviously means hello in Russian. So depending on the culture, application should pick the right string. Also notice that in this resource file, Access Modifier is set to No code generation.

Step 2 – Create a simple Window

Next we create a simple window with two radio buttons to give the user ability to switch cultures between English and Russian and a text block that would display hello string from the correct resource dictionary.

To localize a control we need to set an attached property on the control called Localization. This property is of type LocalizationInfo that has two properties to support localization:

  1. Property – This is the actual DependencyProperty that should display localized value on the UI. In our example we use TextBlock.TextProperty for this purpose.
  2. ResourceKey – This is the resource key within the resource file. In our case this is “Hello”.

Here is the XAML definition of the window:

<Window x:Class="Localization.Window1"
Title="Window1" Height="300" Width="300">
<StackPanel ButtonBase.Click="OnLanguageChanged">
<RadioButton x:Name="EnglishButton" Content="English" IsChecked="True"/>
<RadioButton Content="Russian"/>
<TextBlock Text="{x:Static resources:Resources.Hello}">
Property="{x:Static TextBlock.TextProperty}"


Note in bold the LocalizationInfo property and also design time text support via static Resources.Hello field. Also the radio buttons are hooked via attached handler to OnLanguageChanged method:

private void OnLanguageChanged(object sender, RoutedEventArgs e)
Thread.CurrentThread.CurrentUICulture =
new CultureInfo((bool)EnglishButton.IsChecked ? "en-US" : "ru-RU");

How does it all work?

The magic of keeping track of localizable UI elements and updating their content is done within LocalizationManager class. UpdateResources is the interesting method:

/// <summary>
/// Updates the resources after a culture change has occurred
/// </summary>
public static void UpdateResources()
List<WeakReference> deadReferences = new List<WeakReference>();

foreach (WeakReference reference in Elements)
FrameworkElement element = reference.Target as FrameworkElement;

if (element != null)
LocalizationInfo localizationInfo = GetLocalization(element);
if (localizationInfo != null)

foreach (WeakReference reference in deadReferences)

It basically iterates over HashSet of localizable FrameworkElements and updates the content for DependencyProperty from localized resources. Note that we maintain a HashSet of weak references so UI elements can still be garbage collected without us holding references. As a cleanup phase we detect the dead references and remove them from the HashSet. That’s it now you know how to localize your WPF applications with minimal code !

1 comment:

Greg David said...

Hi! To easily localize your applications, I suggest to try which is a translation management platform designed to simplify the workflow for translators and project managers.