Last modified: 2008-12-09 22:40:45 UTC
Created attachment 5569 [details] Add songlai name to Names.php The songhai language (http://en.wikipedia.org/wiki/Songhai_languages) is not present in the Names.php file and thus can't be rendered properly on WM projects. See the tiny patch attached.
Ethnologue does not have a language with the name "Songlai" classified. ISO 639-3 code 'ses' is for "Koyraboro Senni Songhay", a language of Mali, also known as Koyra Senni, Koroboro Senni, Songay Senni, Songoy, Songai, Songhai, Songay, Songoi, Songhay, Sonrai, Sonrhai, East Songhay, Gao Songhay, or Koyra Senni Songhay[1]. We are discussing the same language here? Next: this patch will not be applied. Languages are added to the MediaWiki core product when at least 50% of the most often used MediaWiki messages have been localised (about 250 of 2200 core messages). Localisation can be done at Betawiki (http://translatewiki.net), a wiki where most of the MediaWiki localisation takes place. In this wiki 'ses' will be added locally until the threshold is reached. [1] http://www.ethnologue.com/show_language.asp?code=ses
I should note that the 50% of 'most used' is of course a lower limit, and that in my personal opinion a localisation isn't really relevant until at least all 'most often used messages' have been translated, after which a locale will actually be maintained, leading to a complete localisation.
Yes, we are talking about koyraboro senni Songhay. I understand the 50% quota but it seems (I may be wrong) that it's requiered to have the language name translated in Names.php in order to have the Template:ses work properly on Commons. My problem is : I can't add songhay legends to the file I upload on Commons because it uses that file to display the name. I don't believe that we need to have translated the whole software to be able to add _content_ in this language.
Then the template is wrong, which may mean it is a content issue, leading to the conclusion that this issue should be dealt with on Commons, rather than in Bugzilla.
OK, I understand and found a workaround. Closing the bug.