@Manuel: The term termbox languages means Labels/Aliases/Descriptions. When added, they are also available for Monolingual properties. They won't become available for Lexemes on the other hand.

In T236938#7668702, @Robin_van_der_Vliet wrote:

In T236938#7659542, @jhsoby wrote:

As Toki Pona is well-attested and seems to have quite some traction, I (as a LangCom member) support adding it for both lexemes and monolingual.

What is the next step in getting support for Toki Pona added? The previously mentioned pull request already got merged.

@Amire80 @jhsoby What do you say?

@Nikki What is the autonym for this language? Because I need to know this to add the language to InitialiseSettings.php (see T277836)

In T293884#7467903, @Lucas_Werkmeister_WMDE wrote:

In Wikibase, yes, but @Mbch331’s changes also add the language to wmgExtraLanguageNames, where the autonym is included. (Eventually we’ll hopefully get rid of that – see T273627 – but depending on where the autonym is used, maybe we’ll add the autonyms to the Wikibase config. I’m not sure.)

In T290857#7349128, @Lyokoi wrote:

There is a very big problem to need a languages codes. There is so many languages without it AND it’s always little language used by minorities. It’s terribly difficult to help, describe and write in these language here, when it shouldn't.

But is there a real use case for monolingual properties in those languages? If there's only a one time use, then you should use mis (miscellaneous), because changing the code so minority languages can be used will make this a significant change.
If there are valid use cases then please provide them, so WMDE can make a better judgment if it's worth changing the code to make this possible.

Besides langcom approval, we also need language codes. So far only Gallo has been provided.

In T287243#7346795, @Esc3300 wrote:

From T263946 it looks like it followed the usual process for new codes for Wikidata. Also it was tested/marked as resolved by WMDE staff.

@Esc3300 LocalNamesEn.php is part of CLDR. That's not a WMDE extension.
The corresponding change was approved by @Raymond and not WMDE

It's not the query service gui that adds the +
When you use the bigdata interface the + gets added as well.

The problem is that the + gets encoded again. It becomes %2B

In T288799#7281405, @Aklapper wrote:

Thanks for taking the time to report this. Could someone please explain where to see a "Patrol button" in the screenshots, and provide links where someone else can see a problem? @Jonathan5566: Please see https://www.mediawiki.org/wiki/How_to_report_a_bug - thanks!

@jhsoby @Amire80; What do you say?

@Eugene233 When requesting new languages always specify what you want to use them for: Monolingual properties or Lexemes or Labels/Description/Aliases as the developer needs to know where to add them in the code.
If you want to use the language outside Wikidata, you need to contact LangCom (not via Phabricator) what you need to do to get the language added for use on all Wikimedia projects.

In T180771#7228271, @Esc3300 wrote:

Seems to be live, at least nan-hani

@Amire80 @jhsoby @Esc3300 @Nikki Could you please reach an agreement on what the desired language code is going to be? I'll make a new patch then.

In T155419#7195690, @Amire80 wrote:

I think the discussion here becomes more complex than it should be. How many labels do we actually expect to have here? If we just start with "mix", and then we get a lot of them, can they be later divided by someone who understands these languages well?

In T286031#7220116, @Esc3300 wrote:

@Mbch331 can you review the patch?

@Amire80 @jhsoby Now we have en-us, is this acceptable too?

In T286862#7219730, @Aklapper wrote:

@Bugreporter: Add where? Which codebase is this about?

In T286031#7193481, @Esc3300 wrote:

It's actually missing in LocalNamesEn which probably explains why we get the Spanish version.

@Amire80 What's your view on this?

In T215032#7200368, @Amire80 wrote:

@Mbch331, I see mvf in the code of WikibaseLexeme, but I cannot actually add lexemes in it. And I don't see it in the code of Wikibase at all. Can you add it please?

@Amire80 @jhsoby What's your view on this?

In T70207#7195691, @Esc3300 wrote:

I'd close this (as incomplete or invalid), it seems to be a pre-phabricator request and https://en.wikipedia.org/wiki/User:Geekemad doesn't exist.

