Mediawiki-i18n

mediawiki-i18n@lists.wikimedia.org

568 discussions

An update on localisation in MediaWiki (2009)
by Siebrand Mazeland 02 Jan '10

02 Jan '10

On 31 December 2007 and 1 January 2008 I sent an e-mail to which this is a follow up[1,2]. First things first, because not everyone reads e-mails completely: * MediaWiki localisation (that is the translation of English source messages to other languages) depends on you! If you speak a language other than English, care about your language in MediaWiki and Wikimedia and like translating, go to http://translatewiki.net, register a user and start contributing translations for MediaWiki and MediaWiki extensions. When your localisation is complete, keep coming back regularly to re-complete it and do quality control. Thank you in advance for all your contributions and effort. * The i18n and L10n area of MediaWiki requires continuous efforts. If this area of FOSS has your interest: we need your help. Please offer your development skills to further MediaWiki's i18n, L10n and translation capabilities[3,4]. All statistics are based on MediaWiki 1.16 alpha, SVN version r60527 (31 December 2009). Comparisons are to MediaWiki 1.14 alpha, SVN version r45277 (1 January 2009). See http://translatewiki.net/wiki/MediaWiki_2009 for a wiki version of this message. ==Introduction== * Localisation or L10n - the process of adapting the software to be as familiar as possible to a specific locale (topic of this message) * Internationalisation or i18n - the process of ensuring that an application is capable of adapting to local requirements (out of scope of this message) MediaWiki has a user interface definition for 362 languages (up from 348). Of those languages at least 39 language codes are duplicates and/or serve a purpose for usability[5]. Reporting on them, however, is not relevant. So MediaWiki in its current state supports 323 languages (up from 322). MediaWiki has 346 core language files (up from 326), of which 27 are redirects from the duplicates/usability group or just empty[6]. So MediaWiki has an active in-product localisation for 308 languages (up from 299). The MediaWiki core product has several areas that can be localised: * regular messages that can and should be localised (2,369 - up 9% from 2,168) * optional messages that can be localised, which is mostly used for languages not using a Latin script (187 - up 8% from 173) * ignored messages that should not be localised (152 - up 2% from 149) * namespace names and namespace aliases (17 - no change) * magic words (142 - up 8% from 132) * special page names (88 - up 2% from 86) * other (directionality, date formats, separators, book store lists, link trail, and others) Localisation of MediaWiki revolves around all of the above. Reporting is done on the regular messages only. MediaWiki is more than just the core product. On http://www.mediawiki.org/wiki/Category:All_extensions 1500 extensions (up 25% from 1200) have some kind of documentation. This analysis only takes the code currently present in svn.wikimedia.org/svnroot/mediawiki/trunk into account. The source code repository contains give or take 445 extensions (up 25% from 370). Most extensions in the MediaWiki Subversion repository now use the reference implementation for i18n. Currently 8,200 messages for MediaWiki extensions can be localised in a consistent way (up 37% from 6,000). ==MediaWiki localisation in practice== MediaWiki localisation has moved further to a centralised collaborative process in translatewiki.net in the past year. Where in 2008 some wikis were still translating in their own MediaWiki: namespace, the introduction of the LocalisationUpdate extension[7], especially in the Wikimedia Foundation wikis, has taken away the last hurdle for local translation against centralised translation: instant gratification. Translations that are committed to Subversion can be added to wikis without requiring software updates, as often as desirable. Little to no translations are submitted through the Bugzilla ticketing system or directly by SVN committers. Exceptions are the localisations of Hebrew, Cantonese, Simplified Chinese, Traditional Chinese, Classical Chinese and Persian, that are still actively maintained in SVN, next to regular contributors from the centralised system. ==The past, the present and the future== MediaWiki localisation has always been a volunteer effort, and expect that it will remain so. 2009 brought a successful Google Summer of Code project, executed by Niklas Laxstrom [8,9] and the Wikimedia Foundation is supporting the localisation that takes place at translatewiki.net[10]. Not only MediaWiki, but all Open Source projects that are supported there[11] benefit from these developments. We want to keep using the Translate extension technology and expand on it, as well as nourish our translator base of nearly 2,000 translators by providing them with better tooling and more projects in 2010. Vereniging Wikimedia Nederland[12], the Dutch Wikimedia Chapter has granted 2,000 Euro to Stichting Open Progress[13] for the translatewiki.net Translation Rallies, that motivated its translators to make more than 60,000 new translations for MediaWiki and its extensions in August and December 2009. New opportunities lie in better support of Translation Memory technology and more supported projects to grow the community and allow the translators to spend their time as productive as possible, while still allowing all the socialising and collaboration features of MediaWiki. At the Google Summer of Code Mentor Summit there was interest from the KDE Documentation Project[14], the PHP Documentation Project, Pidgin, wxWidgets, and other projects. For translatewiki staff this was a confirmation that our approach works. The Translate extension however needs more development. If you want to work on an exciting extension that makes a difference in multi language support for Open Source software and MediaWiki content pages that require structured translation, check out the Translate extension and help us make it better. Your help *is* needed and most welcome! The Wikimedia Strategic Planning process that is currently taking place also allows for a broader perspective on the localisation of MediaWiki in a Wikimedia context[15]. Support for several dozen MediaWiki extension in the Wikia code repository is expected within the next few weeks. Wikimedia is, or will soon be including a localisation score for language projects in their statistics, so that in a year we expect to be able to analyse if localisation is a requirement for a rise in usage or if it is a consequence[16]. ==MediaWiki localisation statistics== Daily statistics for MediaWiki and extension localisation have been available for the past two years[17]. For the past two years (arbitrary) milestones have been set for four collections of MediaWiki related messages. For the usability of MediaWiki in a particular language, the group 'core most used' is the most important. A language must qualify for MediaWiki to have 'minimal support' for that language in the first group. Reaching further milestones indicates the maturity of a localisation: * core most used (469): 98% * core (2,369 messages): 90% * Wikimedia extensions (2,700 messages): 90% * extensions (8,200 messages): 65% Currently the following numbers of languages have passed the above milestones[18]: * core most used: 147 (45.6% of supported languages - up 35% from 109 - goal of 130 passed) * core: 82 (21.1% of supported languages - up 21% from 68 - goal of 90 missed by 203 translations) * Wikimedia extensions: 44 (13.6% of supported languages - up 22% from 36 - goals of 50 missed by 1,500 translations) * extensions: 39 (12.1% of supported languages - up 86% from 21 - goal of 30 passed) I think the changes in the past year are very satisfying. MediaWiki localisation has again improved enormously in the past year. Two of the four goals I set in last years' e-mail have not been reached (only one of four goals was reached for 2008). We nearly got there, though. Currently MediaWiki core contains 377,394 messages (up 24% from 303,863 ultimo 2008). ==Conclusion== So... Is MediaWiki doing well on localisation? Just like the past two years, my personal opinion is that we do a proper job, but can still do a lot better. After all, MediaWiki is the engine that runs a top 5 site in the world committed to creating "a world in which every single human being can freely share in the sum of all knowledge." Observing that there are also an estimated hundred thousand MediaWiki installations out there, more than 250 Wikipedias that all use the Wikimedia Commons media repository, and that 147 languages out of 323 have a minimal localisation, there is a lot of room for improvement; more realistically: the work will never be done, we the least we can do is try to get there :). Last year I mentioned languages from Africa performing way below average. I am sad to conclude that this has not changed considerably. In an overview with a weighted score for the localisation level of MediaWiki in a Wikimedia context[19], the largest African languages have the lowest score (52 out of 100). Large languages spoken on multiple continents and large languages from Europe are doing best (100 and 99 out of 100 respectively). Languages like Oriya, Zulu, Burmese and Urdu are the large languages with the worst localisation score. It is my personal aim to work towards an average L10n score of 83 for the 50 largest languages in the world by the end of September 2010. We have all the tools to successfully localise MediaWiki into any of the 7,000 or so languages that have been classified in ISO 639-3. We only need one person per language to make and effort and make it happen. Reaching the first milestone (core most used) takes about six hours of work. Using translatewiki.net or the Gettext file, little to no technical knowledge is required. Knowledge of MediaWiki is a plus. This was the pitch, basically the same as in 2007 and 2008, with even more experience and data. Goals for MediaWiki localisation per end of 2010 are ambitious, but still realistic with the right effort: * core most used: 170 languages with 98% or more localised * core: 105 languages with 90% or more localised * wikimedia extensions: 65 languages with 90% or more localised * extensions: 50 languages with 65% or more localised I would like to wish everyone involved in any aspect of MediaWiki a wonderful 2010. Cheers! Siebrand Mazeland [1] http://lists.wikimedia.org/pipermail/translators-l/2007-December/000571.html [2] http://translatewiki.net/wiki/User:Siebrand/An_update_on_localisation_in_Me… [3] https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&component=… [4] http://translatewiki.net/wiki/User:Siebrand#Bugs [5] als, be-x-old, ckb, crh, de-at, de-ch, de-formal, dk, en-gb, fiu-vro, gan, got, hif, kk, kk-cn, iu, kk-kz, kk-tr, ko-kp, ku, ku-arab, nb, ruq, simple, sr, tg, tp, tt, ug, zh, zh-classical, zh-cn, zh-sg, zh-hk, zh-min-nan, zh-mo, zh-my, zh-tw, zh-yue [6] als, be-x-old, bh, ckb, ckb-latn, crh, de-at, dk, en-rtl, fiu-vro, gan, hif, hif-deva, ii, iu, kk, kk-cn, kk-kz, kk-tr, ko-kp, ks, ku, nb, pi, ruq, simple, st, tg, tp, tt, ug, zh-classical, zh-cn, zh-min-nan, zh-mo, zh-my, zh-sg, zh-yue [7] http://www.mediawiki.org/wiki/Extension:LocalisationUpdate [8] http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2009/wikime… [9] http://laxstrom.name/blag/2009/09/01/gsoc-wrap-up-translate-extension/ [10] http://techblog.wikimedia.org/2009/10/supporting-translatewiki-net/ [11] http://translatewiki.net/wiki/Project_list [12] http://nl.wikimedia.org [13] http://www.openprogress.org/Stichting_Open_Progress [14] http://translatewiki.net/wiki/Project:KDE_Documentation [15] http://strategy.wikimedia.org/wiki/Localisation [16] http://stats.wikimedia.org/EN/TablesCurrentStatusVerbose.htm [17] http://translatewiki.net/wiki/Translating:Group_statistics [18] http://translatewiki.net/wiki/Translating:Group_statistics_in_time [19] http://translatewiki.net/wiki/Project:MediaWiki_localisation_in_the_50_most…

