Wikidata is one of the most important and exciting innovations in the world around Wikipedia. To make it accessible to a wide range of users, it needs its user interface to be translated to as many languages as possible, and you can help.

At the first stage, already partly enabled, Wikidata stores “interwiki links”, i.e. page metadata that connect articles about a same topic on different language versions of Wikipedia. Historically, these interwiki links have been duplicated and stored in each of the pages they linked together. With Wikidata, the list of pages about a same topic is centralized.

The next goal of Wikidata is to store not only page metadata like interwiki links, but also common data that is repeated in all languages, such as census data for cities and dates of birth and death of famous authors.

Practically all the projects that are related to Wikipedia are massively multilingual, but Wikidata is especially so: it stores common data with the goal of displaying it efficiently in all languages.

The very useful and famous CIA World Factbook site has tables of data about all countries in the world, but the labels are only written in English. Now imagine a site with such tables, but with the ability to display the labels in any language and not just English: that’s what Wikidata aims to become.

In the near future, the translation of such table labels will be done on the Wikidata website itself. In the meantime, you can help by translating the user interface displayed by the software running Wikidata.

Translation of the Wikidata software is done on translatewiki.net, the same translation platform used to translate Wikipedia’s interface. Wikidata relies on three main components that need translating: Wikibase – Repo, Wikibase – Client and Wikibase – Lib.

Wikipedia made encyclopedic articles open and accessible; Wikidata is about to do the same to statistics and other structured information. To ensure that people speaking your language can benefit from the immense potential of Wikidata, and contribute to its success,  please join us today and help us translate it.

Thank you!

after the slush, the flush

When new code does not find its way into production for quite some time, it tends to pile up. It is like with snow and when the time comes when it starts to thaw, it starts with a trickle, the trickles become a stream and all the streams rush down the mountain.

For the WMF Localisation team we worked on our documentation, our help system and our tests. We went to conferences in Belgium and India. And we worked on many small iterative improvements. We rolled out webfonts to more wikis. Input methods were improved and deployed as per requests. We have had our translation memory working on translatewiki.net for ages and now it is configured for use on the WMF wikis who use the Translate extension. Actually, we did experiment first with a new algorithm and we did configure one of the labs systems as a host for the memory of all the fine work we did and do.

Over time a lot of work went into things like plural rules. As the number of languages increase and as we support not only PHP but now also JavaScript, we are optimising our code and we are checking it again. We frequently find that a re-factoring is in order. It makes the code more elegant and easier to maintain. With added documentation and tests we ensure that we know it will work well.

Another fine project waiting to get to the stage where it will flow into our codebase is an updated Easy Timeline. The functionality has always been broken when used in many of  the “other” languages, languages written in a different direction, a different script.  The updated Easy Timeline has been given a revamp; it uses SVG to create the image and you can test it at translatewiki sandbox. Amir welcomes bug reports and LOVES to hear your comments

As you know, we use mingle for our project management (user guest, password guest). In it we have stories that explain the functionality that we are going to develop. Story 532 is one such:

As a potential translator, I want to be able to tell translation administrators in a structured way that I am interested in translating to one or more languages and at the same time provide them with some data about me and preferences on how and how often I would like to be contacted, so that translation administrators can more effectively and efficiently target translators.

Together with the acceptance criteria a narrative like this enables the developer to develop and the finished product to be accepted by our product manager. A story comes with tasks and once you have read the stories and the tasks you have a clue of what goes into getting you new functionality.

The conferences were great, we learn a lot from meeting so many wonderful people. Many tests are deployed and they run regularly. The documentation, including user documentation is written and we love you to translate many of them in your language. We feel really pumped up to get cracking and provide you with more functionality in the next sprint.

Thanks,
Gerard Meijssen
Internationalization / Localization outreach consultant

On Saturday 28 January 2012 at 20:00 UTC there will be a workshop on Translation tools. It will take between 60 and 90 minutes and will consist of an introduction of use cases and features, as well as a Q&A. (local times)

The workshop will focus on the use cases covered by the Translate extension on Wikimedia Meta-Wiki for the following user roles:

• writers: those who write texts that need to be translated
• translation administrators: those who mark pages for translations and post-process translations when they have been made

Please put the following page on your watchlist and write your name down if you would like to attend. The workshop is held online using WebEx. I would advise you to log in 15 minutes in advance to ensure you have ample time to set up your computer if you have not used WebEx before. WebEx can be used in desktop environments on Linux, OSX and Windows.

If you would like to familiarise yourself with the technology before the workshop, please take a look at the elaborate documentation, which includes some tutorials. In the next two weeks, the already present documentation for translators will also be completed.

Credit goes to Pete Forsyth for proposing to have this workshop. Hope to see you online Saturday!

Siebrand Mazeland
Product Manager Localisation
Wikimedia Foundation

