Please go ahead and give write access to https://github.com/translatewiki/

@Pginer-WMF @Nikerabbit It would be helpful to understand what the click action of the target language category is supposed to achieve. The x button works to remove the item from the list on the target side. On the source language side, we have a click action that selects and adds the category to the target language.

Is it possible to provide more information about this bug? I tried replicating this with Google and MinT. None produced the results in the ticket description.

In T408848#11400188, @abi_ wrote:

@Wangombe Can you update what was done for this ticket in addition to renaming the group in group configuration file?

In T410029#11404406, @Nikerabbit wrote:

QA fail:

We'll be following these steps: https://translatewiki.net/wiki/How_to_drop_a_project

Hello @diegodlh, It's possible to pause translation of the project. In this case, we shall archive it. Once you're ready to resume active maintenance of the project, feel free to create a ticket expressing this interest.

composer install installs the https://github.com/mustangostang/spyc dependency

PR is available on the language-date repository -> https://github.com/wikimedia/language-data/pull/457

Here's a screenshot of the ApiLanguageSearch move

We can move the following files to a new namespace MediaWiki\Language\Data;

Here's a link to Recommendation API dashboard.-> https://logstash.wikimedia.org/app/dashboards#/view/72757f80-b566-11f0-a3ef-75d78f452652?_g=h@0e494b1&_a=h@72903ef

On a high level, there might be technical overhead to implementing keyboard navigation for language variants. We can extend this navigation using key modifiers like Shift + arrow to expand the lists but key combinations also add complexity or hand movements to navigation. Selecting using a mouse pointer would be easier in this case. Just something to think about.

In T407981#11322714, @abi_ wrote:

Looking at the last 1 week data,

I don't see any data in Top hosts, Security Levels -Multi indexed, What are these supposed to show?

For "Top Hosts", the visualization is supposed to show data from host.name in the ECS index. This visualization came from the ECS dashboard.

Changes reflecting the merge of ECS and Logsash dashboards for MinT are reflected in the above link. Will work on Recommendation API next

No obvious issues were found during testing of Special:AutomaticTranslations. All entry points link to the their respective locations and content is rendered correctly in different languages. No errors appear in the console when inspecting the pages during navigation as well. Changing languages is a bit slow but this is a known issue with ULS.

All done.

Please grant https://github.com/translatewiki write access to your repository. These translation updates will be submitted to the main branch of your repository. Should you need to review the translations, we offer ability to create a PR that you can merge at your discretion.

@mkroetzsch Please see this link for information about message documentation as your project lacks qqq.json file. Message documentation allows for messages to be translated with the correct context and consequently allowing for high quality translations delivered to Nemo Web.

@Benoit74 Your project is missing a qqq message documentation file. It's available on translatewiki.net nonetheless. Will you be adding this soon?

Exports happened today.

Please go ahead and grant the https://github.com/translatewiki write access to your repository if you haven't already.

The project seems to be missing message documentation as described here: https://translatewiki.net/wiki/Translating:Localisation_for_developers#Message_documentation. Message documentation provides context to the messages to ensure successful translation. Please see the Wikipedia Android App as an example: https://github.com/wikimedia/apps-android-wikipedia/blob/main/app/src/main/res/values-qq/strings.xml

I managed to verify the fixes made by @abi_

Sent out another comment to try get their attention.

As per my testing, I didn't notice anything else out of the ordinary. Any other issues with Special:AutomaticTranslation noticed can be reported under this ticket.

Left a comment on the PR addressing this: https://github.com/wikimedia/edx-platform/pull/502#issuecomment-3359701651

In T400562#11198852, @abi_ wrote:

Issues noticed in the dashboard:

1. Under ContentTranslation errors, the count of errors in the error feed, and the errors in the frequent errors section + frequency don't match.
2. Same as above for CXserver errors section as well.
3. Under ContentTranslation errors, the heading says: CX Servers error frequency.
4. Recommendation API be updated to Recommendation API errors to match the other headings.

In T404561#11205412, @gerritbot wrote:

Change #1190665 had a related patch set uploaded (by Wangombe; author: Wangombe):

[translatewiki@master] Cite Unseen: create merge requests instead of direct push

https://gerrit.wikimedia.org/r/1190665

To get started with adding configurations for this project, .pot files need to be added to the project along with message documentation as highlighted in this link. Please also see the rest of the page for further guidance on how to get your project ready for localization (in case you haven't already)

https://cxserver.wikimedia.org/v2/?doc - some of the endpoints are not available outside the ContentTranslation. Special:AutomaticTranslations doesn't operate within this scope. As much as some title fetching works, it only does because the default MT in the language pair selected doesn't require and authorization token to begin with. I suspect this is to protect API limits on services like Google translate.

The PR was merged.

We now show the fallback title (source title) and language name the title is in.