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.

Ideally we should have : label, language code and lexical category. For instance « gwez (br, noun, L62) » for Lexeme:L62 (or any other presentation and order as long as the informations are here).
This is important because the same lemma often exist in multiple languages and even inside one language, the same lemma can have different category. For instance, "best" in English could be an adjective, an adverb, a noun, and a verb, so at least 4 lexemes, if I understand correctly).

Same problem in other languages :

• French https://www.wikidata.org/wiki/Lexeme:L1?uselang=fr "sumérien" instead of "sumérien"
• Spanish https://www.wikidata.org/wiki/Lexeme:L2?uselang=es "inglés" for "Inglés"
• Catalan https://www.wikidata.org/wiki/Lexeme:L2?uselang=ca "anglès" for "anglès"

etc.

In T195258#4221900, @VIGNERON wrote:

New development, today, on the Status updates I see the same kind of bug (columns given are not what is asked on the SELECT) but on the online result itself (so before export) : query

New development, today, on the Status updates I see the same kind of bug (columns given are not what is asked on the SELECT) but on the online result itself (so before export) : query

It shoud be but can someone check all the points on the checklist?

Not sure if it's already there, the gerrit link seems to be for eu.wikiquote.org not eu.wikisource.org (or am I reading it wrong?)

In T188722#4020638, @Liuxinyu970226 wrote:

Shouldn't we also remove mo from supported monolingual language codes?

I agree this should be removed.
Links, label and description maybe could be kept, but at least doing a interwiki sitelink to a wiki that doesn't exists should not be possible.

In T178957#3921771, @Theklan wrote:

That can happen today. I can upload a photo to the spanish contest and a different one to the french contest. If they are good enough, I would have two photos in the international contest.

Here my thoughts on you thoughts ;)

@Theklan: I totally agree that the country criteria is not a good idea (especially as 'country' can be quite polysemic). And I agree that the Basque UG did a good job during WLM 2017 and that WLM should grow on that.

@Llywelyn2000 sorry to be blunt, but threatening is a low, non-contructive and antagonizing move and an alternative competition is a bad idea too (unless if you aim for mutual destruction) especially as no-one rejected the idea of including Wales (or any other area for that matter) in WLM 2018.

Yes, thank you a lot!

An other view on this problem: http://tinyurl.com/ybrhd82y (request tweeted by Lucas today)

So... The other way round now:

• if it's only for Earth, should it *not* give results on other places ?

In T175578#3596967, @Lucas_Werkmeister_WMDE wrote:

is it conventional to give them in range [0°, 360°) instead of [-180°, +180°) on bodies other than Earth?

Thanks @Effeietsanders for these two sources, can someone (@Bachounda ?) confirm what I guess :

• the second source is about « Monuments, sites et zones classés "patrimoine national" » which seems to be the same as the list we want
• the first source is much wider, all the inventory (most of them not being protected), not sure if we want all of that in the list or not

I found two list that I restored and moved on subpages of the Project:Maroc :

• https://fr.wikipedia.org/wiki/Projet:Maroc/Liste_des_monuments_class%C3%A9s_du_Maroc
• https://fr.wikipedia.org/wiki/Projet:Maroc/Liste_des_monuments_class%C3%A9s_de_la_province_d%E2%80%99Errachidia

@Mbch331 could you please elaborate?

Maybe it can help add a column with a photo in https://wikimania2017.wikimedia.org/wiki/Template:Attendees/100 ?

In T165228#3285744, @abian wrote:

Definitely resolved. Thank you.

@Smalyshev in my case, I tried several queries on Ubuntu and Windows, with Chrome and Firefox and for every option (JSON TSV, CSV, verbose or not), but always opened with LibreOffice Calc (version: 5.1.6.2), the problem is always the same.

I've tried several encodings, including all the ISO-8859 (from ISO-8859-1 to ISO-8859-15) but none seems to match the encoding used...

True it's very weird. I didn't really expected it to works, but it does works in table mode, why not in line chart mode too?

Idée (à la con ?) : et pourquoi pas quelq'un du conseil scientifique ? Je pense en particulier à Dominique Cardon ou à Louise Merzeau dont j'ai déjà pu apprécié les interventions (par exemple celle-ci ).

Vote en cours sur cette page Meta

Maybe unrelated but this request's result is quite strange too...

Je suis hyper-fan des autocollants hexagonaux ! (et Sarah aussi visiblement)