Clearly importing *all* languages (lato sensu) from Wikidata doesn't seems to be a good idea. But on the other hand, it would make sense to import some "important" missing languages. Between 600 and 10 000, there is probably a sensible middle-ground.

I change the task a bit. This kind of tool in called a generator (see Help:Create a new generator on lingualibre).

@Theklan : in the third screen of the RecordWizard, you have a box at the bottom right called ExternalTools.
This tool allows to add a SPARQL query, for instance a query on Lexemes.
It's not 100% direct but I think it's good enough, isn't it ?

Yes, thanks a lot @Poslovitch !

ping @Ladsgroup ?

Yes, the challenge itself is only 2 hours (it's already long enough, I can attest it :P).
I think it's important to prepare some page, explaning the principle of the challenge and a list of people who want to participate.

It looks great

• there was a small typo, I forgot a comma, it is dezhañ, dezhi and not dezhañdezhi
• some inflected forms are quite rare but that is to be expected

+1, I volunteer and I'll be very glad to help reproduce this fun activity.

The history says it was added by @0x010C (https://lingualibre.org/index.php?title=MediaWiki:Common.css&diff=256393&oldid=256389) so I guess we will not know before long...

Yes, we noticed the path inconsistency when upgrading LinguaLibre to Mediawiki 1.35 as it broke some tools (including but not limited to Blazegraph).

FYI, I just created of first short draft for stopwords: https://github.com/belett/Breton_lexicography/blob/main/Stopwords%20br

https://www.wikidata.org/wiki/User:Teester/EntityShape.js is not exactly the tool describe in this task but it's an example of a « simple tool for checking Wikidata »

See also Wikidata:SPARQL_query_service/queries/examples/fr#Requête_de_lexème.

I don't think we really have a tool for that.

The problem came from old corrupted file (File page was still there but not the files themselves).
Once these file were deleted, the error message disappeared.
Maybe there is still some lost files somewhere but I think we can close this task.

Sadly I know the problem, not the solution...

@Yug create lexemes would be very nice but quite difficult. "language + form" is not enough, at least the lexical category is mandatory to create a Lexeme.
Other data are needed to to determine if the lexeme exists and is the same (for instance for cases like "fils" - threads L10371- and "fils" - son L15917 - or "tour" L2330 and "tour" L2331).
How could we solve these problems?

I also think a community consultation is not needed: this is an old historic file that make no sense for most Wikisource.

Yes, the problem is still here and open.

This is a great idea.

I'm copy-pasting/translating some remarks from @Denis_Gagne52 (who in not familiar with Phabricator) on the fr.ws scriptorium.

I can confirm that it seems to be fixed.

Just a quick update, we definitely need the distinction between "ñ" and "n".
It's quite rare but there is some pair of word where the tilde is the only distinction, for instance mañ ("this") and man ("he/she stays" but also "moss").

Maybe we can store the list somewhere online (on a wiki page ? on a pad ? either is good for me) and do a collective review (strike the wrods that are not really stopwords, for instance all the numbers are not really stopwords, there is adverb too I'm not sure we should keep).

I strongly agree.

Hi @Aklapper go on any page on any Wikimedia projects, you'll see that some label are not retrieve and the Wikidata Q identifier (or P identifier) is displayed instead.

Thanks for the merge @Charlotte

@Gehel very true. That said, it won't hurt performances either and what about all the other problems of not being able to stop a query? (I hate when I have to restart my browser and/or computer who froze just because I dumbly forgot to remove a wdt:P279*)

Sorry about the ping then.

Hello, is someone working on this ? Thanks.

More exactly: the code fr-ca works fine (everywhere AFAIK) but for some reason the name "français canadien" doesn't appears on the list (everywhere AFAIK). I think this is a different and separate bug and a new ticket would be more appropriate.

Some precision: apparently (from what I've seen) it appears only in English and French and only for the P195 property.

In T233188#5509703, @MSantos wrote:

Could this changeset delete 2 duplicated nodes be related? https://www.openstreetmap.org/changeset/74624620

In T230767#5456114, @Romaine wrote:

In multiple campaigns people tried to re-enable it, like https://commons.wikimedia.org/w/index.php?title=Campaign:wlm-pt&diff=prev&oldid=363866712

FYI, there is a table at the hackathon working on it right now, at least looking at the first possible obstacle.

And now it seems that http://wikidata.rawgraphs.io/ doesn't work at all any more :/
If it's not temporary then we should probably remove the link altogether :(

It seems to be fixed, isn't it?

Ok, I understand. I was just suggested this as "incubated" wikis is the step just before "small" wikis.

Could I suggest that some people look/work on T212881 ? (not "small wiki" per se, but pre-small wiki ;) )

In T204440#5110497, @GoranSMilovanovic wrote:

@VIGNERON The latest processed dump in Hadoop has a timestamp of 20190204, so February 4th this year I would say.
Q. If you have followed the usage of P380 (Mérimée id), does it seem reasonable to you that the changes since Feb 4. 2019 could have produced a higher overlap with VIAF ID (P214) then what is observed on the dashboard?

Hi, I just tested this new dashboard. The visualisations are great, but I'm more a number cruncher myself.

For the record, last December after https://www.wikidata.org/wiki/Wikidata:Property_proposal/Astronomical_coordinates, I added celestial coordinates on M31: https://www.wikidata.org/wiki/Q2469#P625 (2 months later nobody seems to complain)

Did someone did something?

Indeed, it's a bit strange, without two brackets, it could be

• pizza (Italian: Italian dish)

or

• pizza (Italian / Italian dish)

or

• pizza (Italian dish)^Italian

I think the most important is the lemma, so I would put it first. But I'm not sure on how not mix the gloss and the language:

• Mutter (German, female parent)

Or maybe better:

• Mutter (female parent) (German)

Adding the language would not solve entirely the problem but I think it would be a good thing nonetheless.

I'm guessing that when Lea says Lexemes (with an uppercase L) she thinks of Lexemes in Wikidata (which has been done partially already).

Oh that's strange, it was apparently just a temporary bug. Now It works.

Some of it happened for sure, but probably not all.

Other idea: pass the cursor other and get translations (for people learning a language)

A small story to show why this is important (at least to me) and should be fixed quickly (in my opinion).

On Firefox 60: broken
On Chromium: everything works as expected

Yes, I didn't thought about it but commas should be i18ned "،" for Arabic and Persian, "、" for Chinese and Japanese (and maybe others for other languages but I don't know them, is there a list for i18n comma somewhere?).

In T195740#4248545, @Micru wrote:

@Lea_Lacroix_WMDE Why do we need to use a a list of language codes at all? Why not to do like with units and let the user select any item, and then have it checked with the constraints?

As explained in my prevuious message, I agree we need to specify at least language and script. For the rest (country, orthography reform, ...), I think the best way to store this kind of information is to use property in the lexeme itself. The advantages of the property is it is really flexible and so we can decide a psoteriori what kind of information we want to store in one lexeme.

See too the broader related ticket : T195740

Tough questions.

Yes for a link (I forget about it, shame on me) and yes too, for multiple lexemes (especially "tour"@fr will probably have 3 lexemes with the same features, for the equivalent of "tower"@en, "round"@en and "pottery wheel"@en).

Here is a proposal of what the warning message could look like:

In T195443#4232267, @Aklapper wrote:

Hi, steps to reproduce are welcome.