Add option (disabled by default) to force untranslated centralnotices
Open, HighPublic

Description

It often happens that banners are enabled in languages which have no translations, against the usage guidelines, and the fallback language is used automatically (usually English): this makes users riot.

Centralnotice admins are currently expected to manage the list of languages manually, adding each language only when ready. This means doubling the work around publishing of translations, so admins are lazy and just select all languages. Given they are humans and we can't just whip them endlessly, please make the interface easier.

Adding a checkbox to control whether a banner will be shown even in languages where no translation is available should be comparatively easy. Fallbacks should be disabled by default.

Nemo_bis updated the task description. (Show Details)
Nemo_bis raised the priority of this task from to High.
Nemo_bis added subscribers: Nemo_bis, PiRSquared17, Glaisher.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 20 2015, 10:11 AM

I'd support this, I don't know the level of difficulty but I imagine that it shouldn't be too horrible given the list of translated languages already exists and is shown on the banner page. The one question would be on a campaign level (where language settings are usually done) or the banner level (where the translations are). I imagine the easiest is banner but that may cause conflicts.

I do think that requiring the checkbox to be available is important though, for globally important messages (including the one Nemo mentions here, in my opinion) it can end up being better to deploy the banner with a translate link and then publish translations as they come in to get the message out to as many people as possible as quickly as possible. Getting advance translations without the banner for all can be close to impossible (even some of the most popular languages can be difficult at times).

jeremyb-phone set Security to None.Apr 27 2015, 2:59 AM
jeremyb-phone added a subscriber: jeremyb.
Elitre added a subscriber: Elitre.Apr 27 2015, 3:16 PM
awight added a subscriber: awight.Oct 21 2015, 6:46 AM

@Nemo_bis
Thank you for bringing this up! Showing readers untranslated banners is pretty outrageous--I suspect CN admins are sometimes doing this as a workaround for showing a banner to everyone in a country, regardless of their first choice interface langage--see T53475, which might be aggravating that problem.

Do you have any examples where enabling your proposed checkbox would make sense? I'm having a hard time imagining a case--a banner only contains images or something? Perhaps you're just suggesting this checkbox as a way to slowly migrate the people who think that targeting all languages makes sense?

Also, maybe we should have a subtask for targeting languages automatically as they are translated?

@Nemo_bis
Thank you for bringing this up! Showing readers untranslated banners is pretty outrageous--I suspect CN admins are sometimes doing this as a workaround for showing a banner to everyone in a country, regardless of their first choice interface langage--see T53475, which might be aggravating that problem.

Do you have any examples where enabling your proposed checkbox would make sense? I'm having a hard time imagining a case--a banner only contains images or something? Perhaps you're just suggesting this checkbox as a way to slowly migrate the people who think that targeting all languages makes sense?

The problem is that getting translations for banners is incredibly difficult beyond the major languages and putting a banner up with a translation link gets those faster then any possible means. Especially for notices that really should go to everyone (legal policy changes where everyone is legally required to be notified for example or major consultations like the privacy policy or Terms of Use where cutting small languages completely out of the loop is just not an option etc) it is good (and important) to try to get as many languages as possible from the start but waiting until we have all languages (essentially impossible) or not sending them the banner at all is just not an viable option. We need to have a way to still open the flood gates at some point for those banners.

In a perfect world what i'd do in a case like that is send the banner text out to translators for translation a couple weeks in advance, get as many as possible and then turn the banners on only for those wikis we have languages in. Then we keep turning it on as we get more but eventually (since we're not getting translations for every language we support) we turn it on for all languages ensuring that the banner has a link for translating that banner and we watch carefully to ensure that those languages get published rapidly. [or even better that those languages get published automatically but we need to ensure we have some carefulness for spam and vandalism in that case]/

Also, maybe we should have a subtask for targeting languages automatically as they are translated?

I definitely think having a way to target languages automatically as they are targeted is useful and I'd recommend it frequently.

Do you have any examples where enabling your proposed checkbox would make sense? I'm having a hard time imagining a case--a banner only contains images or something?

For instance a banner whose purpose is to ask translations from English to language X, shown only to logged-in users with a certain amount of edits and who know both languages (as found by uls-languages cookie or similar, for instance).

These are very convincing cases, but by this logic wouldn't you say that all campaigns are important enough to be displayed before they have been fully translated?

MarcoAurelio added a subscriber: MarcoAurelio.