1 0

Call for translations: MediaWiki needs your language skills
by Siebrand Mazeland 20 Dec '09

20 Dec '09

Dear translators, MediaWiki is constantly in need of your help. In the MediaWiki repository we do not only maintain MediaWiki with about 2,400 messages but we also have well over 400 MediaWiki extensions, of which some 375 have over 8,000 translatable messages. As the end of this year is near, and we are getting ready for the next major MediaWiki release (1.16), we once again call upon you for your help. Please come to http://translatewiki.net, create a user account, request translator rights and set your language in your preferences. Then check your language code at http://translatewiki.net/wiki/Special:LanguageStats to see where you can contribute. Chances are that you can contribute a whole lot. Thank you very much in advance for your help! Siebrand Mazeland

1 0

Re: [Mediawiki-i18n] [OSM-dev] Links and I18N
by Ævar Arnfjörð Bjarmason 28 Oct '09

28 Oct '09

2009/10/28 Bráulio Bezerra da Silva <brauliobezerra(a)gmail.com>: > The links in the OSM page are not translatable. For example, the "Help and > Wiki" link always goes to the English wiki, which isn't desirable. Could > anyone with easy access to the site add this as a translatable string? The problem is that those strings are marked as optional by Translatewiki and AFAIK there isn't a way to see what strings are optional for a project without digging around in source files, but maybe I'm wrong.

