From 6944f8912dd19cebc858cc43b1b8ecd8c10392af Mon Sep 17 00:00:00 2001 From: Rick Anderson Date: Thu, 22 Jun 2017 14:12:41 -0700 Subject: [PATCH] Update localization.md (#3522) --- aspnetcore/fundamentals/localization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/fundamentals/localization.md b/aspnetcore/fundamentals/localization.md index 677523bb6b..57a176136a 100644 --- a/aspnetcore/fundamentals/localization.md +++ b/aspnetcore/fundamentals/localization.md @@ -171,7 +171,7 @@ If you create a resource file in Visual Studio without a culture in the file nam ### Adding Other Cultures -Each language and culture combination (other than the default language) requires a unique resource file. You can create resource files for different cultures and locales by creating new resource files in which the ISO language codes are part of the file name (for example, **en-us**, **fr-ca**, and **en-gb**). These ISO codes are placed between the file name and the .resx file name extension, as in *Welcome.es-MX.resx* (Spanish/Mexico). To specify a culturally neutral language, you would eliminate the country code, such as *Welcome.fr.resx* for the French language. +Each language and culture combination (other than the default language) requires a unique resource file. You create resource files for different cultures and locales by creating new resource files in which the ISO language codes are part of the file name (for example, **en-us**, **fr-ca**, and **en-gb**). These ISO codes are placed between the file name and the *.resx* file name extension, as in *Welcome.es-MX.resx* (Spanish/Mexico). To specify a culturally neutral language, remove the country code (`MX` in the preceding example). The culturally neutral Spanish resource file name is *Welcome.es.resx*. ## Implement a strategy to select the language/culture for each request