This article is currently in the process of being translated into Arabic (~22% done).

تطبيق WPF:

Application Culture / UICulture

اذا كنت قد تعاملت في بعض الأحيان مع أرقام أو تواريخ في برنامج wpf الخاص بك, مثلا بسبب واحدة من المقالات الموجودة في هذه الدورة التعليمية, قد تكون لاحظت شيئا رائعا: وهو أن الأرقام والتواريخ تعرض تلقائيا بشكل يتوافق مع الشكل المستخدم على جهازك. إذا كنت تعيش في بلد يتحدث اللغة الإنجليزية, لن تلاحظ الفرق, أما لو كنت تعيش في واحد من البلدان الكثيرة حيث تكتب الأرقام أو/و التواريخ بشكل مختلف, فهذا سيكون أمرا رائعا حقا.

و إذا خطر في ذهنك أنه لا يمكن أن يكون هناك العديد من الإختلافات عند تنسيق شيء بسيط مثل التواريخ و الأرقام، فأنا أقترح عليك أن تلقي نظرة على هذا البرنامج البسيط، أين غيرت تنسيق نفس الرقم و التاريخ لتنسجم مع المفضل في الولايات المتحدة، ألمانيا، و السويد:

إذا كما يمكنك مشاهدته هنالك اختلافات في كيفية عرض الأرقام والتواريخ . الخبر الجيد أنه .NET framework يمكن أن تساعدك كثيراً . في الحقيقة هي تفعل ذلك تلقائياً : حيث يتم تهيئة الأرقام و التواريخ طبقاً لإعدادات الكمبيوتر الذي يتم تشغيل البرنامج من خلاله. الخبر السيء أن ذلك التنسيق والتهيئة التلقائية قد يكون ليس كما تريده أن يكون. لكن لا تهتم يمكنك بسهولة تغيير هذه التنسيقات فجميعها تابعة لكلاس CultureInfo , يمكنك معرفة المزيد عن ذلك من خلال الرابط التالي C# Tutorial article on CultureInfo . حاليا دعنا نناقش كيفية تطبيق هذه التقنيات على برنامجك WPF

Ad-hoc formatting

If you only need to apply formatting for a specific piece of information, e.g. the contents of a single Label control, you can easily do this, on-the-fly, using a combination of the ToString() method and the CultureInfo class. For instance, in the example above, I applied different, culture-based formatting like this:

double largeNumber = 123456789.42;

CultureInfo usCulture = new CultureInfo("en-US");
CultureInfo deCulture = new CultureInfo("de-DE");
CultureInfo seCulture = new CultureInfo("sv-SE");

lblNumberUs.Content = largeNumber.ToString("N2", usCulture);
lblNumberDe.Content = largeNumber.ToString("N2", deCulture);
lblNumberSe.Content = largeNumber.ToString("N2", seCulture);

This might suffice for some cases, where you just need special formatting in a couple of places, but in general, you should decide if your application should use system settings (the default) or if you should override this behavior with a specific culture-setting for the entire application.

CurrentCulture & CurrentUICulture

Applying another culture to your WPF application is quite easy. You will, potentially, be dealing with two attributes, found on the CurrentThread property of the Thread class: CurrentCulture and CurrentUICulture. But what's the difference?

The CurrentCulture property is the one that controls how numbers and dates etc. are formatted. The default value comes from the operating system of the computer executing the application and can be changed independently of the language used by their operating system. It is, for instance, very common for a person living in Germany to install Windows with English as their interface language, while still preferring German-notation for numbers and dates. For a situation like this, the CurrentCulture property would default to German.

The CurrentUICulture property specifies the language that the interface should use. This is only relevant if your application supports multiple languages, e.g. through the use of language-resource files. Once again, this allows you to use one culture for the language (e.g. English), while using another (e.g. German) when dealing with input/output of numbers, dates etc.

Changing the application Culture

With that in mind, you now have to decide whether to change the CurrentCulture and/or the CurrentUICulture. It can be done pretty much whenever you want, but it makes the most sense to do it when starting your application - otherwise, some output might already be generated with the default culture, before the switch. Here's an example where we change the Culture, as well as the UICulture, in the Application_Startup() event which can be used in the App.xaml.cs file of your WPF application:

