Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

ASP .NET Core default language is always English

I set the localization as described in Microsoft's blog, but the default language is always English. This is how my Startup.cs looks like with regards to the localization.

CultureInfo[] supportedCultures = new[]
            {
                new CultureInfo("ar"),
                new CultureInfo("en") 
            };

In ConfigureServices method:

services.Configure<RequestLocalizationOptions>(options =>
    {
        options.DefaultRequestCulture = new RequestCulture("ar", "ar");
        options.SupportedCultures = supportedCultures;
        options.SupportedUICultures = supportedCultures;
    });
    services.AddLocalization(options =>
    {
        options.ResourcesPath = "Resources";
    });

    
    services.AddMvc()
    .AddViewLocalization()
    .AddDataAnnotationsLocalization();

In Configure method:

app.UseRequestLocalization(new RequestLocalizationOptions()
{
    DefaultRequestCulture = new RequestCulture("ar"),
    SupportedCultures = supportedCultures,
    SupportedUICultures = supportedCultures
});
like image 454
HishamGarout Avatar asked Jun 11 '17 05:06

HishamGarout


People also ask

What is the default language of ASP?

The default scripting language in ASP is VBScript.

How do I change the language of a resource file in ASP.NET MVC?

Now go to the browser and change the language for Tool -> Internet Options. Click the Add button. Select the language depending on your resource file language and click ok. Run you application and click the submit button.

How ASP.NET applications are localized?

App localization involves the following: Make the app's content localizable. Provide localized resources for the languages and cultures you support. Implement a strategy to select the language/culture for each request.


2 Answers

You are setting "arabic" as DefaultRequestCulture but DefaultRequestCulture is used if none of the built-in providers can determine the request culture. The default providers are:

  1. QueryStringRequestCultureProvider
  2. CookieRequestCultureProvider
  3. AcceptLanguageHeaderRequestCultureProvider

Most likely the culture is determined from the Accept-Language HTTP header that the browser is sending.

You have to remove the AcceptLanguageHeaderRequestCultureProvider in order to fallback to DefaultRequestCulture. To do that, we can overwrite the RequestCultureProviders list of RequestLocalizationOptions and use only the other two providers. In Startup.cs:

public void ConfigureServices(IServiceCollection services)
{
    CultureInfo[] supportedCultures = new[]
    {
        new CultureInfo("ar"),
        new CultureInfo("en")
    };

    services.Configure<RequestLocalizationOptions>(options =>
    {
        options.DefaultRequestCulture = new RequestCulture("ar");
        options.SupportedCultures = supportedCultures;
        options.SupportedUICultures = supportedCultures;
        options.RequestCultureProviders = new List<IRequestCultureProvider>
        {
            new QueryStringRequestCultureProvider(),
            new CookieRequestCultureProvider()
        };
    });
}

and in Configure method just use app.UseRequestLocalization(); before app.UseMvc();

like image 96
tmg Avatar answered Oct 13 '22 13:10

tmg


If you are using Ajax call to set the culture and respond the back to the client with JSON result.

You have to set the cookie value corresponded to ASP.Net as below in browser level. otherwise, localizer is unable to find the correct culture with cookie value.

var date = new Date();
date.setTime(date.getTime() + (30*24*60*60*1000));
expires = "; expires=" + date.toUTCString();
document.cookie = '.AspNetCore.Culture' + "=c=" + (data.message || "ko-KR") + "|uic=" +(data.message || "ko-KR")  + expires + "; path=/";
window.location.reload();
like image 43
dush88c Avatar answered Oct 13 '22 13:10

dush88c