2 1

Re: [Mediawiki-i18n] [OSM-dev] Links and I18N
by Ævar Arnfjörð Bjarmason 28 Oct '09

28 Oct '09

2009/10/28 Bráulio Bezerra da Silva <brauliobezerra(a)gmail.com>: > Thank you. It is inside the "optional" category in the OSM's TranslateWiki > page. That's why I couldn't find it. Yes sorry, there it is. I couldn't find it either:)

1 0

Re: [Mediawiki-i18n] [OSM-dev] OSM website & Potlatch translation
by Ævar Arnfjörð Bjarmason 15 Oct '09

15 Oct '09

On Thu, Oct 15, 2009 at 1:44 PM, Erik Johansson <emj(a)kth.se> wrote: > On Thu, Oct 15, 2009 at 12:08 AM, Ævar Arnfjörð Bjarmason > <avarab(a)gmail.com> wrote: >> However the Translatewiki sync last happened last Saturday. I don't >> know why there hasn't been another update more recently. CC-ing it to >> the Translatewiki guys so they can chime in. > > Hi do you have a script that does the translatewiki 2 yaml, or how is > that handled? Would be nice to have some checks of the validity of > translatewiki translations.... It's done by Translatewik itself through an export driver. The code is all in /extensions/Translate in the MediaWiki SVN: http://www.mediawiki.org/w/index.php?title=Special:Code/MediaWiki/path&path… What sort of validation checks were you interested in implementing?

