Page MenuHomePhabricator

Can't send translation notifications for translatable banners
Open, LowPublic

Description

Currently, one cannot use translation notifications for translatable CN banners: They do not show up in the dropdown list of available translation tasks to notify translators about in https://meta.wikimedia.org/wiki/Special:NotifyTranslators . (Neither are they contained in the list of available translation tasks that greets willing translators at https://meta.wikimedia.org/wiki/Special:PageTranslation .)

If this should rather be categorized as a bug for the Translate or TranslationNotification extensions, please let me know. Bur for now I'm filing it as a bug for CentralNotice, because I think that it may have to do with the way CN stores the translation units belonging to a particular banner. E.g. these two pages contain the German translation for the banner "FDCpropreview20133_v1":

https://meta.wikimedia.org/wiki/CNBanner:FDCpropreview20133_v1-text1/de

https://meta.wikimedia.org/wiki/CNBanner:FDCpropreview20133_v1-text2/de

and they are collected in the translation group "Centralnotice-tgroup-FDCpropreview20133_v1". Perhaps it would be possible to organize them into a translatable *page* instead? E.g.

https://meta.wikimedia.org/wiki/CNBanner:FDCpropreview20133_v1
with the translation units called "text1" and "text2", so that the above two URLs would become:

https://meta.wikimedia.org/wiki/CNBanner:FDCpropreview20133_v1/text1/de

https://meta.wikimedia.org/wiki/CNBanner:FDCpropreview20133_v1/text2/de

(This might have other benefits too, e.g. that one could link to a wiki page showing the entire translated text for a banner just in that language.)

That's just me thinking aloud though. Any other solution that enables the use of TranslationNotifications for translatable banners would work too. For my current use case, I'm now resorting to setting up a separate translatable page and manually copying the translation text back and forth, but that doesn't scale.

Details

Reference
bz56187

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 22 2014, 2:37 AM
bzimport set Reference to bz56187.
bzimport added a subscriber: Unknown Object (MLST).

mwalker wrote:

The last time this came up; it was because we create the CentralNotice aggregate group -- which was not queried for when looking for translation tasks.

I know Phillipe has just been adding [ Help with translation ] links to banners to solve this problem.

@Niklas; I know I have some open tasks to retire translation groups that are no longer needed which I know was something we wanted so that translators were not presented with out of date content to translate. I'm guessing that still stands -- but if that was out of the way; do you have any thoughts?

Sorry didn't read the description completely. Will do that later. Just noting in that Special:NotifyTranslators was only implemented for translatable pages. The banners are not considered as translatable pages in Translate extension.

(In reply to comment #1)

The last time this came up; it was because we create the CentralNotice
aggregate group -- which was not queried for when looking for translation
tasks.
I know Phillipe has just been adding [ Help with translation ] links to
banners
to solve this problem.

Yes, we have been including these links routinely for a long time (e.g. https://meta.wikimedia.org/wiki/Special:CentralNoticeBanners/edit/FDCpropreview20132v1 - but I seem to recall it was common practice in 2012 already). And they are usually good drivers of translations. But not always (I have run several country-specific FDC community review banners for 6-10 hours now without getting translations for the local languages in that country). Also, there is some kind of expectation that at least for major languages, it is preferable to already have translated versions available when launching the banners, instead of presenting them in English first. So the links don't quite solve this problem.

(In reply to comment #2)

Sorry didn't read the description completely. Will do that later. Just noting
in that Special:NotifyTranslators was only implemented for translatable
pages.
The banners are not considered as translatable pages in Translate extension.

Thanks, that was indeed my assumption in the tentative proposal above, so it's useful to have this confirmed (I also clarified the documentation on mediawiki.org in that regard).

@Tbayer is this still a problem? Thanks!

Yes, the situation hasn't changed.

atgo set Security to None.
Elitre added a subscriber: Elitre.May 4 2015, 5:21 AM

Reading this bug and T87448, I'm increasingly convinced that banners *should* be translated pages. There's no good reason to translate each string as a separate message, it takes away from context and continuity. Banner messages are in this weird overloaded role anyway, where they are also used as variable parameters, and we should clear that up.

The historical reason for the banner message misstep was probably that most banners are heavily marked up with raw, unbalanced HTML and other junk, there are very long sections which would not be translated.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 21 2015, 7:11 AM

The historical reason for the banner message misstep was probably that most banners are heavily marked up with raw, unbalanced HTML and other junk, there are very long sections which would not be translated.

I think there were concerns about only using translations which have been marked as reviewed. But that should be possible even with translatable pages with some effort. With regards to heavy markup, sensible use of <translate>...</translate> and tvars tags can hide that markup from translators.

As an additional bonus, you would be able to easily group messages on two levels: similar messages on one page (as different units), and similar pages on aggregate message groups (see glossary and documentation if you are not familiar).

KTC added a subscriber: KTC.Jan 31 2016, 9:16 PM
Jseddon lowered the priority of this task from Normal to Low.Aug 16 2016, 10:59 PM
mmodell removed a subscriber: awight.Jun 22 2017, 9:39 PM