Currently the message is set to "optional" on translatewiki.net. Would it make sense to set the message to "ignore", so that no translations could be made? In the consequence all existing "translations" would be removed from the json files. I do not know if this would make any problems.

In T157809#7232455, @Esc3300 wrote:

@Raymond would you have a look?

i18n/ve-wmf/en-gb.json was deleted today: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/705596

In T286679#7220858, @Nikerabbit wrote:

@Raymond any idea why https://github.com/wikimedia/mediawiki-extensions-VisualEditor/blob/master/i18n/ve-wmf/en-gb.json still shows Welsh even though https://translatewiki.net/wiki/MediaWiki:Tag-visualeditor/en-gb has been deleted?

In T286031#7220528, @Esc3300 wrote:

Actually, it wont fix it for labels, as "en-us" doesn't work despite being defined in LocalNamesDe.

• See this addition at https://test.wikidata.org/w/index.php?title=Q149653&uselang=de
• and compare it with that addition to the same

Which gets us back to T261851 about something similar.

In T286031#7220364, @Esc3300 wrote:

I get "español de América Latina" with https://test.wikidata.org/wiki/Q149653?uselang=de or uselang=en

Interesting fact: on https://test.wikidata.org/wiki/Q149653 it works well.

In T286031#7220112, @Esc3300 wrote:

I don't think it's useless and, even if it is, I don't think it's going to break anything.

It may be a problem with languages accepted for Wikidata labels that aren't MW interface languages.

In T286031#7220037, @Esc3300 wrote:

@Raymond That's the language name for monolingual text, a slightly different usecase than the two presented above. Can we try to add the patch to see if it would solve it for these?

In T286031#7219780, @Esc3300 wrote:

@Raymond What do you think ?

In T266345#7188586, @AnneT wrote:

Hi @Raymond, I've opened up patches to cover the process outlined in this comment so we can get these messages migrated from WikibaseMediaInfo to MediaSearch. Some thoughts and questions:

• I think it would be best to first move the messages to MediaSearch, then delete them from WBMI after that's all done, so I think we will need for you to disabling syncing with WBMI temporarily.
• Please let me know if these patches sufficiently cover what you'll need to sync everything with translatewiki.net, or if there's something I could do differently to facilitate this process
• In terms of actually syncing everything and merging these patches: it would probably be best if we could do this all between when one branch is cut and the next, so that all of the work can roll out at once via the train one week. FYI, those of us on the Structured Data team will be unavailable all of next week. Please let me know how you'd like to coordinate this. I'm not sure if you need to merge a patch before syncing to translatewiki.net, and if you'd like to merge the patches yourself or have one of us do it. Either way, I am happy to coordinate that here or on IRC.

Thanks very much for your help!

When exporting mediawiki today:

In T265468#6602634, @Mohammed_Sadat_WMDE wrote:

Make non-controversial change of

1. "und" from "unknown language" to "undetermined language"
2. "Unsupported language" for "mis" to be lowercase ("unsupported language")

as per consensus here.

In T284363#7136147, @Aklapper wrote:

Stalling as this needs upstream changes; please link to the CLDR.unicode.org ticket once created

In T284363#7136012, @TKsdik8900 wrote:

2 comments:

Is this a task that could be handled by WMDE devs who developed the "Two-Column-Edit-Conflict-Merge"?

A lot of reports on de.wiki for misaligned table editig too. i.e. https://de.wikipedia.org/wiki/Wikipedia:Technik/Werkstatt#Tabellenbearbeitung_KAPUTT%21%21%21 and https://de.wikipedia.org/wiki/Wikipedia:Technik/Text/Edit/VisualEditor/R%C3%BCckmeldungen#Visueller_Editor_bei_Tabellen

Any chance that this could be fixed in the near future? It's really annoying to run into the misleading error "wrong input". As I am an experienced user I know what to do (trim by hand) but other people with less experience would give up :-(

In T281702#7053018, @Mbch331 wrote:

In T270377#6975929, @Seb35 wrote:

With the narrowing create=working/exiting=non-working, I remind others had this issue. I found T263928, D3nnis3n had this issue (warning: on the mentionned issue, a lot of people had similar-but-not-exactly-the-same issues and it is difficult to follow, so strictly read D3nnis3n). If I understand correctly, he fixed it using nginx. But perhaps you can try this: T263928#6528000 (the mentionned 403 issue is perhaps/probably because of cookies in a private wiki).

In T266345#7000054, @AnneT wrote:

@Raymond do you have thoughts on Matthias's comment above?