To be clear this isn't just a ULS thing, the current default rule for CN is to always use the 'user' language rather then the content language. This is, essentially, a request to change to contentlanguge :)

Rephrasing summary.

@AndyRussG: I just noticed that CNBannerChoiceDataResourceLoaderModule might have a caching bug here... If context->getLanguage() is UI language, and we're caching for project/content language combination, then there's a chance of incorrect data getting into the cache?

Change 197741 had a related patch set uploaded (by Awight):
CentralNotice uses content rather than interface language

https://gerrit.wikimedia.org/r/197741

If we decide this is the right thing to do, here's a patch... https://gerrit.wikimedia.org/r/197741

I'm not sure how to solve the variant issue, however. I don't think the content language variant is available to the ResourceLoader startup module, nor would it be used to split the cache?

Gotcha for local testing: on the production site, ?variant=tg-latn will set the RL lang=tg-latn param, but I don't know what the correct LocalSettings config would be to make that happen. Locally, I see lang=tg when I use variant, and lang=tg-latn if I use the uselang param instead.

@Nemo_bis
I'd be curious what you think of this feature request, do you agree that it makes more sense than targeting banners by MediaWiki interface langauge?

In T53475#1741248, @awight wrote:

@Nemo_bis
I'd be curious what you think of this feature request, do you agree that it makes more sense than targeting banners by MediaWiki interface langauge?

No. I can't imagine a case in which it would make sense, other than as workaround for T50956.

@Nemo_bis, could you clarify your comment?

Imagine that I go to the Italian Wikipedia. Imagine that my interface language is set to English there. Imagine that CentralNotice is running banners in Italian (but not English), specifically for the Italian Wikipedia, about something that affects that particular wiki.

Should I (a) see the banner in Italian or (b) see nothing?

I am not sure if this proposal is a good idea in the way it has been described above: as I read there to replace the system from user language to content language. If it is additional to the current setup, maybe it is possible, but in replace of it I am against.

The strength of the CentralNotice system is that it communicates to the user in the language they have set for themselves. The proposal above seems to aim in removing this strength...

@Romaine
Great points, I think you're right that we need to offer both flavors of language targeting.

I think we need to separate receiving from sending. The problem is that the sender isn't thinking in terms of people who speak Dutch. The sender is thinking in terms of people at the Dutch Wikipedia.

Imagine that we are posting a message that is available in Dutch (only) and that is useful for all contributors at the Dutch Wikipedia (only). (Perhaps we are announcing a local election.) What we have now is this:

What we want is this:

and see T55641

This issue affected T194939 and in place of CentralNotice three seperate sitenotices will be used

Change 197741 abandoned by Awight:
CentralNotice should use content rather than interface language

https://gerrit.wikimedia.org/r/197741