There is also T180771 which requests this code (plus several others) to be added as a monolingual code. Until there's final approval there, this one has to wait.

@Lucas_Werkmeister_WMDE There is also https://gerrit.wikimedia.org/r/663943 which gerritbot somehow doesn't want to link to this ticket.

@noarave There is also https://gerrit.wikimedia.org/r/663943 which gerritbot somehow doesn't want to link to this ticket.

There is also https://gerrit.wikimedia.org/r/663943 which gerritbot somehow doesn't want to link to this ticket.

In T263946#6825859, @Amire80 wrote:

Is anyone adding these codes? @Mbch331

Probably also resolved with T267927.

URL formaat hiervoor is: https://www.google.com/searchbyimage?image_url=<wikiportret afbeeldingsurl>&q=<titel>

Browsers tonen niet standaard de metadata van een afbeelding. Dus met rechtsklik -> afbeeldingsinformatie zie je de metadata niet.
Daar is een extensie voor nodig.
Ik zal kijken of ik de info uit de afbeelding kan halen en kan weergeven op Wikiportret (zal in een ingeklapt blok zijn, omdat het best veel informatie zal zijn).

In T223782#6789547, @Halfak wrote:

It looks like we're getting very decent fitness. I think we can do a lot more with targeting features of articles. E.g. does nlwiki use infoboxes? Are there cleanup templates we can look for that would suggest quality issues? Anyway, we can leave that for follow-up work.

We're not fans of adding a lot of cleanup templates.
Most common are Wikify (to mark an entiry article needs clean up, but no need to remove it), Twijfel (there is doubt about the article) and Bron? (citation needed), and Wanneer? (when did the claim happen?)
And yes, we do use infoboxes see https://nl.wikipedia.org/wiki/Categorie:Wikipedia:Sjablonen_infobox and subcategories.

Another deletion that still shows up: Q105098078
It was deleted January 29th at 8:55 AM CET (= 7:55 AM UTC)

Q104982840 which was deleted January 27th 08:48 CET still shows up in my query for invalid P2397 values

Based on Amir's comment this is not done for now.

@Amire80 @jhsoby What do you say?

Same goes for Q104864462 and Q104839853.

In T272442#6765137, @Amire80 wrote:

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

@Amire80 @jhsoby What do you say?

@Amire80 @jhsoby What do you say?

@Darwinius Where do you want to use them? Monolingual text properties, Lexemes and/or labels, aliases and descriptions?

If you want to use it for labels, descriptions and aliases (as you mention in your examples), then adding it as a monolingual language isn't the solution. It needs to be added as a termbox language.
@Amire80 @jhsoby Is the language acceptable as a termbox language?

In T180771#6719463, @Nikki wrote:

In T180771#6715965, @Ladsgroup wrote:

@Mbch331 Does langcom approve this patch then? https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/555688/

Shouldn't they be lowercase for consistency?

In T180771#6715965, @Ladsgroup wrote:

@Mbch331 Does langcom approve this patch then? https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/555688/

@Amire80 Are all languages accepted or just nan-hani?

@Amire80 @jhsoby What do you say?

In T180345#6458503, @jhsoby wrote:

These seem reasonable to me, but I'd like to see if @Amire80 has any comments.

@ObyEzeilo Please explain what you mean with adding Igbo language to Wikidata.

In T128078#6703843, @Peter_James wrote:

Slashes are still converted to %2F in UK Parliament thesaurus ID (https://www.wikidata.org/wiki/Property:P4527). The formatter is http://explore.data.parliament.uk/?endpoint=terms/$1

The url generated by Wikidata is: http://explore.data.parliament.uk/?endpoint=terms/8193 this gets redirected to https and then it's changed to %2F.
Solution is to prevent the redirect by changing the formatter url

@Amire80 What should we do with this language? Add oj or the different languages on SIL?

@Amire80 @jhsoby What do you say about adding this language code?

@jhsoby @Amire80 Are these languages also acceptable for Lexemes?

@jhsoby @Amire80 What do you say about adding this language?

@Loominade Monolingual codes aren't used for Lexemes. Request is to add them for Lexemes. I'll rename the ticket.
@Amire80 @jhsoby What do you say?

In T195816#6618501, @Loominade wrote:

@Okkn what about Japanese written in latin?

Wikidata item: https://www.wikidata.org/wiki/Q53979348
IETF: ja-Latn

In T212313#6611342, @Aklapper wrote:

How to get feedback from LangCom on this task? Are there any contact workflows that the task author should follow?

@Amire80 @jhsoby What's your opinion?

@Amire80 @jhsoby What's your opinion?

It was merged last Wednesday, so it should be available somewhere this Thursday (after new code has been deployed to Wikidata)

In T265782#6598198, @Lucas_Werkmeister_WMDE wrote:

Moving back to TODO because, uh, I think we forgot to do the part that the task asks for? As far as I can tell (ignoring the unfortunately misleading commit messages), the attached changes added non-runr for lexemes and for monolingual text, and also taught cldr the language name, but non is still not available for lexemes. (Beta concurs btw.)

In T265906#6560598, @Amire80 wrote:

az-cyrl is OK.

For Arabic script we already have azb. Is az-arab any different?

Ping @Bugreporter Is this request for all Mixtec languages or just for Mixtepec Mixtec?

In T180345#6458503, @jhsoby wrote:

These seem reasonable to me, but I'd like to see if @Amire80 has any comments.