In T180771#7191533, @Addshore wrote:

As the current Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)) unstaller, what is this task stalled on?

This is blocked on LangCom approval for the remaining languages.

In T284808#7183772, @Lydia_Pintscher wrote:

Don't we already have this? I don't think we allow adding terms for simple for example? Or am I missing something?

@Esc3300 My patch was denied for 2 reasons:

1. I used da instead of nl (which has been fixed)
2. There is not enough proof of consensus in this task (this is something I can't fix.

Added missing translations. Language codes that are present in CLDR need to be updated upstream, language codes not present in CLDR can be added to LocalNamesNl.php

Since there is only approval for mix in case of Mixtepec Mixtec and no approval for mix-und, this isn't ready to go. Still needs LangCom approval. @jhsoby @Amire80 is mix-und a good alternative for this case where it's unknown which form of Mixtec is used?

In T262922#7178793, @Bouzinac wrote:

Another wonder : monolingual language code does not necessarily mean there would be a new line "gsw-fr" as labels for items, does it?

No. It's only available for monolingual properties. Labels/aliases/descriptions aren't properties and thus not supported. If it's needed, a new ticket is needed for that.

In T215032#7167462, @Popolon wrote:

Which kind of sample do you want.

As an exemplle, from :
https://fr.wikipedia.org/wiki/Mongol_bitchig

{{lang|cmg-Mon|ᠮᠣᠩᠭᠣᠯ ᠪᠢᠴᠢᠭ}} this is the name of the Mongolian script in classical and modern Mongolian.

In T245927#7164813, @Esc3300 wrote:

I updated the task for LocalNamesRu.php and added the usual one week for patches as due dates. It may still be fixed/communicated to CLDR as well.

In T157809#7164833, @Esc3300 wrote:

seems to be ready to go. I add the usual one week for patches as "due date".

In T285076#7164682, @Esc3300 wrote:

If I understand correctly, T162406 is about CLDR. Ideally, all these changes should eventually be in upstream CLDR and not in local MediaWiki code.

It's about LocalNamesSco.php only.

Ideally these changes should be added to Cldr

@jhsoby @Amire80: What do you say?

In T284276#7160260, @Esc3300 wrote:

In T280774#7153111, @Esc3300 wrote:

Can we add it to the Wikidata's sitewide css?

In T262922#7153044, @Esc3300 wrote:

@Mbch331 Thanks. Would you add the language names as well (see description) or is this already done?

Language name is correct in CLDR (in LocalNamesEn.php).

Not used for Lexemes, but added as a monolingual language code. Will remove it there.

Since this was created by a langcom member, I assume this can be considered as approved by LangCom

@jhsoby @Amire80 What do you say?

Looks like the language dropdown is using ULS and not the monolingual language dropdowns from Wikidata. So this is more for the SDC team and not for the Language codes team.

I think the list of disallowed languages can be something like:

In T44396#7150835, @Esc3300 wrote:

Is there a blacklist feature or would that need to be created?

! In T44396#7150849, @Esc3300 wrote:

@Mbch331 what do you think?

In T157809#7150763, @Esc3300 wrote:

LocalNames/LocalNamesDa.php hasn't been created yet

In T212313#7150692, @Esc3300 wrote:

In T212313#6611768, @Nirmos wrote:

What system message would be different in Indian English compared to British English?

Can we have en-in for labels/descriptions without having it as an interface language?

In T284276#7148337, @Esc3300 wrote:

Well, test is after deployment (i.e. ensure it actually works). Ideally this is done by the person who requested the new code.

In T284276#7148299, @Esc3300 wrote:

Which steps can run parallel ?

I think there are two possibilities:

• steps that can't technically done in parallel
• steps that can technically be done in parallel

For the later, there may be reasons to do them before or after some step. Obviously, it doesn't mean they have to be done in parallel.

Current estimate for the entire process seems to be 5 weeks (if you are available). This seems a lot for a somewhat basic task even for the volunteer part of our organization.

Which steps can run parallel ?