private void Application_Startup(object sender, StartupEventArgs e)
    Thread.CurrentThread.CurrentCulture = new CultureInfo("de-DE");
    Thread.CurrentThread.CurrentUICulture = new CultureInfo("en-US");

Since we use the Thread class as well as the CultureInfo, don't forget to add the required namespaces to your file, if they are not already present:

using System.Threading;
using System.Globalization;

With this in place, numbers and dates will now be formatted according to how they prefer it in German (de-DE). As mentioned, you can leave out the line defining the culture for the UICulture (the last line) if your application doesn't support multiple languages.

Changing the culture during the Application_Startup event, or at the latest in the constructor of your main window, makes most sense, because values that are already generated aren't updated automatically when you change the CurrentCulture property. That doesn't mean that you can't do it though, as illustrated by this next example, which also serves as a fine demonstration of how the output is affected by the CurrentCulture property:

<Window x:Class="WpfTutorialSamples.WPF_Application.ApplicationCultureSwitchSample"
Title="ApplicationCultureSwitchSample" Height="200" Width="320">
    <StackPanel Margin="20">
<RowDefinition Height="Auto" />
<RowDefinition Height="Auto" />
<ColumnDefinition Width="*" />
<ColumnDefinition Width="*" />
    <Label Name="lblNumber" Grid.Column="1" />
    <Label Grid.Row="1">Date:</Label>
    <Label Name="lblDate" Grid.Row="1" Grid.Column="1" />
<StackPanel Orientation="Horizontal" HorizontalAlignment="Center" Margin="0,20">
    <Button Tag="en-US" Click="CultureInfoSwitchButton_Click" HorizontalContentAlignment="Stretch">English (US)</Button>
    <Button Tag="de-DE" Click="CultureInfoSwitchButton_Click" HorizontalContentAlignment="Stretch" Margin="10,0">German (DE)</Button>
    <Button Tag="sv-SE" Click="CultureInfoSwitchButton_Click" HorizontalContentAlignment="Stretch">Swedish (SE)</Button>
using System;  
using System.Globalization;  
using System.Threading;  
using System.Windows;  
using System.Windows.Controls;  

namespace WpfTutorialSamples.WPF_Application  
    public partial class ApplicationCultureSwitchSample : Window  
public ApplicationCultureSwitchSample()  

private void CultureInfoSwitchButton_Click(object sender, RoutedEventArgs e)  
    Thread.CurrentThread.CurrentCulture = new CultureInfo((sender as Button).Tag.ToString());      
    lblNumber.Content = (123456789.42d).ToString("N2");  
    lblDate.Content = DateTime.Now.ToString();  

The interesting part is found in the CultureInfoSwitchButton_Click event, where we set CurrentCulture based on which of the buttons were clicked, and then update the two labels containing a number and a date:

Culture & Threads: The DefaultThreadCurrentCulture property

If your application uses more than one thread, you should consider using the DefaultThreadCurrentCulture property. It can be found on the CultureInfo class (introduced in .NET framework version 4.5) and will ensure that not only the current thread, but also future threads will use the same culture. You can use it like this, e.g. in the Application_Startup event:

CultureInfo.DefaultThreadCurrentCulture = new CultureInfo("de-DE");

So, will you have to set both the CurrentCulture AND the DefaultThreadCurrentCulture properties? Actually, no - if you have not already changed the CurrentCulture property, setting the DefaultThreadCurrentCulture property will also be applied to the CurrentCulture property. In other words, it makes sense to use the DefaultThreadCurrentCulture instead of CurrentCulture if you plan on using multiple threads in your application - it will take care of all scenarios.


Dealing with the culture of your WPF application is very important, but fortunately for you, WPF will do a lot of it for you completely out-of-the-box. If you need to change the default behavior, it's quite easy as well, using the CurrentCulture and CurrentUICulture properties, as illustrated in the numerous examples of this article.

This article has been fully translated into the following languages: Is your preferred language not on the list? Click here to help us translate this article into your language!