May 11 2022
@Manuel: The term termbox languages means Labels/Aliases/Descriptions. When added, they are also available for Monolingual properties. They won't become available for Lexemes on the other hand.
May 10 2022
Feb 1 2022
Jan 14 2022
Nov 5 2021
Nov 3 2021
Oct 29 2021
Oct 26 2021
Sep 13 2021
But is there a real use case for monolingual properties in those languages? If there's only a one time use, then you should use mis (miscellaneous), because changing the code so minority languages can be used will make this a significant change.
If there are valid use cases then please provide them, so WMDE can make a better judgment if it's worth changing the code to make this possible.
Besides langcom approval, we also need language codes. So far only Gallo has been provided.
Sep 12 2021
Aug 29 2021
It's not the query service gui that adds the +
When you use the bigdata interface the + gets added as well.
Aug 28 2021
The problem is that the + gets encoded again. It becomes %2B
Aug 14 2021
Aug 11 2021
Aug 6 2021
@Eugene233 When requesting new languages always specify what you want to use them for: Monolingual properties or Lexemes or Labels/Description/Aliases as the developer needs to know where to add them in the code.
If you want to use the language outside Wikidata, you need to contact LangCom (not via Phabricator) what you need to do to get the language added for use on all Wikimedia projects.
Jul 21 2021
Jul 19 2021
Jul 18 2021
Jul 17 2021
@Amire80 What's your view on this?
Jul 8 2021
Jul 3 2021
Jul 2 2021
This is blocked on LangCom approval for the remaining languages.
Jun 29 2021
Jun 27 2021
@Esc3300 My patch was denied for 2 reasons:
- I used da instead of nl (which has been fixed)
- There is not enough proof of consensus in this task (this is something I can't fix.
Added missing translations. Language codes that are present in CLDR need to be updated upstream, language codes not present in CLDR can be added to LocalNamesNl.php
Jun 26 2021
Since there is only approval for mix in case of Mixtepec Mixtec and no approval for mix-und, this isn't ready to go. Still needs LangCom approval. @jhsoby @Amire80 is mix-und a good alternative for this case where it's unknown which form of Mixtec is used?
No. It's only available for monolingual properties. Labels/aliases/descriptions aren't properties and thus not supported. If it's needed, a new ticket is needed for that.
Jun 22 2021
Jun 21 2021
Ideally these changes should be added to Cldr
Jun 19 2021
Jun 17 2021
Jun 16 2021
Jun 13 2021
Jun 12 2021
Language name is correct in CLDR (in LocalNamesEn.php).
Not used for Lexemes, but added as a monolingual language code. Will remove it there.
Since this was created by a langcom member, I assume this can be considered as approved by LangCom
Looks like the language dropdown is using ULS and not the monolingual language dropdowns from Wikidata. So this is more for the SDC team and not for the Language codes team.
Jun 11 2021
I think the list of disallowed languages can be something like:
Jun 10 2021
Which steps can run parallel ?