| Pginer-WMF | |
| Jul 26 2018, 10:37 AM |
| F24147043: Screen Shot 2018-07-26 at 12.34.34.png | |
| Jul 26 2018, 10:37 AM |
| F24147028: Screen Shot 2018-07-26 at 12.33.49.png | |
| Jul 26 2018, 10:37 AM |
When content such as tech news is available in a language variant such as Brazilian Portuguese (pt-br) but lacks a translation into Portuguese (pt), the MassMessage system publishes the English version on Portuguese Wikipedia. The expected result would be to consider the language variant as a fallback and show the content in Brazilian Portuguese instead.
| Content available in Brazilian Portuguese | Published content in English on Portuguese Wikipedia |
|---|---|
 |  |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T195760 Language Annual Plan 2018-2019 | |||
| Resolved | • Nikerabbit | T204818 Language tools maintenance intervention: Improve the quality of translations for Translate extension | |||
| Resolved | • Nikerabbit | T200414 Consider language variants when delivering content |
To the best of my knowledge, this is neither caused by MassMessage nor Translate. I believe (@Johan can correct me if I'm wrong) there's a Lua module that generates a giant #switch parser function to send out localized messages.
I'm also not sure whether pt is supposed to fallback to pt-br.
The same behavior is seen if you translate a [[MediaWiki:Message]] into [[MediaWiki:Message/pt-br]] but not [[MediaWiki:Message/pt]], and the UI is set to pt.
It's more complicated than that (e.g. it depends on whether Message is defined in i18n files too).
In MediaWiki language files pt falls back to pt-br and en, pt-br falls back to pt and en.
I'm sure this is fixed. We can now send translatable pages and it uses the language fallbacks.