# Multi-Language Support for RadChart

> caution **RadChart** has been deprecated since Q3 2014 and is marked as obsolete as of the 2026 Q2 SP1 (v2026.2.708) release. This is the last release that includes the RadChart component — its source code will be removed from the assembly in the next release. We strongly recommend using [RadHtmlChart](https://www.telerik.com/products/aspnet-ajax/html-chart.aspx), Telerik's modern client-side charting component.
> To transition from RadChart to RadHtmlChart, refer to the following migration articles:
>
> * [Migrating Series](https://www.telerik.com/products/aspnet-ajax/documentation/controls/htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-series-configuration)
> * [Migrating Axes](https://www.telerik.com/products/aspnet-ajax/documentation/controls/htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-axes-configuration)
> * [Migrating Date Axes](https://www.telerik.com/products/aspnet-ajax/documentation/controls/htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-date-axis-configuration)
> * [Migrating Databinding](https://www.telerik.com/products/aspnet-ajax/documentation/controls/htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-data-binding-configuration)
> * [Features parity](https://www.telerik.com/products/aspnet-ajax/documentation/controls/htmlchart/changes-and-backwards-compatibility/migrating-from-radchart-to-radhtmlchart/migrate-functionalities---features-and-series-types-parity)
>
> Explore the [RadHtmlChart documentation](https://www.telerik.com/products/aspnet-ajax/documentation/controls/htmlchart/overview) and online demos to determine how it fits your development needs.

RadChart bridges off the rich localization feature set already built into ASP.NET 2.0. See the following resources for background information and tools for ASP.NET 2.0 localization:

* [ASP.NET QuickStart Tutorials](http://quickstarts.asp.net/QuickStartv20/aspnet/doc/localization/localization.aspx)

* [Google Language Tools](http://www.google.com/language_tools?hl=en) for translating (used in prototyping, not production).

See the following localization tutorials:

* [Local, Implicit localization example.](https://www.telerik.com/products/aspnet-ajax/documentation/controls/chart/advanced-topics/localization-example-using-local-resources--implicit-expression)

* [Global, Explicit localization example.](https://www.telerik.com/products/aspnet-ajax/documentation/controls/chart/advanced-topics/localization-example-using-global-resources--explicit-expression)

The resources used for localization can be **local** or **global**:

**Local** resources are used for the controls on a specific page. This method assumes the existence of a resource file located in the ASP.NET Folder **App_LocalResources** with the same name as the page you're translating. So, if you're localizing default.aspx, ASP.NET expects to see default.aspx.resx (the default language), and translated versions e.g. default.aspx.fr-FR.resx for a French translation.

Resources can also be **global**, i.e. shared anywhere in the application. This method uses a resource file located in the ASP.NET folder **App_GlobalResource**.

There are two syntaxes used in specifying items on the page that need translation, **Explicit** and **Implicit:**

* **Explicit** uses expression binding syntax like that used for binding data in-line to the ASP.NET HTML page. This type of expression can be used to identify both local and global resources. In the example below the chart title Text property is being explicitly set to a resource item named "Title" in the resource file \App_GlobalResource\MyGlobals.resx.

```ASP.NET
<charttitle>
   <TextBlock Text="<$ Resources>"></TextBlock>
</charttitle>
```

* **Implicit** assumes the existence of a resource file located in the ASP.NET Folder App_LocalResources with the same name as the page you're translating. Notice in the example below the meta:resourcekey attribute. The resource key in the HTML ties back to the name of the resource item in the resource file. Using the resource key and the property value in the resource file you can define any number of properties.In the example below the chart title text name in the resource file is formatted as <resourcekey><property name>, i.e. "RadChart1Resource1.ChartTitle.TextBlock.Text".

```ASP.NET
<telerik:RadChart ID="RadChart1" runat="server" enableembeddedskins="False"
meta:resourcekey="RadChart1Resource1">
<PlotArea>
   <YAxis MaxValue="50">
   </YAxis>
   <YAxis2 MaxValue="3" MinValue="1" Step="1">
   </YAxis2>
   <XAxis MaxValue="3" MinValue="1" Step="1">
   </XAxis>
</PlotArea>
<ChartTitle>
   <TextBlock Text="Sales">
   </TextBlock>
</ChartTitle>
...    
```

> note Localization can also be performed using the Microsoft Localization API to retrieve resources programmatically at runtime.