1 0

The OpenStreetMap website is now translatable at Translatewiki
by Ævar Arnfjörð Bjarmason 01 Oct '09

01 Oct '09

The main OpenStreetMap website (http://openstreetmap.org) can now be translated on the web using Translatewiki. I originally floated the idea in July[1] and after meeting up with the maintainers of Translatewiki at Wikimania 2009[2] we made it happen. Nikerabbit and Siebrand (Translatewiki guys) have done some great work on making this happen. If you want to translate OpenStreetMap site you can now do so at the Translatewiki site: http://translatewiki.net/wiki/Translating:OpenStreetMap Since it was imported yesterday from the OpenStreetMap SVN server we've had 1500 edits to the translations by 10 different users. 9 of those are to languages that didn't have translations already (although they're still small): Stats for yesterday: http://translatewiki.net/w/i.php?title=Translating:OpenStreetMap/stats/trun… Stats for today: http://translatewiki.net/w/i.php?title=Translating:OpenStreetMap/stats/trun… Stats for *now*: http://translatewiki.net/wiki/Translating:OpenStreetMap/stats/trunk These translations aren't automatically being synced back to the OpenStreetMap SVN repository yet. Me and Nikerabbit have been fixing bugs in the import/export process required to make this happen. Those bugs don't affect translations on Translatewiki.net, but it might be a few days before we can start committing back so the translated strings will show up on the OpenStreetMap site. So please go to Translatewiki and help make OpenStreetMap available in your language! 1. http://lists.openstreetmap.org/pipermail/dev/2009-July/016127.html 2. http://lists.openstreetmap.org/pipermail/dev/2009-August/016707.html

6 10

Update on using Translatewiki for translations
by Ævar Arnfjörð Bjarmason 28 Aug '09

28 Aug '09

On Thu, Jul 9, 2009 at 12:17 PM, Ævar Arnfjörð Bjarmason<avarab(a)gmail.com> wrote: I'm splitting this from the previous thread. > On Tue, Jun 23, 2009 at 1:21 PM, Richard Fairhurst<richard(a)systemed.net> wrote: >> Potlatch uses the OSM wiki for localisation. I have no plans to change this >> in favour of a third-party solution. > > Perhaps we should look into using translatewiki, OpenLayers is already using it: > > http://translatewiki.net > http://translatewiki.net/wiki/Translating:OpenLayers/stats/trunk > > The software itself is just a MediaWiki extension: > > http://www.mediawiki.org/wiki/Extension:Translate > > How it works is that you write a driver for it so that it can > read-write your in/output, here's the driver for OpenLayers for > example: > > http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/Translate/ffs/Op… > > Then you run a job periodically which dumps the translations & imports > them into your project. Bidirectional syncing is also possible but > then you have to worry about merging. > > They're already working on a YAML driver. > > Once you're logged in you get a nice Launchpad-like interface for > translations. *I* think it's more tedious than just editing the YAML > in Emacs but then again it's not really targeting that demographic but > amateur translators who'll be more familiar with a web interface I talked to siebrand (Translatewiki guy) yesterday here at Wikimania 2009 about using Translatewiki for OSM projects. Beginning with the rails_port. They now have a YAML driver so they can support our translations, how it would work is: * Initially the translations would be imported to Translatewiki from the files in sites/rails_port/config/locales/ * Translators would then go to the Translatewiki site for translations It would be easiest if translations were exclusively done at Translatewiki from this point (so we don't have to do merging). Strings could be added / deleted in the primary en.yml file by developers when hacking the rails_port and the re-import / export process would take this into account. Translations would then be merged back into the OSM SVN by running a job which exports from Translatewiki. Siebrand has offered to take care of this task if we give him a SVN account. He's already maintaining such jobs at dozens of SVN servers, so adding one more isn't a workload for him. Here's an example of such a commit: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/55608 The only problem I can see is Translatewiki's incompatibility with with rails-i18n's plural forms. I.e. when you can turn a key "foo.bar" into "foo.bar.[one/two/three/.../other]" if it contains a "{{count}}" variable. We can hack around this by simply providing all the plural forms for all languages if any language needs them. Plural forms are used for <2% of our translation strings so I don't think this would be that large of a PITA. Especially compared to all the translations we'd get in return.

