Page MenuHomePhabricator

Add an option to update.php script of LocalisationUpdate for scoping languages
Closed, InvalidPublicFeature

Description

In T272830, @Nikerabbit wrote:

While Wikimedia sites have weekly deployment cycle, third party wikis do not get updated translations unless the upgrade to a new major release. They can run LocalisationUpdate, but in practice nobody does because it needs manual setup and is very slow (if used against github) or takes a lot of disk space if using with local clones of everything).

As an administrator of a third party wiki, I've also felt the update is slow if used against Github as the update.php queries and fetches the translations of all languages from the repository. However, small wikis are commonly monolingual, there are few needs to provide updated translations of all displayable languages that are not the content language of the wiki, omitting other languages is a quite reasonable choice to small wiki administrators. Based on this, I propose to introduce a new option for scoping languages.

Proposal 1
# The next line updates all languages
php update.php
# The next lines update only specified languages
php update.php --lang es
php update.php --lang es --lang fi
Proposal 2
# The next line updates only the content language
php update.php
# The next line updates all languages
php update.php --all-lang
# The next line updates the content language of the wiki and the specified language
php update.php --lang de

Though I'm not sure which behavior is better, both meet the requirement.

Event Timeline

I don't think the default behavior should be changed, but adding a language filter seems reasonable. Since I am currently working on T272830: Support doing translation update backports to stable branches, I'm curious whether that task or this task would be more beneficial for you?

Honestly, the language filters would not be applied to the wiki I involved in because the wiki is multilingual at least on the main page and the wiki is willing to have a very long execution time as a cronjob. If the language filter is added, I would use it personally for testing as the long execution time is undesirable for tests. On the other hand about the backporting, I love backporting but it is also true that waiting for the next release for translation updates is slower than LocalisitionUpdate.

Lens0021 changed the subtype of this task from "Task" to "Feature Request".Jul 28 2021, 8:35 AM
Jdforrester-WMF subscribed.

The LocalisationUpdate extensions has been archived. See T309694 for details.