• Mobile

    Controlling current culture in your XAML Windows Store apps

    September 26, 2012 Share
    When building an application for Windows 8 we find the same known feature for Globalization through the CultureInfo.CurrentCulture and CultureInfo.CurrentUICulture properties, used in many cases where it comes to using culture-specific strings, formatting dates, numbers, etc. And while developing, you might be surprised that, in the common scenario, the current culture does not derive from the OS culture for the current machine. Then, how the current culture is resolved? It turns out that there is a way to get the correct OS UI culture. To understand the process I will start from a blank app and modify it for our needs. Package.appxmanifest default language When...
  • Testing & ALM

    Localization of the TeamPulse Ideas & Feedback Portal

    With the 2012 R2 Release, localization of the Ideas and Feedback Portal is as easy as editing a text file!  Background Localization is the process of changing the text in an application to another language, or locale.  Well designed applications allow for changing the text that is displayed without having to branch the source code and recompile, and TeamPulse certainly falls into this category.  Built on Microsoft’s .NET Platform, TeamPulse takes full advantage of the localization features provided by the .NET Framework, allowing you to customize the Ideas and Feedback portal to the language that best meets your needs. Based on our customers’...
  • .NET Mobile

    Localizing the RadEditor

    In my last post I went over how to create your own custom dictionary for RadSpell and since this control is fully integrated into our RadEditor control I wanted to discuss how to use your custom dictionary with the RadEditor, as well as how to localize the RadEditor itself. To start off we want to make sure that we can take use of our custom dictionary in the RadEditor. To do this we need to make sure that the “RadSpell” folder is located in the “App_Data” folder of our project. In the RadSpell folder we have to add all of our custom...
  • .NET

    Enhancing the Localization Support of RadControls for Silverlight and WPF

    With the Q1 2009 SP2 release of RadControls for Silverlight we introduced an enhancement of the LocalizationManager class. Two new properties were added to enrich the localization support in the suite - DefaultCulture and DefaultResourceManager. With the new properties you no longer have to always create an instance of the LocalizationManager. Here is a brief description of the two properties: DefaultCulture A static property of type System.Globalization.CultureInfo. Use this one to change localized values without changing the UI culture of the current thread. DefaultResourceManager A static property of type System.Resources.ResourceManager. Use this one to change localized values using a new resource manager, i.e. a new resource file. Example: The attached...
  • .NET

    Localization for RadControls for Silverlight and WPF

    As we are continuously working on the localization of all our controls, we'd like to share how the localization is actually progressing at our side. With the RadControls for Silverlight Q1 2009 SP1 we introduced the LocalizationManager. Actually we have used it to localize the RadUpload control for Silverlight. Now we have four more controls localized right from the box: RadTreeView, RadMediaPlayer, RadColorSelector and RadColorPicker. In the attached example you can see them localized. Another control to be localized soon is the RadGridView control. The LocalizationManager allows you to easily localize any of our controls. In addition, we followed the practice to share the same code across Silverlight...