As you use ASP.NET, you can also use ASP.NET Ajax. If so, there are two properties on ScriptManager :
EnableScriptLocalization - Gets or sets a value indicating whether the ScriptManager control displays localized versions of script files.
EnableScriptGlobalization - Gets or sets a value indicating whether the ScriptManager control supports a script that supports parsing and formatting of culture, specific information.
<asp:ScriptManager ID="AjaxManager" runat="Server" EnablePartialRendering="true" EnableScriptGlobalization="true" EnableScriptLocalization="true" />
If you enable both of them (set to true), then ASP.NET Ajax extenders, etc. should automatically be localized in the culture specified in web.config:
<configuration> <system.web> <globalization fileEncoding="utf-8" requestEncoding="utf-8" responseEncoding="utf-8" culture="en-GB" uiCulture="en-GB" /> </system.web> </configuration>
For example, setting this will localize the AjaxControlToolkit Calendar to your particular culture.
Even if you are NOT using ASP.NET Ajax, adding ScriptManager and turning on localization will give you a useful javascript variable called __cultureInfo that contains a JSON array of localized formate, such as currencies, dates, etc.
"CalendarType":1,"Eras":[1],"TwoDigitYearMax":2029,"IsReadOnly":true},"DateSeparator":"/","FirstDayOfWeek":1,"CalendarWeekRule":0,"FullDateTimePattern":"dd MMMM yyyy HH:mm:ss","LongDatePattern":"dd MMMM yyyy","LongTimePattern":"HH:mm:ss","MonthDayPattern":"dd MMMM","PMDesignator":"PM","RFC1123Pattern":"ddd, dd MMM yyyy HH\u0027:\u0027mm\u0027:\u0027ss etc....