Probably the most interesting highlight of today’s i18n deployment is the configuration of the Translate extension on MediaWiki.org. We have observed that on some wikis special pages exist that explain in the language of the Wiki functionality like Narayam or WebFonts. Such documentation is welcome on all MediaWiki installations where the functionality is used by people using the same language for their user interface.

For writing the documentation MediaWiki.org is the obvious platform. With the deployment of Translate we have the basis for writing and translating user documentation in a structured and organised way.

Narayam and WebFonts have been updated to the latest versions that have been tested on translatewiki.net. As Narayam and WebFonts are still very much a work in progress, we invite anyone to continue their testing at translatewiki.net . The changes are:

• menu appears only on click, not when hovering
• menu positions are now correct for RTL languages and do not go off screen any more
• Narayam and Webfonts support the Kannada script for the Tulu language on the Incubator

There are also some smaller fixes among them the change of the autonym for the Veps language to “Vepsän kel”.. The full details for all the changes is at revision 106667.

Thanks,
Gerard Meijssen
Internationalization / Localization outreach consultant

With a new sprint, new functionality for MediaWiki is identified to be deployed in two weeks time. There is room for dealing with issues to do with Narayam and WebFonts. Many of the new activities have to do with documentation, translation and feedback.

The sprint backlog in Mingle (user: guest password: guest)

What we hope for is that the feedback functionality that is now part of MediaWiki can be used to ask for feedback of MediaWiki features. It is obvious that the Wikimedia Localisation team cannot support all the 300+ languages that have their projects or exist in the incubator. What we can do is process the information we get from our language support teams. Figuring out how to do this is one of the goals for this sprint.

The use of Narayam and WebFonts will be helped a lot with documentation; “where to find that character on this keyboard mapping” or “what does an international keyboard look like” are questions looking for an answer. Determining how to document and what to translate is not all that obvious. With keyboard maps and fonts distributed as part of MediaWiki documenting on “the” wiki does not scale to other Wikimedia wikis and, MediaWiki wikis outside the Wikimedia Foundation are as much in need of documentation. When people start using MediaWiki because of such language support features we accomplish real support for a language.

For this sprint, these questions are looking for an answer and in the mean time the Translate extension will gain these new features:

• Documents that need translation can be grouped together; for instance all the Fundraiser messages or Wikimedia reports
• Documents can be marked as no longer needing translation
• Changes to the state of documents and translations will be logged and the log will be available for viewing
• Depending on the state of a document or a translation, attention can be drawn when there is a need for activity

User documentation needs translation and hopefully many of the algorithms used for the localisation of MediaWiki at translatewiki.net will equally apply for user documentation. Life will become a lot easier for all those people who administer MediaWiki and have only a basic understanding of English. We hope to deliver this in one of our future sprints.

Thanks,
Gerard Meijssen
Internationalization / Localization outreach consultant

When you make use of any of the projects of the Wikimedia Foundation, you are expected to abide by its terms of use. These terms of use provide you with practical and legal terms of reference. The original version is in English but we do know that for many in our communities English is not a language that will convey any message.

For this reason the translation of the terms of use is essential. There is a recurring need for the translation of texts and this translation work is done by volunteers. This work is really important to get our message out, making it as easy and efficient as possible is one way of showing our appreciation for the work that these volunteers do.

Translation is made easy because the user interface will just work in the language set in the preferences.

Details like the languages that have a translation are all shown in the language set in the preferences.

Even with the best preparation, a text may change over time. As the text is broken into separate fragments that need translation, it is possible not only to indicate what needs to be revisited by a translator, it is also possible to indicate the changed text in pink in the readable text.

Volunteers are masters of their own time. They choose how much they want to do in one go. Making the translated text immediately available is one way in which we show appreciation for the work that is done and, at the same time it is an invitation to other volunteers to complete the work that still needs doing.

With all the Translate functionality in place, we expect that it is easier to translate, we hope that more people will be involved and that important texts like the “terms of use” will become available in as many languages as we can find translators for.

Gerard Meijssen
Internationalization / Localization outreach consultant

Earlier today the folks over at Google provided an update on their progress using Translation Toolkit with volunteers and translators to improve the article count in smaller language versions of Wikipedia, including Arabic, Gujarati, Hindi, Kannada, Swahili, Tamil and Telugu.  Google is a passionate believer in the need to translate and bring more high quality works of text to less-represented languages on the web.

Michael Galvez, a Product Manager from Google, presented the recent findings of these efforts at this year’s Wikimania in Gdańsk – which wrapped up on Sunday, July 11 of this year.

From Michael’s post:

We believe that translation is key to our mission of making information useful to everyone. For example, Wikipedia is a phenomenal source of knowledge, especially for speakers of common languages such as English, German and French where there are hundreds of thousands—or millions—of articles available. For many smaller languages, however, Wikipedia doesn’t yet have anywhere near the same amount of content available.

