Thread history

From Support
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
14:50, 15 November 2021 Verdy p (talk | contribs) New reply created (Reply to Adding a new language - Lologooli)
12:57, 15 November 2021 Amire80 (talk | contribs) New reply created (Reply to Adding a new language - Lologooli)
12:27, 15 November 2021 Verdy p (talk | contribs) New reply created (Reply to Adding a new language - Lologooli)
10:42, 15 November 2021 Tochiprecious (talk | contribs) Comment text edited  
10:42, 15 November 2021 Tochiprecious (talk | contribs) Comment text edited  
10:39, 15 November 2021 Tochiprecious (talk | contribs) New thread created  

Adding a new language - Lologooli

Dear Administrators, could you pls add the Lologooli language? There's a group of people who want to translate in this language.

ISO 639-3: rag

  • Local name: Lologooli
  • Name in English: Logooli Language
  • Written: left to right
  • Script: Latin script

Thank you

Tochiprecious (talk)10:39, 15 November 2021

There's now an initial Portal:rag, but it's still not marked as enabled (a site adminsitrator may enable it later).

For the local name, Wikipedia gives Lulogooli, may be Lologooli is a variant you found (but I do not find references for this, while Glottolog lists other aliases).

Verdy p (talk)12:27, 15 November 2021
Amir E. Aharoni (talk)12:57, 15 November 2021

Note to Amir: there are several places to enable/disable a language.

  • The "disabled=yes" parameter in the Portal template used at top of the Portal:code" page, just displays the top notice banner (it is applicable when this applies to all scripts or variants of the language). This is the only thing that your dropped.
  • The "no-15924*=*" or "no-variant*=* parameters (with a non-empty value in the Portal template inclusion) also disables the individual link to the translation interface for a specific script or variant (it is still needed even if the language is disabled because yuo can enable it temporarily (in an edit preview) to test the link to the translation interface, if it does not work or is not effectively enabled, this parameter should be set for each non-working script or variant).
  • There should be no "variant*=*" parameters in the Portal template inclusion for script-only variants (i.e. those using a 4-letter ISO 15924 script code), as this unnecessarily duplicates the list of translation links in the "scripts" and "variants" sections of the portal.
  • The base category (named from the English name of the language, contains a <nowiki>{{Disabled language}]}<nowiki> for showing the banner at top, it also categorizes in "Category:Disabled languages by name" instead of "Category:Languages by name"
  • Its subcategory "" page contains the <nowiki>{{Disabled language}]}<nowiki> banner, it does not change the categorization.
  • Its subcategories "Category:User code"", "Category:User code"-level" contain the Babel template with an extra parameter "disabled=*" with a non-empty value to display the top banner as well. These subcategories are automatically created when we create the portal page, but these user categories have to be changed to use a tracling template showing the navigation and properly subcategorizing them (otherwise the Babzl autocreation still does not generate this single line.

This could be simpler if we just had an API (or magic function) allowing to test the effective status of each language or variant and display the correct status directly, without having to update 9 pages each time for a whole language (however this is not complex to do manually in less than one minute, and this works instantly).

Also when adding a language code whose names are still not known by the "#language:" parser function (at least the names in English and a native name; you can map names for other related languages or wellknown languages, notably those used in linguistic studies, or if the language is a minority one and there are primary languages used in the same region) in the MediaWiki database (Look for the ISO 639-3 site to find the English name, look at references in Glottolog, check the article name used in the portal going to the English Wikipedia, it is not necessarily the same name or the article way describe several languages on the same page), we need to edit the Template:Languagename/db to add them (so that the portal and categories will properly show the names). This local db is still needed because there's still no unified source (and updates for Mediawiki will take long, and this wiki is also used to translate other projects than just Wikimedia wikis based on MediaWiki).

I think that all this will help you (and other people) understand what is going on and how I maintained all this since many months, while I've categorize also all base language categories by large families (not the whole tree), and countries (those listed in Glottolog). This categorization helps users finding the correct language code to use for their translations and avoid confusions (portal pages contain all important links for references in ISO 639, Glottolog and related references that they also link to, and containing interesting status and classification). I've tried to minimize the cost of maintenance and check accurate sources as much as possible (sometimes Wikipedia is insufficient in its articles or listed translations, or there are typos that may take time to be agreed and fixed there in some wikipedia editions, deviating for other sources, sometimes you'll find translation not in Wikipedia but in Wikidata, or wikidata may contain different names and it's hard to decide which name would be the most representative while being precise enouh to exhibit relevant distinctions, even in English).

Thanks anyway for enabling the translation and partially updating the portal.

Verdy p (talk)14:50, 15 November 2021