With this syntax, would this be possible?

In the last 24 hours, this happened 82 times.

@NicoV - Thanks. Will leave this open for a while to track any further issues we notice.

@NicoV - I would recommend avoiding the generation of the .po files during the build process. Translatewiki.net will output the po files based on the latest pot files.

@NicoV - The issue with the extra "}" appears to be fixed now. Can you please confirm from your side?

Ran the exports today and did not notice this issue.

@DannyS712 - Works now: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/608602

Thanks @Amire80 for creating the Message delivery list for testing this task. Tested on metawiki. Messages were sent from MetaWiki to MediaWiki.

Now displaying some documentation related to the Translate markup when the user edits a source translation page. See screenshots below for more details on how this looks.

The task description captures various options and their pro's and con's quite well. S-CONTROL and M-VERSIONING would be the ideal direction to move forward in. That gives translation admins, more control over how translations are rendered and might work well for scenarios that we have not thought of right now.

We've added a group synchronization cache, which has the follow cache keys,

Found 5 instances of this in Logstash since it was deployed on mediawikiwiki.

I think this is setup well and can be marked as done.

During imports,

@NicoV - This appears to be an issue with plural expansion / closing on our end. We will have to make a fix for this. Filed T256227: Incorrect plural expansion / closing for Gettext plurals to track the issue.

The issue was caused due to a human error. I ran the exports from translatewiki.net before all the existing translations from WPCleaner were imported into translatewiki.net which caused some translations to become empty. Since this was the first import from WPCleaner, we should have waited longer before starting the exports. I don't expect this to happen again in the future.

@NicoV, Thanks for checking this. I noticed the huge amount of changes, and was planning to check them tomorrow. We'll import the new changes from WPCleaner and push out the changes again tomorrow.

Possibly related to T255334: Translation page does not contain the latest translations/last translation

In T255101#6230755, @NicoV wrote:

@abi_

Do you know how to ask for adding a Phabricator project for WPCleaner?
It's probably by creating a task here, but is there any special tags or anything else?

As Niklas said earlier, the message definition should not be null. We need to identify where this is happening so that we can properly fix it,

I've gotten necessary access and will be taking care of testing this.

2. The skin is just good to have and may give translators some additional info about the project. Currently the skin is used on the project page and the group selector for example -
   
3. How often are changes from master deployed to the production server? We don't want translations pushed out from translatewiki to sit idle without being used for long periods of time.

While adding some language code maps, noticed that these are the languages defined in the build file. Things to note,

Twn pushed out the changes today: https://github.com/StarCitizenTools/mediawiki-skins-Citizen/commit/5f1815b74cd3bce98b7ed5eaee965a0351d94bf1

I've configured the bot to push changes to a branch named translatewiki and then create a PR to the master branch. You can review it, and merge.

In T255101#6223068, @abi_ wrote:

2. I think that should be fine. From my understanding, no additional build process is needed if when new translations are needed?

We've accepted the Github request.

This has been deployed and translations are being pushed out to the repository.

1. That is usually enough. We will be pushing translations today, so will have confirmation then.
2. I think that should be fine. From my understanding, no additional build process is needed if when new translations are needed?
3. Releasing periodically even if there are no feature / bug fixes just for translation updates is recommended. Since new translations maybe available every week, releasing that frequently maybe too much, so once every 2 weeks or even a month should be good.

@NicoV - Few questions,

There are three different editors / editor modes that we've to handle,

In T254134#6181073, @Majavah wrote:

I added you to Trusted-Contributors

@Aklapper - Could it be because I was a contractor before and then became a WMF Employee at which time my account was renamed? During my time as a contractor, I had created the MediaWiki account, which was then renamed to APatro_(WMF)

Please let me know if its easier to get access to Trusted-Contributors instead and use that to vote.

Task objective: Make it easier for editors editing translatable pages to find documentation describing the Translate extension specific markup.

Once the changes for this task are deployed, user's of the MassMessage extension will be able to, send a translated page from the wiki as a message. Depending on the language of the target page where the message has to be delivered, and whether a translation of the source page is available in that target page language, the source page will be either delivered in the target page language, a fallback language, or the source language.

A commit was pushed out by Translatewiki.net to the repository today - https://github.com/jwbth/convenient-discussions/commit/9d019e3a7bd328555b1b5b5eb90b3e0ea6a72ec1

BTW, how often are changes of the source language file in the source repository checked?

As you noticed, the patch has been deployed and messages are ready to be translated.

We've released updated versions of the library on npm (v0.2.0) and packagist (v1.0.0).

@Jack_who_built_the_house - No nothing pending from your side as of now. We will add the project to twn, and comment here.

As far as I can tell, this code has been unchanged for a while. Did we add update phan or add any new rules to it?

This has been deployed and tested on translatewiki.net.

This is deployed and tested on Translatewiki.net

I think the following pages would be helpful to provide to user's when editing a source translation page,

I've added a short notice when users are editing a source translation page -

@abi_ Sorry, I had no time to update the repository properly. The path for translations has moved from src/js/i18n/%CODE%.json to i18n/%CODE%.json (there is the old path in the patch).

@Jack_who_built_the_house - I'll go through and answer your questions tomorrow, but couple of things that we wanted to call out,

1. The English strings have double quotes used as apostrophe, any specific reason why? Eg: Show a link to edit other users\" comments
2. English only has two plural forms, but we noticed that there are messages that have three forms specified. Eg: "notification-newcomments": "$1 new {{plural:$1|comment|comments|comments}}$2$3

I've added the,

1. Project page - https://translatewiki.net/wiki/Translating:Convenient_Discussions
2. Translation description

While we identify what's causing the spike in memory usage, we've increased the memory limit to 2.5G. Will keep monitoring.