This task has been marked as resolved, so now what about T188859? Will this information be available on https://stats.wikimedia.org/v2/#/all-projects?

@Prod do you plan to start a review for your extension?

Petit aparte sur le Logoscope comme ça fait longtemps qu'on a pas eu de contact avec le Logoscope. Il me semble que cette discussion de janvier 2018 raconte les dernières nouvelles sur le partenariat Wiktionnaire / Logoscope. En résumé, je crois que Logoscope était en train de réécrire son parser ce qui devait permettre d'augmenter les journaux étudiés. Je crois qu'ils n'ont pas mis leur fichier de données à jour depuis septembre 2018. Du côté Wiktionnaire, on cherchait le meilleur moyen de profiter et d'afficher leur données. J'avais proposé le modèle Logoscope mais il restait encore des dicussions (voir le lien vers la Wikidémie) pour un déploiement à grand echelle. Donc pour les recontacter, pourquoi pas mais je n'ai pas grand chose de nouveau à leur proposer de notre côté et je trouve ça dommage.

Pour info, Module:cas existe déjà. Il reste maintenant à voir comment on veut l'utiliser précisément. Par exemple, est ce qu'on l'utilise uniquement sur la ligne de forme ? Ou aussi dans els tableaux de déclinaisons. Ailleurs ?

During the Wikiconvention francophone 2019, it has been proposed not to limit the place of learning to only one. For some users, it may be relevant to set several places of learning for a given language.

For your information, here is what I see, when I try to edit the main page

In T231026#5435306, @Nikerabbit wrote:

That page uses action=edit API module. Translate itself does not check for such permissions. Can you edit the page directly by clicking the title dropdown and choosing Show in wikieditor?

In T231234#5439338, @Isarra wrote:

Should we just put the languages back in the sidebar? In retrospect, I'm not actually sure this (moving it out) was such a great idea...

Waiting that this feature be implemented, it is already possible to "delete" a pronunciation during the "Recording" step. To do so, you can simply press the "Del" button, so that the pronunciation is deleted and you can re-record it directly.
That's said, I agree that this shortcut should be documented somewhere.

Hmmm, it is weird, I am not able to reproduce anymore. I was using Firefox ESR 60.0.8. The page was stable (I could scroll and see this effect) but when I reloaded the page, the bug dissapeared. So maybe it was a cache issue or something similar.

Oops, sorry for the noise. Thank you very much for the investigation of our problem. We will fix it on our wiki.

Just to be clear, we have two link: "Edit" and "Edit source". Clicking on "Edit" or "Edit source" beside a section always opens the Visual Editor (I expect that clicking on "Edit source" opens the wikicode editor). However, if one clicks on "Edit" in the tab on the top of the page, it will open the Visual Editor (as expected) and clicking on "Edit source" will open the wikicode editor (as expected).

In T212843#4912902, @deryckchan wrote:

This will address migration blocks like https://www.wikidata.org/wiki/Wikidata:Properties_for_deletion#Property:P2521, where the lack of a feature to call Lexemes in Wikipedias is blocking the migration of a property.

For the French Wiktionary, I do not know what will decide the community but if we decide one day to use the Lexeme data from Wikidata, it will be the most probably for the Forms (conjugation, inflection, declension, etc). I think we will never use the Senses. So what Mike Peel proposed just before makes sense for a full flexibility.

Indeed for the second point, it is indicated on P443 (Constrain section) that the lexeme has to be excluded (it makes sense). So Lingua Libre Bot should not add P407. That's said, it is not clear why the exclamation mark appears in Strom.

Not sure it should be marked as resolved because I do not see any new taks titled "[EPIC] Find best strategy for Visual Edidor Wiktionary configuration" or similar. This task should be opened first and linked to this task before closing this one.

For now, I have replaced "fr:Gwendoline Daudet" by "fr:Gwendoline_Daudet" and the link is now ok. But the problem remains.

There is some improvements on this. I do not see any issue anymore. Is it fixed?

With another property (P6614), I experienced a similar issue yesterday

Actually I just tried using Firefox 66.0 on Mageia Linux 64-bits and it worked. So it seems the problem occur sometimes, probably on some webbrowsers.

Indeed, the color is now there. Thanks

Not sure this issue is resolved. I still do not see the icon in red and blue (they remain grey).

In T217883#5011550, @Krenair wrote:

In T217883#5011518, @Aklapper wrote:

In T217883#5011452, @Pamputt wrote:

It means for everyone except logged-in user that have changed the skin in their preference.

@Pamputt: What does "changed the skin in their preference" mean exactly? Do you propose to overwrite the skin setting of every account that has set "Vector" as their skin on https://fr.wiktionary.org/wiki/Spécial:Préférences#mw-prefsection-rendering ? Wouldn't that mean that a lot of people would log in and suddenly see a completely different user interface without knowing why and not necessarily knowing how to revert (if they wanted), even those people who intentionally chose to prefer Vector over other skins? (Note that the Preferences unfortunately does not offer a "Use default skin" setting; you explicitly have to choose a skin...)

Pretty sure they're saying that everyone who hasn't selected a particular skin in preferences already would now get timeless, just they'd be able to change by going to preferences.

In T217883#5010779, @Aklapper wrote:

What does "default" mean? Logged-in users? Anonymous users? New logged-in users?

Another example in the Preferences menu, the banne "Lingua Libre is in open beta. Be aware that bugs can still occur. Please share your feedback here !" appears in English while all the rest of the interface is in French (in my case).

@Spinster, does what 0x010C proposes solve your problem? Can we close this task?

This is how I experience this problem