In T239084#6868454, @MMiller_WMF wrote:

@Amire80 -- thank you for your attention to our copy, and sorry this slipped through the cracks. Did you abandon the patch because it had been waiting too long?

You did, of course, and I missed it :)

pap-aw is probably OK, but can you please specify what kind of information do you plan to add in this language? Lexemes, labels, values, etc.?

Actually no, a moment.

Let's do nan-hani and see how it works.

In T275389#6848833, @KartikMistry wrote:

In T275389#6848765, @Amire80 wrote:

Of course it's a bug. It's not actually possible to translate from them, so they must not appear in the list. It's not the most urgent thing or a deployment blocker, but should be addressed some time soon nevertheless.

Only solution right now is to add cxserver configuration only after Wikipedia is actually created Or T271809 is done.

Of course it's a bug. It's not actually possible to translate from them, so they must not appear in the list. It's not the most urgent thing or a deployment blocker, but should be addressed some time soon nevertheless.

Pull request: https://github.com/WikipediaLibrary/TWLight/pull/621

There is demand for this also in the Arabic Wikipedia (discussion). I updated added the description accordingly.

A bit of background: this comes after a discussion on Telegram, where I wondered by should ms-arab be used and not ms-x-Q83942, which already works. What convinced me that ms-arab is better is this response by @Mahir256:

As far as script codes for ms go, the use of the established "arab" subtag would be unambiguous in its reference to Jawi. If the official script code weren't distinguishing enough, then we would have reason to retain the private use code (and even then, BCP47 would allow us to tack on private use subtags to existing composed codes, so the use of arab would still not be entirely eliminated in that case)

OK, this can be added.

OK to add it.

Is anyone adding these codes? @Mbch331

Simply moving the messages in en.json and qqq.json is enough. Everything else will be done by translatewiki scripts.

Leave it open. It's probably not going to be removed entirely, but at the moment it does have several important bugs, and this task here has good documentation of these. I'll open new tasks separately soon (like, within a month), and close this one.

OK, got it. Go for it.

Sure, but why? Why not $1, for example?

It's legit, but it's on the way to being supported in core MediaWiki, do adding it for lexemes will soon become redundant. Just complete the Most Used messages in translatewiki, and you'll get it.

Thanks a lot for the detailed explanation!

In T272243#6754478, @Nikerabbit wrote:

I think it would make sense to limit translations into new languages on translatewiki.net

We can set the list of allowed languages in the message group configuration. The question would be how to keep it up to date. Would you be willing to submit patches to add languages?

The languages are probably legit, but is there anyone who actually knows them and plans to add lexemes in them?

I can't speak for the whole Language committee, but as far as I can tell, both issues are just a technicality.

Related? - T243250

Not sure where is the good place to put my feedback of this kind... I'll put it here as a comment, but if there's a better place let me know.

Should these be codes? Can't they be just spelling variants, as it is done for Hebrew?

With a bit of work, syl in the Sylheti script will soon be supported in core MediaWiki, and if it's supported in core, it doesn't have to be added especially for lexemes. Is it very urgent to add lexemes in it already now? If someone knows this language well, I encourage them to complete the translation of the most used messages at https://translatewiki.net/wiki/Special:Translate?filter=%21translated&action=translate&language=syl&group=core-0-mostused . It should take just a few days with some dedication. Let me know if I can help with that. The Tyap language (kcg) translators completed the most used messages from 0 to 100% in less than a month recently :)

In T270202#6742054, @alexhollender wrote:

• text should say "Search for pages containing [x]", currently it says "containing [x]" -- *where are we at with this?

Yes, all the previous ones are fixed.

And another one:

In T6547#6734367, @Bouzinac wrote:

Hello, I don't know if it's the right topic here but if someone has a nice template in xxwiki, how to make it crosswiki ?
For instance, I have a frwiki template, it has a LangSwitch to help show custom text for each wiki. So that if I modify something in frwiki, I can just copy paste among wikis and basta. But someone did not like that and consider enwiki as the sole and unique wiki that shouldn't be international.... So is there another way to have "international" template?

These are fine.

I had already announced it, and the most prominent contributor supports: https://ts.wikipedia.org/wiki/Wikipedia:Community_Portal/Archive-6#Community_Response

Thanks :)

Thanks again for the detailed explanation!

I'm not saying anything about how urgent this is. As long as we're in agreement that the current user experience is sub-optimal, the product manager can prioritize this in any way that seems right :)

Thanks a lot for the detailed descriptions!

... Here are two more messages that appear to have the same problem:

In T228745#6714509, @Exec8 wrote:

In T228745#6714459, @Amire80 wrote:

In T228745#6714448, @Exec8 wrote:

This applies to incubator projects that have a total of at least 10kB in total size and 10 unique pages and was approved as an incubator project by the language committee. This is regardless if the incubator project is 4 days or 14 years inactive/ dormant/ active in incubator.

I'm not sure where are these numbers coming from :)

If you're talking about migrating from the current incubator to the new proposed sites, it's unlikely that inactive sites with just 10 pages will be migrated. Certainly not among the first ones. It's a question of language committee policy details, but I imagine that the first sites to migrate from the current incubator to the new autonomous wikis will be those that have some actual activity. The abandoned Incubators with few pages and no editors will probably wait until people who know these languages come to revive them.

For example, Hiligaynon Wikipedia, https://incubator.wikimedia.org/wiki/Category:Wp/hil . It is 1800+ number of articles. Much activity happened in 2014 by yours truly but got dormant again.

In T228745#6714448, @Exec8 wrote:

This applies to incubator projects that have a total of at least 10kB in total size and 10 unique pages and was approved as an incubator project by the language committee. This is regardless if the incubator project is 4 days or 14 years inactive/ dormant/ active in incubator.

In T228745#6712680, @Krinkle wrote:

I think overall these requirements make a lot of sense.

It happens on the level of the account, not on the level of the software you use to make edits. The Red_Khan_Bot must be added to the bots group, and then all its edits will be marked as bot edits, whether you make them using pywikibot or the usual interactive editing interface.