Localization & Active Locales

[HeyJoel]

Localization is possible but requires changes to be made directly in the database. This area hasn't been looked at much and ideally we need to spend a bit of time working out the exact requirements of a flexible cms locale system.

• Ideally we'd have a way to define active locales in code
• The routing would be flexible (although we need to investigate the different ways sites might want to do this)
• We need to create a localized sample site
• We need to ensure that we test for situations where a locale is enabled and then disabled again with resources attached.

Any input here as to what might be needed by a locale system are welcome

[HeyJoel]

This area needs working on as part of the asp.net core migration. For now the active locale is determined by the current thread culture and available locales are still set in the db. The current thread culture can be set using the built in request localization middleware, but you need to define the supported culture collection to match your db localization settings.

TODO:

• Create a localization sample site so we can play around with the scope of localization in practice
• Work out a configuration strategy that is simple, extensible and in keeping with asp.net core.
• Implement a RequestCultureProvider for our standard url culture format e.g. 'cofoundry.org/en-GB/'
• Create a pluggable path formatter to allow customization of localized urls to be used in GetAllPageRoutesQueryHandler.CreateFullPath and IPagePathHelper

Test startup code:

var supportedCultures = new[]
{
    new CultureInfo("en-US"),
    new CultureInfo("en-GB"),
    new CultureInfo("es")
};

var options = new RequestLocalizationOptions()
{
    DefaultRequestCulture = new RequestCulture("en-US", "en-US"),
    SupportedCultures = supportedCultures,
    SupportedUICultures = supportedCultures
};
app
    .UseRequestLocalization(options)
    .UseCofoundry();

[HeyJoel]

Some additional info about why the culture list is restricted by default on this issue