Telerik blogs
  • Release

    Sneak Peek: Internationalization & More in Telerik Reporting R1 2018

    Sneak Peek Internationalization & More in Telerik Reporting R1 2018_270x123
    We have lots of great features coming to Telerik Reporting in our next release. Read on to get an early preview of new features, including Standalone Report Designer Internationalization.
    December 21, 2017
  • Mobile

    Controlling current culture in your XAML Windows Store apps

    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...
    September 26, 2012
  • Productivity

    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’...

    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...
    April 30, 2010
  • Desktop WPF

    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...