Branch support for localisation of MediaWiki core
Closed, DeclinedPublic
Actions

Assigned To

None

Authored By

	Amire80
	Feb 20 2015, 3:48 PM

Description

Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/3895

Context

This story is part of the feature that will change the MediaWiki localisation format from executable PHP code to JSON. The full change is described in RFC Localisation format.

This is a complementary approach to Localisation Update.

Narrative

As a MediaWiki administrator, I can receive localisation updates with point releases of MediaWiki, so that I can benefit from localisation updates with very little effort.

Acceptance Criteria

Ensure branch support works again (2 versions back) in translatewiki.net
Ensure MediaWiki core branch localisation can be exported using Translate update to versions back (1.20/1.21).

Related Objects

Mentioned In: T148278: Include translations for "changecredentials*" and "credentialsform*" messages on REL1_27
T119938: Main page tab is not translated in 1.26

Event Timeline

Amire80 raised the priority of this task from to Low.Feb 20 2015, 3:48 PM

Amire80 added projects: Language-Team, MediaWiki-Internationalization.

Amire80 subscribed.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 20 2015, 3:48 PM

Nikerabbit updated the task description. (Show Details)Feb 22 2015, 2:23 PM

Nikerabbit set Security to None.

Nikerabbit added a project: translatewiki.net.

Nikerabbit subscribed.

Nikerabbit updated the task description. (Show Details)Feb 22 2015, 2:25 PM

Nemo_bis mentioned this in T119938: Main page tab is not translated in 1.26.Feb 27 2016, 11:49 PM

Nikerabbit removed a project: Language-Team.Jan 2 2018, 9:45 AM

Nikerabbit moved this task from Backlog to Processes on the translatewiki.net board.Jun 17 2018, 4:54 PM

Nikerabbit mentioned this in T148278: Include translations for "changecredentials*" and "credentialsform*" messages on REL1_27.Aug 29 2018, 6:20 AM

I assume there's no need for "Conversion script json->php if needed" anymore since all the currently supported branches are JSON now?

Also maybe this is a silly question, but if people can use LocalisationUpdate to get the latest translations, why couldn't we use that script but have it write output to the languages/ JSON files, and then commit the result?

Also maybe this is a silly question, but if people can use LocalisationUpdate to get the latest translations, why couldn't we use that script but have it write output to the languages/ JSON files, and then commit the result?

Not silly at all. It doesn't currently write to those JSON files, but that probably wouldn't take long. The main difference is that without explicit support from translatewiki.net side, it is not possible to translate messages that only exist in older versions, nor messages that have been changed in master. Given these are in the minority, it would be better than nothing though.

In the long run I would like to implement a generic LU service that is not software dependent.

Nikerabbit updated the task description. (Show Details)Aug 29 2018, 6:30 AM

Translation backports are almost as good and currently running.

Branch support for localisation of MediaWiki coreClosed, DeclinedPublicActions