It is hard to believe that we don't have translations of the Wikimedian language names in the Wikimedian languages. So, please, do that starting from the page: http://meta.wikimedia.org/wiki/Language_names
It is hard to believe that we don't have translations of the Wikimedian language names in the Wikimedian languages. So, please, do that starting from the page: http://meta.wikimedia.org/wiki/Language_names
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
It is a very good idea, but may be it is good to update the table first: I see for instance that crh (Crimean Tatar) is not there, and the crh.wp was open in January.
Cheers Yaroslav
On Wed, May 14, 2008 at 10:59 PM, Yaroslav M. Blanter putevod@mccme.ru wrote:
It is a very good idea, but may be it is good to update the table first: I see for instance that crh (Crimean Tatar) is not there, and the crh.wp was open in January.
I added Crimean Tatar (in the section "Aditional languages"). I used [[meta:Template:Active <Project>s]] lists to list languages. It is possible that more languages are missing, too. There is instruction at the page how to add a language which is not listed, too.
Hoi, The Babel extension that is being developed in Betawiki has all these languages translated into the native language. Also the name for the language is initially retrieved from the CLDR standard. We will welcome your help localising the Babel extension... We truly want it to become available as a WMF extension :)
I am still puzzled what you want to use it for.. There are many projects that have already done exactly this and many are available under a free license as well.. Thanks, GerardM
On Thu, May 15, 2008 at 12:29 AM, Milos Rancic millosh@gmail.com wrote:
On Wed, May 14, 2008 at 10:59 PM, Yaroslav M. Blanter putevod@mccme.ru wrote:
It is a very good idea, but may be it is good to update the table first:
I
see for instance that crh (Crimean Tatar) is not there, and the crh.wp
was
open in January.
I added Crimean Tatar (in the section "Aditional languages"). I used [[meta:Template:Active <Project>s]] lists to list languages. It is possible that more languages are missing, too. There is instruction at the page how to add a language which is not listed, too.
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
On Thu, May 15, 2008 at 2:18 AM, Gerard Meijssen gerard.meijssen@gmail.com wrote:
The Babel extension that is being developed in Betawiki has all these languages translated into the native language. Also the name for the language is initially retrieved from the CLDR standard. We will welcome your help localising the Babel extension... We truly want it to become available as a WMF extension :)
I am still puzzled what you want to use it for.. There are many projects that have already done exactly this and many are available under a free license as well..
I need it for bots. And I need it only for existing WM projects. I know that there are many projects which have almost everything needed, so it would be helpful. Also, I see that [[ISO 639-1]] pages through a lot of the projects are well localized.
The point is that I/we need it for WM purposes (which don't include only bots, but, as you said, may be useful for Babel templates, too; also, instead of looking into codes at Meta localization pages, we may look in language names in our language). Actually, I think that it should be added into Betawiki as an integral part of MW localization process.
However, while I am waiting for that, I want to have something. Actually, I think that this set of pages may be useful for further work related to MW localization.
Hoi, The Babel extension is to do away with the Babel templates.. Having them in an extension means that we need to maintain them only once. There is already support for 69 languages and it does include the language name in the language itself. Thanks, GerardM
On Thu, May 15, 2008 at 2:33 AM, Milos Rancic millosh@gmail.com wrote:
On Thu, May 15, 2008 at 2:18 AM, Gerard Meijssen gerard.meijssen@gmail.com wrote:
The Babel extension that is being developed in Betawiki has all these languages translated into the native language. Also the name for the language is initially retrieved from the CLDR standard. We will welcome
your
help localising the Babel extension... We truly want it to become
available
as a WMF extension :)
I am still puzzled what you want to use it for.. There are many projects that have already done exactly this and many are available under a free license as well..
I need it for bots. And I need it only for existing WM projects. I know that there are many projects which have almost everything needed, so it would be helpful. Also, I see that [[ISO 639-1]] pages through a lot of the projects are well localized.
The point is that I/we need it for WM purposes (which don't include only bots, but, as you said, may be useful for Babel templates, too; also, instead of looking into codes at Meta localization pages, we may look in language names in our language). Actually, I think that it should be added into Betawiki as an integral part of MW localization process.
However, while I am waiting for that, I want to have something. Actually, I think that this set of pages may be useful for further work related to MW localization.
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
On 5/15/08, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, The Babel extension that is being developed in Betawiki has all these languages translated into the native language. Also the name for the language is initially retrieved from the CLDR standard. We will welcome your
Another solution is to use libicu (http://www.icu-project.org/) via php-intl extension (http://docs.php.net/manual/en/intro.intl.php). ICU have already imported those translations from CLDR. See http://demo.icu-project.org/icu-bin/locexp?_=fr&SHOWLanguages=1#Language... , for an example of french translations.
With php-intl, use, http://docs.php.net/manual/en/locale.getdisplaylanguage.php: to get localized display of language name http://docs.php.net/manual/en/locale.getdisplayscript.php: localized display of script name http://docs.php.net/manual/en/locale.getdisplayregion.php: localized display of region name
MediaWiki then could have magic variables for these translations.
help localising the Babel extension... We truly want it to become available as a WMF extension :)
I am still puzzled what you want to use it for.. There are many projects that have already done exactly this and many are available under a free license as well.. Thanks, GerardM
Hoi, There are many more languages then provided by either the CLDR or the ICU-project.. Also we have a need not only but also for the name of the language. The codes as used by the ICU are a mix of the codes used by the different ISO-639 standards.. The Babel extension is aware of both ... Thanks, GerardM
On Thu, May 15, 2008 at 8:56 AM, Anon Sricharoenchai anon.hui@gmail.com wrote:
On 5/15/08, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, The Babel extension that is being developed in Betawiki has all these languages translated into the native language. Also the name for the language is initially retrieved from the CLDR standard. We will welcome
your
Another solution is to use libicu (http://www.icu-project.org/) via php-intl extension (http://docs.php.net/manual/en/intro.intl.php). ICU have already imported those translations from CLDR. See http://demo.icu-project.org/icu-bin/locexp?_=fr&SHOWLanguages=1#Language... , for an example of french translations.
With php-intl, use, http://docs.php.net/manual/en/locale.getdisplaylanguage.php: to get localized display of language name http://docs.php.net/manual/en/locale.getdisplayscript.php: localized display of script name http://docs.php.net/manual/en/locale.getdisplayregion.php: localized display of region name
MediaWiki then could have magic variables for these translations.
help localising the Babel extension... We truly want it to become
available
as a WMF extension :)
I am still puzzled what you want to use it for.. There are many projects that have already done exactly this and many are available under a free license as well.. Thanks, GerardM
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
There is an important distinction between translating all language names and translating the language names of Wikimedia projects. For the first one I suggest usage of OmegaWiki, of course (Gerard, may you give the links to the ISO 639-* sets at OW?), which may be filled by other projects, too. Babel templates/extension should contain not only WM languages, too.
The other thing is the set of languages which are used at WM projects. This should be the priority for translation. When we have translated the most of them, we would be able to have, for example, multilingual www.wiki*.org pages, as well as a lot of other lists which contain language names of WM projects.
On Thu, May 15, 2008 at 9:03 AM, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, There are many more languages then provided by either the CLDR or the ICU-project.. Also we have a need not only but also for the name of the language. The codes as used by the ICU are a mix of the codes used by the different ISO-639 standards.. The Babel extension is aware of both ... Thanks, GerardM
On Thu, May 15, 2008 at 8:56 AM, Anon Sricharoenchai anon.hui@gmail.com wrote:
On 5/15/08, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, The Babel extension that is being developed in Betawiki has all these languages translated into the native language. Also the name for the language is initially retrieved from the CLDR standard. We will welcome
your
Another solution is to use libicu (http://www.icu-project.org/) via php-intl extension (http://docs.php.net/manual/en/intro.intl.php). ICU have already imported those translations from CLDR. See http://demo.icu-project.org/icu-bin/locexp?_=fr&SHOWLanguages=1#Language... , for an example of french translations.
With php-intl, use, http://docs.php.net/manual/en/locale.getdisplaylanguage.php: to get localized display of language name http://docs.php.net/manual/en/locale.getdisplayscript.php: localized display of script name http://docs.php.net/manual/en/locale.getdisplayregion.php: localized display of region name
MediaWiki then could have magic variables for these translations.
help localising the Babel extension... We truly want it to become
available
as a WMF extension :)
I am still puzzled what you want to use it for.. There are many projects that have already done exactly this and many are available under a free license as well.. Thanks, GerardM
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
There are some important similar sets for translation, which I didn't include (maybe I should do that...):
- The names of the projects in different languages (Wikipedia, Wikinews, Wiktionary...). - The language adjectives forms in connection with the projects names (Wikipedia in Italian [language], Wiktionary in French [language]...). - General rules for genitive/possesive case usage for the projects for constructions like "Wikipedia statistics/Statistics of Wikipedia [in <some> [language]]".
Some of the features needed for that are implemented at MediaWiki and could be used at Betawiki after some amount of coding.
On Thu, May 15, 2008 at 12:27 PM, Milos Rancic millosh@gmail.com wrote:
There is an important distinction between translating all language names and translating the language names of Wikimedia projects. For the first one I suggest usage of OmegaWiki, of course (Gerard, may you give the links to the ISO 639-* sets at OW?), which may be filled by other projects, too. Babel templates/extension should contain not only WM languages, too.
The other thing is the set of languages which are used at WM projects. This should be the priority for translation. When we have translated the most of them, we would be able to have, for example, multilingual www.wiki*.org pages, as well as a lot of other lists which contain language names of WM projects.
On Thu, May 15, 2008 at 9:03 AM, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, There are many more languages then provided by either the CLDR or the ICU-project.. Also we have a need not only but also for the name of the language. The codes as used by the ICU are a mix of the codes used by the different ISO-639 standards.. The Babel extension is aware of both ... Thanks, GerardM
On Thu, May 15, 2008 at 8:56 AM, Anon Sricharoenchai anon.hui@gmail.com wrote:
On 5/15/08, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, The Babel extension that is being developed in Betawiki has all these languages translated into the native language. Also the name for the language is initially retrieved from the CLDR standard. We will welcome
your
Another solution is to use libicu (http://www.icu-project.org/) via php-intl extension (http://docs.php.net/manual/en/intro.intl.php). ICU have already imported those translations from CLDR. See http://demo.icu-project.org/icu-bin/locexp?_=fr&SHOWLanguages=1#Language... , for an example of french translations.
With php-intl, use, http://docs.php.net/manual/en/locale.getdisplaylanguage.php: to get localized display of language name http://docs.php.net/manual/en/locale.getdisplayscript.php: localized display of script name http://docs.php.net/manual/en/locale.getdisplayregion.php: localized display of region name
MediaWiki then could have magic variables for these translations.
help localising the Babel extension... We truly want it to become
available
as a WMF extension :)
I am still puzzled what you want to use it for.. There are many projects that have already done exactly this and many are available under a free license as well.. Thanks, GerardM
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
The translation of language names in WM should be put in public domain? So that CLDR can copy these translations into CLDR repository.
On 5/15/08, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, There are many more languages then provided by either the CLDR or the ICU-project.. Also we have a need not only but also for the name of the language. The codes as used by the ICU are a mix of the codes used by the different ISO-639 standards.. The Babel extension is aware of both ... Thanks, GerardM
On Thu, May 15, 2008 at 12:40 PM, Anon Sricharoenchai anon.hui@gmail.com wrote:
The translation of language names in WM should be put in public domain? So that CLDR can copy these translations into CLDR repository.
Translations of language names are public domain.
The language name issues has been concerns of mine, and of course, Erik Zachte at least since 2006. Increasing the number of projects, the statistics table he generates has become less and less translated: all languages but English tables are mixture of English and that language. And it happens on other values in his stats, like the project names except Wikipedia, new feature of the stat table etc.
Shortly for non-English speakers, the more useful Zachte stats becomes, the more it becomes reader-unfriendly with increasing English values on the table.
We had a desire to clean it up, but alas, had no time to spare until now. Is there anyone who are willing to take care of those translation of "all Wikimedia languages" and complete the table update.
On Thu, May 15, 2008 at 7:29 AM, Milos Rancic millosh@gmail.com wrote:
On Wed, May 14, 2008 at 10:59 PM, Yaroslav M. Blanter putevod@mccme.ru wrote:
It is a very good idea, but may be it is good to update the table first: I see for instance that crh (Crimean Tatar) is not there, and the crh.wp was open in January.
I added Crimean Tatar (in the section "Aditional languages"). I used [[meta:Template:Active <Project>s]] lists to list languages. It is possible that more languages are missing, too. There is instruction at the page how to add a language which is not listed, too.
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
On Thu, May 15, 2008 at 8:17 AM, Aphaia aphaia@gmail.com wrote:
The language name issues has been concerns of mine, and of course, Erik Zachte at least since 2006. Increasing the number of projects, the statistics table he generates has become less and less translated: all languages but English tables are mixture of English and that language. And it happens on other values in his stats, like the project names except Wikipedia, new feature of the stat table etc.
Shortly for non-English speakers, the more useful Zachte stats becomes, the more it becomes reader-unfriendly with increasing English values on the table.
We had a desire to clean it up, but alas, had no time to spare until now. Is there anyone who are willing to take care of those translation of "all Wikimedia languages" and complete the table update.
This set of pages were produced in the process of partitioning translation file for my bot. While I dealt only with Wikinews, it was reasonable to keep them inside of one page [1], including messages like "Images", "Administrators", "Good [pages]" etc. are.
However, the rest of messages for statistics (including, of course, Zachte's statistics) may be maintained at the similar way -- until all of them would be moved to Betawiki (or some similar project).
[1] - http://meta.wikimedia.org/wiki/User:Millbot/translations.py
On Wed, May 14, 2008 at 3:39 PM, Milos Rancic millosh@gmail.com wrote:
It is hard to believe that we don't have translations of the Wikimedian language names in the Wikimedian languages. So, please, do that starting from the page: http://meta.wikimedia.org/wiki/Language_names
Sorry, but what exactly is the point of this? Isn't it best to use the language in its proper name (or language code) whenever possible?
i.e. instead of us using "Japanese", shouldn't we refer to it by "ja" and/or "日本語"?
2008/5/14 Casey Brown cbrown1023.ml@gmail.com:
On Wed, May 14, 2008 at 3:39 PM, Milos Rancic millosh@gmail.com wrote:
It is hard to believe that we don't have translations of the Wikimedian language names in the Wikimedian languages. So, please, do that starting from the page: http://meta.wikimedia.org/wiki/Language_names
Sorry, but what exactly is the point of this? Isn't it best to use the language in its proper name (or language code) whenever possible?
i.e. instead of us using "Japanese", shouldn't we refer to it by "ja" and/or "日本語"?
All statistics in English are naming languages because the name in English is a default. So, why other languages shouldn't have that privilege to have statistics in their own language, instead of having code names (which already exists).
BTW, except for well known languages (~30), all other codes are not so useful, even the language name may be known. While adding Crimean Tatar, I realized that I added it with "chr" code, instead of "crh". Ask a random Wikipedian which languages have codes "eu", "fa" and even "zh"...
I think that your approach has a lot of common with the fact that you are a native English speaker and that you have everything in defaults.
wikimedia-l@lists.wikimedia.org