1 0

Call for translations: translatewiki.net August 2009 Translation Rally
by Siebrand Mazeland 09 Aug '09

09 Aug '09

As of today, and up to and including next Monday, http://translatewiki.net is having its second ever Translation Rally[1]. As an incentive to our translators, we are dividing 1,000 Euro over all translators that contribute 500 or more new translations to MediaWiki or its extensions. This Translation Rally has kindly been made possible by a grant from the International Projects fund of the Dutch Wikimedia chapter Vereniging Wikimedia Nederland[2] to Stichting Open Progress[3], that coordinates the financial aspect of the Translation Rally. We call on all non-English speakers to take part in this Translation Rally and make it as big a success as possible, so that MediaWiki can stay one of the best localised pieces of software in the known universe. The first Translation Rally ended with 35 translators meeting the requirements[4], and some 20,000 new messages were translated over the regular stream. A success we could not have imagined. We dare you to do even better this time. Cheers! Siebrand Mazeland translatewiki.net staff [1] http://translatewiki.net/wiki/Project:Rally-2009-08 [2] http://nl.wikimedia.org/wiki/Mainpage [3] http://openprogress.org/Open_Progress [4] http://translatewiki.net/wiki/Translating:Language_project/500claim

1 0

regarding MediaWiki internationalisation and language setup
by Ram Jeevan 07 Aug '09

07 Aug '09

HI, i've install latest 1.15 mediawiki. now i want to install localisation. can you help me in this. like my URL will be http://localhost/mediawiki/index.php/Main_Page if click on 'en' language. and if i click on fr then it should be http://localhost/mediawiki/index.php/Main_Page/fr Thanks Ram

2 1

List admin change
by Siebrand Mazeland 13 Jun '09

13 Jun '09

Just an administrative notice: I just took over as list administrator from Nikerabbit. At the moment this list has 153 subscriptions and is very low volume. Cheers! Siebrand

1 0

← Newer
1
...
44
45
46
47
48
49
50
...
57
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Mediawiki-i18n