This is now deployed on Translatewiki.net. Groups and individual messages that have had errors are displayed to administrators, and can be marked as resolved.

Commented on wrong task.

We've done two things to address this larger issue:

This has been tested on Translatewiki.net

Another update on what's completed:

Language data release is done. Leaving in Recheck after deployment for monitoring.

Now available for translations here: https://translatewiki.net/wiki/Special:Translate?group=wikipedia-library-partner-descriptions

Cita is now available for translation at: https://translatewiki.net/w/i.php?title=Special:Translate&group=cita

Waiting on Amir to provide feedback regarding this task. Another option would be to involve Pita to also help with reviewing the documentation.

This has been deployed on translatewiki.net and is working as expected.

@jsn.sherman - This approach of having a separate JSON file may work out better for translators. It'll give them more context as to what they are translating. The changes for this are already present in this patch: 677559: Wikipedia Library Card Platform - Add partner descriptions | https://gerrit.wikimedia.org/r/c/translatewiki/+/677559

closing this as this does not seem to be issue.

I've submitted a series a patches that replaces usage of blacklist with exclusionList and whitelist with inclusionList. That should take care of all occurrences of (white|black)[ \-]?list in Translate but some more work will be needed for translatewiki.net

This is deployed and is working on MediaWiki.org:

In T254481#6954394, @Sakretsu wrote:

Still not working since Tech news sections are now marked by the new static name "tech-newsletter-content". It would be great if it was the same as before, e.g. "technews-2021-W12".

Update: I'm unable to reproduce this issue locally. Seems to be something that's specific to meta. This patch: https://gerrit.wikimedia.org/r/674969 should fix the issue and if in case it doesn't we'll go ahead and remove the type hint from the method argument.

Translations exported here: https://github.com/ProfessionalWiki/EDTF/commit/7f4fc41c8b05cfe6c5730d23ecff1964a7f5f79f

We've submitted this patch that will limit the number of translatable pages that can be moved: 668655: Limit the max number of pages that can be moved | https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/668655

We're now highlighting the pages that don't support template transclusion

The project is now available for translation at: https://translatewiki.net/wiki/Special:Translate?group=mwgithub-edtf

Yes, I'll update the configuration to ignore this validation

In T275298#6908594, @JeroenDeDauw wrote:

Well yeah, but why? Is this somehow used on TranslateWiki? The linked https://github.com/ProfessionalWiki/IdGenerator is a MediaWiki extension, which uses the description on Special:Version. This request is about a PHP library, so there is no place the message would be shown.

In T47096#6912104, @Pols12 wrote:

So, in order to determine whether a page is translation-aware when transcluded, is this now a sufficient test to look at this checkbox state in Mark special page?

The option is now,

A PR was opened with the changes: https://github.com/lucaswerkmeister/tool-lexeme-forms/pull/20/files

@JeroenDeDauw We'll now start processing this request. Can you take a look at the "concerns" section?

Marking this as medium, similar to what we have for the group synchronization cache.

The project is now available for translation at: https://translatewiki.net/w/i.php?title=Special:Translate&group=wikidata-lexeme-forms

I've mentioned the project and translation licenses separately on the project page.

In T272243#6892077, @LucasWerkmeister wrote:

Alright, done in R2362:72c16b93d68a: Fix ku and tg language codes for translatewiki.net.

@LucasWerkmeister Ah, thanks for bringing that up. We can use a language codeMap like this: https://github.com/wikimedia/translatewiki/blob/master/groups/Pywikibot/Pywikibot.yaml#L11 to handle it

@LucasWerkmeister - We are a go from our side once you merge i18n branch to the main branch.

Related patch is merged and tranfserbot is now available for translation on translatewiki.net: https://translatewiki.net/wiki/Special:Translate?action=translate&group=out-pywikipedia-transferbot

In T47096#6888462, @Tacsipacsi wrote:

Is it possible to make this option checked by default for pages being marked for translation for the first time, but unchecked for pages being re-marked? The risk of breaking things is quite low in case of a newly translatable template, it’s high only for templates already in use. This way fewer pages would be left with supportsTransclusion set to false, yet the risk of breaking things would be considerably lower.

In T47096#6866085, @Tacsipacsi wrote:

Issue: translation aware transclusion is checked by default on Special:PageTranslation for legacy pages (not marked for translation since the deployment of this change). This will inevitably lead to accidentally breaking things, it should be unchecked by default.

We've received the invite. Niklas has permissions to accept invites, but he is currently on leave. Let's wait till 8th March, 2021.

Some documentation related to file formats is present here: https://www.mediawiki.org/wiki/Help:Extension:Translate/File_format_support#Supported_file_formats

@LucasWerkmeister

1. Thanks, this is good to start with. Hypens are preferred but translatewiki handles underscores as well.
2. We would still need push access to the repo. The bot can push to the twn branch, and create a PR to the main branch. The main branch could be marked as protected.

@LucasWerkmeister I've added some concerns, please let me know if they make sense.

@LucasWerkmeister - Apologies for the delay, I will take a look at this today or tomorrow.