The langdb in jquery.uls includes useful information about languages: script (and by extension - direction), autonym, and geographical areas in which the languages is spoken. It also includes functions for querying the database.
Being coupled to ULS makes it not-so-comfortable to use in other products that could use a library for querying information about languages on the frontend. It should be separated from ULS.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | Amire80 | T30708 BiDi: LTR and RTL mixed up (tracking) | |||
| Resolved | • Nirzar | T66617 List of languages looks strange when mixes RTL and LTR languages | |||
| Resolved | santhosh | T78337 refactor the langdb in ULS to make it more easily reusable | |||
| Resolved | santhosh | T131140 Create a language data library out of jquery.uls.data module and make it independent of jquery |
https://github.com/wikimedia/language-data now provides the langauge data that was initially bundled in jquery.uls. We required this for ContentTranslation-CXserver
Jquery.uls will start using this library. See https://github.com/wikimedia/jquery.uls/pull/271