Additional example for SupportedCultures to support ALL cultures

[ThinkElevenDave]

Description

[Enter feedback here]
The docs provide an example of supporting two cultures, but many people (based on StackOverflow activity) simply want numeric/date support dynamically without having to specify EVERY culture (of which they might not even know the end user's culture).

Frustratingly, our premium Copilot license in VS continues to suggest that, "options.SupportedCultures = null; // support all cultures" which appears to be both incorrect and misleading.

Therefore the documentation should also document how to dynamically support every culture, e.g.:

app.UseRequestLocalization(options =>
{
	var supportedCultures = CultureInfo.GetCultures(CultureTypes.AllCultures)
										.Where(cul => !string.IsNullOrEmpty(cul.Name))
										.ToArray();

	options.DefaultRequestCulture = new RequestCulture("en-GB"); // suggest using your largest audience's culture here
	options.SupportedCultures = supportedCultures;
	options.SupportedUICultures = supportedCultures;
});

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/globalization-localization?view=aspnetcore-8.0#dynamically-set-the-culture-in-a-blazor-web-app-by-user-preference

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/globalization-localization.md

Document ID

d6f07538-228e-9f96-680f-6c324caf11d6

Platform Id

bd2a8fe1-da71-2bfb-045d-1b5f49d944a4

Article author

@guardrex

Metadata

• ID: 15e7c51d-1839-1849-813a-23c4d21c64ae
• PlatformId: bd2a8fe1-da71-2bfb-045d-1b5f49d944a4
• Service: aspnet-core
• Sub-service: blazor

Related Issues

[github-actions]

🧟💀 Happy Halloween!!_* 🎃🧛

Stand-by! ... A green dinosaur 🦖 will be along shortly to assist.

[guardrex]

Thank you, @ThinkElevenDave! That's a welcome suggestion.

@ilonatommy, @hishamco ... How does that look to you?

[ilonatommy]

While the code makes sense for SupportedCultures, I don't think that any application provides satellite assemblies / resx files for "cultures which they might not even know the end user's culture". It would be good to underline the fact that SupportedUICultures is for localization and SupportedCultures for globalization and supplying "all possible" values for the former one does not make sense. We would like to change the line:

options.SupportedUICultures = supportedCultures;

to e.g.

  // Only the languages you actually localize for UI/resources
var uiCultures = new[]
    {
        new CultureInfo("en-GB"),
        // add more as you add resources
    };

CultureTypes.AllCultures includes neutral cultures (e.g., en, fr, es) which lack region-specific formats (currency symbol, some date defaults). For formatting scenarios (dates, numbers, currency) you typically want specific cultures (en-GB, fr-FR, etc.). I would change the getter argument to be CultureTypes.SpecificCultures.