Awaiting deployment on Translatewiki.net

This is working well. See patch - https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/518879

SemanticTasks extension's configuration has been updated on Translatewiki.net to reflect the move to Github.

Implemented a fix for this. In addition removed some compatibility code added for pre MW 1.31. Fixed an issue were we were not updating the # of users under the site_stats.

• Renames are determined based on content within a language in a group. If a message key has been renamed, the old key in the wiki will appear as deleted, and the new incoming key will appear as a new message. We determine renames by comparing the content of the messages deleted from the wiki, and new incoming messages. If the content is the same, we consider them a rename.
• In a group, if the source language key is renamed, then all the other language message keys will also be renamed.
• It is not possible to ignore renames, but the matched renamed messages can be broken and added as a new messages.
• If the content of the incoming new key, and the deleted wiki key is not similar, the system will not be able to recognize them as renames. In such cases, it is possible to manually mark a new message as a rename of an old message using the Rename dialog.
• A check has been added to ensure that two users cannot update the changes at the same time. For eg: User A and B load the ManageMessageGroup page. User B breaks a rename, but user A is still looking at an old screen that does not reflect this updated change. When A submits the ManageMessageGroup page, the system will warn them that they have outdated changes and they should reload the page to see the latest changes.

For caching, plan is to setup Redis and then,

This has been deployed on Translatewiki.net. I've checked that the latest Portuguese translations are present.

Hi Kartik,

Cool, I'll do that.

As per the comments above, we're going to mark this as done. Subsequent improvements will be carried out on the child tasks created.

@Guycn2 - Once the issues outlined by Raymond are fixed, we can proceed on adding this project to Translatewiki.net

Greetings everyone.

Hi @MarcoAurelio - Would it be possible to fix the issues mentioned by Raymond? We'll look at adding the project to translatewiki.net after that.

@kostajh - Thank you.

(If you'd like to enable the pipeline for an extension you maintain or contribute to, please reach out to us via the comments on this post.)

Tested this on Translatewiki.net.

We will have to,

I am fairly confident that the newly added strings in the commit here were lost because the JSON was invalid. There is a trailing comma at the end of the last key which should not be there.

Does this make sense? Do you see any step where the user may lack the information needed to make the decision?

My intention with the dialog box was to have something similar to what Phab has when editing related tasks

@Nikerabbit - Thanks for that assessment.

I'm seeing the following -

I think this UI looks much more intuitive. Few points,

OK, so I should have clarified, the hide option is to collapse the messages themselves. So right now there are two notices shown to the users. The hide button will collapse the section and show only a single notice which in this case is Definition uses {{PLURAL:.... It does not the collapse the diff notice.

While translating an outdated message, it is possible to see the "difference" between the previous message by clicking on Show difference. Currently it is not possible to Hide differences once expanded. Sometimes the difference can be very long and not being able to hide the difference is a problem.

This is done and deployed on Translatewiki.net

This is done and deployed on Translatewiki.net

Had to run the createMessageIndex.php script again after autoimport to update the message index after adding Ajapaik web app and mw-scss extension to Translatewiki.net.

Have been using this updated UI on Translatewiki.net for a few days now. Changes have been working as expected.

This is working as expected. Tested on meta.wikimedia,

This is fixed. Tested on meta.wikimedia

Tested this on mediawiki.org, and I see that the language is now part of the query string for Link to message

The patch was merged and the change has been deployed on Translatewiki.net.

Hi @Puik - I'll be submitting a patch to update the configuration files on Translatewiki to add this new project. I expect to get round to it either today or tomorrow.

This is done. Screenshots from meta.wikimedia,

This is done. Screenshots from meta.wikimedia,

This is done. Screenshots from meta.wikimedia

This is fixed. Please see changes on meta.wikimedia

In T213802#5179450, @abi_ wrote:

With the latest patch, the translate extension will use the following keys,

1. wiki:translate-groups:v3 - Contains message groups implemented by other third party plugins such as the BannerMessageGroup by the central notice extension.
2. wiki:translate-mg:aggregate:v1 - Contains the array based configuration for the AggregateMessageGroups in the instance.
3. wiki:translate-mg:filebased:v1 - Contains the array based configuration for the FileBasedMessageGroups in the instance.
4. wiki:translate-mg:wikipage:v1 - Contains an array of strings representing the titles used to recreate the WikiPageMessageGroups in the instance.
   
   Earlier 2, 3 and 4 were part of the 1st key's cache. In addition, they cached serialized class objects, which have now been updated to store either array based configurations or strings.
   
   Note that the wiki prefix maybe different based on the instance setup.