Google is reporting an increase of about 16 million words so far due to the efforts of local volunteers and translators using the Translation Toolkit.  In Hindi Wikipedia these efforts have resulted in an increase in size of about 20 per cent. They continue their work directly with volunteers from these language projects, and continue to expand the capabilities of the translation toolkit in new languages.

A big thanks for the ongoing efforts of the volunteers and translators, and to Google for continuing to invest time and resources in this great translation system.

Jay Walsh, Communications

Wikimedia projects support over 270 languages. This amazing global reach is powered by volunteers who translate not only the contents but also text used in MediaWiki so that localized wikis can be easily navigated and operated by users in their local language. Translatewiki.net is the amazing translation engine which not only supports Wikimedia projects but other open source projects. Siebrand and Nike are leading this translation platforms.

The user experience programs at Wikimedia Foundation is also benefited from translatewiki.net and translation volunteers. The usability beta has been completely translated into thirteen languages and twelve languages are 99% complete. These stats can be found at the translation completion status page for the usability extension by courtesy of GeardM.

The usability beta is planned to be switched to be the default interface in April. Additional translation boost for languages which are not fully translated will improve the usability of the new interface greatly.
GerardM had a great example of the interface in Nepali, whose localization is not complete, in his blog.

Translation help for such as Indonesian, Greek, Thai, Arabic, Hebrew, Italian, Sinhala, Korean and much more, are greatly appreciated.

With six projects in over 250 languages, multilingual communication and content translation are big priorities for us. That’s one reason I was excited to go to the Open Translation Tools 2009 conference and be in the same room with 80 other translators, content providers and developers all working in the open translation space. Another reason is that the conference was held in Amsterdam in the old city center, in a beautiful venue right by one of the canals.

We have some amazing opportunities to collaborate with folks on other projects, from translation memory based systems like that in use by the World Wide Lexicon to source code string repository interfaces like Transifex. As one person put it, the perfect testbed for crowd-sourced translation is Wikipedia; if we can’t make it work there, where can it work? I also had a chance to talk with Gerard Meijssen and Siebrand Mazeland about new ways to facilitate tighter integration with translatewiki.net and to encourage more projects to make use of the translatewiki facilities. It should be a really productive year.

Folks told me to go visit the Van Gogh Museum, so I was dismayed to find that they don’t allow photography. However, the Wiki Loves Art NL project, organized by the NL Wikimedia chapter, had reached an agreement with the museum to allow two small groups in for photographs, during the week I happened to be there! So, come Tuesday morning, I was one of 20 lucky Wikimedia community members and photojournalists to be given private access to the Van Gogh collection. Some photos from the group are already available on the flickr group from which they will be uploaded to the Commons.

Right after the conference I went to the first two days of the OTT book sprint, which had as its goal the production of a comprehensive manual for beginner volunteer translators of open content with open tools. Once again we were in an awesome venue (see the picture; we were in one of the turrets!) and under the expert guidance of Adam Hyde we got a huge amount of content generated in just a few days.

On the last day I skipped town to go visit a colleague on one of the Wikimedia projects; we’ve worked closely together for over two years and had never met face to face. Perhaps that was the most important part of the whole trip: bringing our virtual community into the real world one person at a time.

Today Google is announcing the release of Google Translator Toolkit, a new application that extends their well known translation tool, Google Translate.  The Tool kit may change the way Wikipedia grows in other languages (from Google’s announcement today):

At Google, we consider translation a key part of making information universally accessible to everyone around the world. While we think Google Translate, our automatic translation system, is pretty neat, sometimes machine translation could use a human touch. Yesterday, we launched Google Translator Toolkit, a powerful but easy-to-use editor that enables translators to bring that human touch to machine translation.

Google Translator Toolkit allows users to help the system learn adaptively – and it has built-in functionality that will allow rapid translation of pages from Wikipedia.  Readers can correct mistakes, add context, and generally improve the translator’s ability to provide stronger first drafts of translations. This is a tremendous step towards free culture and the expansion of free knowledge on behalf of Google.

Volunteers at Effat University in Saudi Arabia have been working with Google to translate over 100,000 words into from the English Wikipedia into Arabic to help build the Toolkit and pave the way for further translations of Wikipedia content, a strong showcase for the Toolkit (more from Google):

These articles were among most widely searched articles throughout the Middle East, and they were either previously unavailable in Arabic or they were short relative to the English article. We are now reviewing and posting these top articles back to Wikipedia, in order help to make Wikipedia even more useful in Arabic. As Saudi Arabia’s HRH Princess Lolowah Al-Faisal said, Effat worked with Google “to solve the problem of making a huge amount of online information available to Arabic speakers, all over the world.”

You can try out the toolkit here.  Google has also posted a video to provide a quick tutorial. We look forward to seeing even more active translation within Wikipedia and beyond over the coming months.

Jay Walsh, Head of Communications