Sitecore 10.1 with .NET Core rendering and custom cultures on Linux

sitecore-dotnetcore-customcultures.md

Sitecore 10.1 and .NET Core Rendering Host with Custom Cultures

In traditional Sitecore you can always insstall custom cultures using .NET Framework (unless you're on PaaS ;).

If you're running .NET Core RenderingHost on a Alpine linux based container, you're options are a bit more limited. One way would be to build additional cultures into alpine but it's quite a hassle. You need to build the custom .dat file first etc.

However, it turns out that you can actually create new CultureInfo("en-IS") without them being installed. There is however one culprit, these cultures are not included in the GetCultures method. This method is used internally by Sitecore to validate the that the route contains a valid culture for the localization to work.

Luckily you can replace the contraint added by Sitecore with a custom version that looks like `csharp public bool Match(HttpContext httpContext, IRouter route, string routeKey, RouteValueDictionary values, RouteDirection routeDirection) { if (!values.ContainsKey(RenderingEngineConstants.SitecoreLocalization.RequestCulturePrefix)) { return false; }

        var lang = values[RenderingEngineConstants.SitecoreLocalization.RequestCulturePrefix].ToString();
        CultureInfo culture = null;
        if (!string.IsNullOrEmpty(lang))
        {
            culture = CultureInfo.GetCultures(CultureTypes.AllCultures)
                                 .SingleOrDefault(c => c.IetfLanguageTag.Equals(lang, StringComparison.InvariantCultureIgnoreCase));

            if (culture == null && Regex.IsMatch(lang, "^[a-z]{2,3}(?:-[a-z]{2,3}(?:-[a-z]{4})?)?$"))
            {
                try
                {
                    culture = new CultureInfo(lang);
                }
                catch (Exception ex)
                {
                }
            }
        }

        return culture != null;

    }
}`