If this ticket is going to be closed, which ticket covers showing the language names in the dropdown?
Tue, Feb 23
Thu, Feb 18
Tue, Feb 16
I'm closing this again because the issue I reported here is fixed - the language code dag is now accepted for lexemes.
Since the language dropdown for lexeme senses uses the same list, that has the same problem. The codes I mentioned in #6753045 don't show up, nor do any lexeme-specific languages like ctg, fro, nrf-je, az-cyrl.
Fri, Feb 12
It's working now \o/ https://www.wikidata.org/w/index.php?diff=1359422326&oldid=765503160
Thu, Feb 11
Wed, Feb 3
Sat, Jan 30
And another: reading pattern of Han character should be qualifier on items and main value on forms, not main value or qualifier everywhere.
Thu, Jan 28
To reproduce this, increase the font-size of the html element. The screenshots below are with the font-size set to 250%.
This seems to already be possible? e.g. https://www.wikidata.org/wiki/Special:NewLexeme?lexeme-language=Q1&lemma-language=mis&lemma=test&lexicalcategory=Q2
Wed, Jan 27
I've noticed this too. I can reproduce it in a desktop browser too with a simple query like https://query.wikidata.org/#select%20%2a%20%7B%20%3Fa%20%3Fb%20%3Fc%20%7D%20limit%2010 and telling the devtools to display it as mobile, or by making the window too narrow for the text in some other way (make the browser window smaller and/or zoom in/increase the font size).
Jan 23 2021
Jan 22 2021
I don't think language fallback explains the behaviour I'm seeing here since I was using English at the time I originally reported this (I switched to British English more recently). But now that you mentioned it, I just tried switching back to English and searching for "singu" is actually still failing when the UI language is set to English, even though it works for British English and the item has the same label for both. "sg" and "nt" don't work even when the language is set to English.
"singu" is now working for some reason, but "sg" and "nt" still don't
Replacing links with buttons would be one way to fix T250519
Could you turn the documentation pages you mean into links? :)
There are multiple romanisation systems for Japanese and the current ja-x-Q53979348 lemmas are a mixture of them, so I think statements on forms (Revised Hepburn romanisation for Revised Hepburn, transliteration for other systems) are more appropriate than adding ja-latn.
Jan 21 2021
And the next one: transliteration has some constraints for what type of items it can be used on. Those constraints apply to usage on items and do not make sense applied to lexemes. Since I can't restrict those constraints to items, the only way I could resolve the constraint violations they were creating was to remove the constraints entirely.
Jan 20 2021
Jan 19 2021
Jan 18 2021
The way it's designed to work, codes which are added for labels are automatically available for monolingual text and lexemes too, but codes which have been added for monolingual text have to be added for lexemes separately (and vice versa). So, looking at the dates, I don't think it's related since that ticket is from before dag was added for labels. Back then it was working the way it was designed to, now it isn't.
Jan 17 2021
Jan 16 2021
I noticed that the dropdown is the same one used for monolingual text languages and - indeed - the one for monolingual text has the same problem with the language code not being detected on middle click paste. Although, thankfully, it's much less destructive there, since it mostly doesn't allow saving when it thinks a field is empty.
There are even a bunch of languages we can add labels for which don't show up in the list, despite not being explicitly excluded, e.g. aa, cho, dag, es-419, ho, hz, ng, rn, shi-latn, uz-cyrl, uz-latn...
In the interest of not having this stalled indefinitely, I've removed the request for az-arab from this ticket.
Jan 15 2021
It can also cause existing glosses to be deleted if you try to change the language:
This just happened to me with nrf-je which is one of the language codes which doesn't appear in the dropdown at all, so there's no distinction between a successfully detected language code and one where it will silently discard your new gloss. :(
Jan 13 2021
This is not a duplicate of T89213. The lemma should always be displayed. It's a bug that it depends on successful language fallback, because it shouldn't depend on language fallback in the first place.
Jan 12 2021
Jan 8 2021
Jan 5 2021
I spent far too long this morning confused by these edits:
Jan 4 2021
Jan 3 2021
Jan 1 2021
This is also a problem for monolingual text statements, lemmas, forms and senses.
Dec 30 2020
Next example: Pinyin transliteration should have a property scope of qualifier on items and lexemes and main property on forms. Since we can't do that, it now says the scope is main property or qualifier everywhere.
Dec 29 2020
This could potentially be useful for old URLs too: We could display URLs in outdated statements differently from those in normal/preferred rank statements.
Dec 28 2020
Dec 25 2020
Dec 23 2020
I think it would be useful to see some examples of how these would be used/what they would be used for.
Dec 18 2020
Dec 17 2020
Yay! Looks good \o/
Dec 9 2020
Should we exclude certain entity types or include? So should we have a allow or deny list?
Dec 7 2020
Since the whitespace gets stripped when saving anyway, would removing the trim()s from https://gerrit.wikimedia.org/g/mediawiki/extensions/WikibaseLexeme/+/0e48721161973149c18fa7539b22ed1f6b13cb7f/resources/templates/glossWidget.vue.html#38
https://gerrit.wikimedia.org/g/mediawiki/extensions/WikibaseLexeme/+/0e48721161973149c18fa7539b22ed1f6b13cb7f/resources/templates/lemma.vue.html#25 and I think https://gerrit.wikimedia.org/g/mediawiki/extensions/WikibaseLexeme/+/0e48721161973149c18fa7539b22ed1f6b13cb7f/resources/store/actions.js#33 fix this?
Dec 1 2020
There were 10 lexemes in the 2020-11-27 lexeme dump which I've also fixed. They came from two users, Jacek Janowski and Tokyo Akademia, which was the case for most of the previous ones I fixed too.
Nov 25 2020
Nov 24 2020
The vast majority of the time people use Q, people are presumably copying the ID from the item page. I just fixed all the ones which had q, but I'll have to wait until the next lexeme dump to find out if I got them all (or if any new ones appeared).
Nov 13 2020
Nov 5 2020
Nov 3 2020
It also affects <title>
Nov 2 2020
Nov 1 2020
T137810 had an extremely negative effect on me and I have no desire to get dragged back into that argument, sorry.
Oct 31 2020
Oct 29 2020
Oct 26 2020
Oct 22 2020
I've run into this twice today already. :(
Oct 19 2020
Oct 18 2020
Oct 17 2020
Oct 12 2020
Note that we already use sr-ec and sr-el for terms (see language stats). The problem here is not that the codes are missing, it's that adding those codes to your Babel box does not cause them to appear in the term box.