you can inject ILocalizationService

I've a kind similar issue with Ajax and Culture.

I'm trying to implement "Load more" button via Ajax. It sends an Ajax request to SurfaceController and than it pass parameters to the ViewComponent (including current culture). But it always returns content in default language.

What am I doing wrong? And how to get content in current culture?

public IViewComponentResult Invoke(string tag, int currentPage, int pageSize,  string culture)
    {

        if (_umbracoContextAccessor.TryGetUmbracoContext(out IUmbracoContext? context) == false)
        {
            throw new NotImplementedException();
        }

        var personNodes = context.Content.GetAtRoot()
            .First()
            .FirstChild<DoctorsAll>()
            .Children<Doctor>(culture) ?? Array.Empty<Doctor>();

        if (!String.IsNullOrEmpty(tag))
        {
            personNodes = personNodes.Where(x => x.ServiceTag.Contains(tag));
        }

        var result = personNodes
            .Select(p => new FilterViewModel()
            {
                Title = p.HeroTitle,
                Description = p.HeroText,
                ImgUrl = p.HeroImage.Src,
                Link = p.Url()
            })
            .Skip(pageSize * currentPage)
            .Take(pageSize)
            .ToList();

        if(!result.Any())
            return Content(string.Empty);

        return View(result);
    }

In case anyone is still searching, take a look at the UmbracoPublishedContentCultureProvider. This sets the default culture at some points in the application. Leading to unexpected behaviour of the UICulture in the View rendering.

You can override this by creating your own RequestCultureProvider, this example takes the cultureinfo of a request header. The order of inserting is important. The Umbraco providers are inserted before the original microsoft providers (QueryStringRequestCultureProvider for example)

/// <summary>
///     Sets the request culture to the culture of the header
/// </summary>
public class HeaderCultureProvider : RequestCultureProvider
{
    private readonly RequestLocalizationOptions _localizationOptions;
    private readonly object _locker = new();

    /// <summary>
    ///     Initializes a new instance of the HeaderCultureProvider class.
    /// </summary>
    public HeaderCultureProvider(RequestLocalizationOptions localizationOptions) =>
        _localizationOptions = localizationOptions;

    /// <inheritdoc />
    public override Task<ProviderCultureResult> DetermineProviderCultureResult(HttpContext httpContext)
    {
        var header = httpContext.Request.Headers["CultureCode"];
        if (header.Count > 0)
        {
            var culture = header[0];
            if (culture != null)
            {
                lock (_locker)
                {
                    // We need to dynamically change the supported cultures since we won't ever know what languages are used since
                    // they are dynamic within Umbraco. We have to handle this for both UI and Region cultures, in case people run different region and UI languages
                    // This code to check existence is borrowed from aspnetcore to avoid creating a CultureInfo
                    // https://github.com/dotnet/aspnetcore/blob/b795ac3546eb3e2f47a01a64feb3020794ca33bb/src/Middleware/Localization/src/RequestLocalizationMiddleware.cs#L165
                    CultureInfo? existingCulture = _localizationOptions.SupportedCultures?.FirstOrDefault(
                        supportedCulture =>
                            StringSegment.Equals(supportedCulture.Name, culture, StringComparison.OrdinalIgnoreCase));

                    if (existingCulture == null)
                    {
                        // add this as a supporting culture
                        var ci = CultureInfo.GetCultureInfo(culture);
                        _localizationOptions.SupportedCultures?.Add(ci);
                    }

                    CultureInfo? existingUICulture = _localizationOptions.SupportedUICultures?.FirstOrDefault(
                        supportedCulture =>
                            StringSegment.Equals(supportedCulture.Name, culture, StringComparison.OrdinalIgnoreCase));

                    if (existingUICulture == null)
                    {
                        // add this as a supporting culture
                        var ci = CultureInfo.GetCultureInfo(culture);
                        _localizationOptions.SupportedUICultures?.Add(ci);
                    }
                }

                return Task.FromResult<ProviderCultureResult>(new ProviderCultureResult(culture));
            }
        }

        return NullProviderCultureResult;
    }
}

Then add the provider like this:

public class CultureAttributeLocalizationOptions : IConfigureOptions<RequestLocalizationOptions>
  {
      public void Configure(RequestLocalizationOptions options)
      {
          options.RequestCultureProviders.Insert(0, new HeaderCultureProvider(options));
      }
  }

Eventualy in the composer, you can add the options

// add header culture attribute
services.ConfigureOptions<CultureAttributeLocalizationOptions>();

Hope this helps.

is working on a reply...