Wikimedia blog

News from the Wikimedia Foundation and about the Wikimedia movement

Posts Tagged ‘Translate extension’

Updates from the Language Engineering Google Summer of Code projects

Google Summer of Code (GSoC) 2013 is well underway on the coding phase. Four projects this year are related to various aspects of MediaWiki and Wikimedia internationalization initiatives. On completion of these 4 projects, we expect to present:

These projects are being mentored by members of the Wikimedia Language Engineering team along with members from the WMF Mobile and VisualEditor teams. In this post, we touch base with each of the projects about the challenges that they have faced so far and on their accomplishments.

MediaWiki VisualEditor internationalization and right-to-left languages support

A screenshot of a draft version of the VisualEditor language inspector.

Moriel Schottlender is working on adding better support for non-English languages to the VisualEditor. Her project consists of two main parts. The first is triaging and fixing bugs in handling right-to-left text reported by volunteer editors who test the currently deployed version of the editor in languages such as Arabic and Hebrew. She has already fixed several bugs such as moving the cursor in the correct direction using the arrow keys and adapting the design of VisualEditor’s dialog boxes to right-to-left layout. The other part of the project is developing a “language inspector”–a tool for setting the language of a piece of text in an article. This is needed very frequently in Wikipedias in all languages to set properties such as font, size or direction of a foreign name or quotation. Nowadays it is done using a multitude of templates and HTML tags, and Moriel’s project will make it easy and unified.

jQuery.IME extensions for Firefox and Chrome

Part of Project Milkshake, jQuery.ime is an input method library. Making a good start, Praveen Singh has already implemented working jQuery.ime extensions for both Chrome and Firefox. Rather than loading all input methods at once, input method scripts are loaded only when the user selects a particular input method. The jQuery.ime and jQuery.uls upstream projects were added as git submodules in the extensions. This will provide a way to synchronize the extensions with the upstream projects in the future by simply updating the respective submodule. Universal Language Selector (ULS) has been successfully integrated in the extensions, thus providing the users with an easy way to choose among different languages. The extension remembers a user’s most recently selected languages and their corresponding input methods, and offers an easy way to choose among those languages.

Language Coverage Matrix Dashboard

The Language Coverage Matrix dashboard was a project conceived during the last Open Source Language Summit held in Pune, India earlier this year. The project began as a shared spreadsheet and over the next few months, the data was filtered to uniquely identify the internationalization support status for each language and its variants. The dashboard will provide an interface to search this data and present visual data representations. The test instance set up by Harsh Kothari on wmflabs, showcases the search features. The spreadsheet data has been ported to a MySQL database. Plans for the coming few weeks include additional query implementation, code refactoring and start of the visualization representations.

Phone app for MediaWiki translation

The Translate extension is used for translating MediaWiki content. This project will bring the convenience of this widely used extension as an Android app. The iPhone app created by the student Or Sagi, is already available for download and testing. The similarly designed Android app will provide features for translation and proofreading. Due to conflicts with examination schedules, major work on this project will effectively start from late July.

Getting more updates

More details about the progress of each of these projects can be found on the project home pages. The students and mentors also meet up every week for demos. Please let them know if you’d like to be part of any of these sessions.

Runa Bhattacharjee
Outreach and QA coordinator, Language Engineering, Wikimedia Foundation

A new translation home page, the Maven Program and other updates from Language Engineering

The Wikimedia Language Engineering team continued to develop additional features for Translate UX (TUX) and to fix bugs, including a number of critical bugs that affected Microsoft Internet Explorer. TUX has now been deployed on Wikimedia sites and on The team also launched the new outreach program, called Language Mavens, and conducted an office hour.

The view after the user logs in to the new home page of This is currently in development.

The view after the user logs in to the new home page of This is currently in development.

Redesigning the main page of

As part of the original specifications for TUX, the main page is being redesigned. The layout will now include a set of tiles for the project groups that will contain the projects’ logo and statistics. The links conveniently placed on the tiles can be used to access the project messages for translation and proofreading. Once logged in, users will be presented with summarized statistics of their recent activities.

Significant changes are also planned for the account sign-up form. Along with features that will allow newly signed-up users to familiarize themselves with the translation workflow, it’ll make the process of getting the translation permissions smoother. The page will also include artwork to depict cultural diversity from around the world. The main page is currently under preparation, but the special page can already be accessed on

Language Mavens: The new outreach program

Language Mavens, the new outreach program for the Language Engineering team, was launched to provide better support to the various language communities within Wikimedia projects. The program was announced during the monthly office-hour (read the logs). After a meeting with the initial group of participants, the pilot phase is now underway. The program aims to regularly connect with the language communities across the Wikimedia projects to get feedback about the user experience and any improvements needed in the language support features. To optimize the internationalization tools and workflows, the program will also facilitate participation in activities such as bug triages and testing days. The team will hold regular meetings with the Maven team members. The program is open for participation, and new members can sign up online. To get more details about the program, you can read the program’s description and write to runa at wikimedia dot org.

Up next

For the next development sprints, the team will continue to work on the projects mentioned above, and also devote significant efforts on redesigning the Universal Language Selector (ULS) interface based on the design review document. The Language Engineering team will host a community bug triage session on April 24th, 2013 at 17:00 UTC. The team also invites students participating in Google’s Summer of Code 2013, to work with them on several internationalization projects.

To know more about our projects and ways to participate, please find us on the IRC channel #mediawiki-i18n (Freenode) or write to runa at wikimedia dot org.

Runa Bhattacharjee, Outreach and QA coordinator, Language Engineering

Language Engineering Sprint Update: Translation User Experience improvements, testing and coverage

The Wikimedia Language Engineering team completed its recent development sprints with a focus on feature completeness of ‘Translate User eXperience’ or ‘TUX’ for deployment and also made preparations for its new community outreach project. Below are some of the highlights from the sprint.

Work is underway on the design of the new main page for

Work is underway on the design of the new main page for


Translate Editor – TUX, has been deployed: The Language Engineering team has been blogging on improvements to the Translate Extension which has now been deployed to WMF sites and been enabled as the default editor on Issues encountered while using the new editor can be reported via Bugzilla. More details about TUX’s design features can be found in our previous blog post.

New Language Outreach Program: A new outreach and support program to facilitate feedback from our language wiki projects is also currently in development. The program would facilitate focused feedback about the tools being developed and reaching out with solutions to the larger communities working on Wikimedia projects in various languages. The pilot phase is scheduled for launch in the coming weeks and an announcement with the details of the program will be shortly made.

Updates to the MediaWiki Language Extension Bundle (MLEB): In other news, Amir Aharoni announced the release of the new version of the MediaWiki Language Extension Bundle (MLEB). Besides development updates to TUX, version 2013.3 of MLEB includes bug fixes to the Universal Language Selector (ULS) as well as new fonts for Hebrew, Javanese and Arabic. Last but not least, a Marshallese input method has been contributed to jQuery.ime by Nick Doiron.

Testing plan for language tools: A preliminary outline of a testing plan for all internationalization tools currently maintained by the team was completed. Guided by earlier discussions with the Fedora Localization Testing Group (FLTG), the initial draft includes setup of test environment, preparing test scenarios, collecting feedback and analyzing results.

Preparations for visualization of language coverage information: Work also continued on the Language Coverage Matrix, a collection of data about the availability of language tools for different languages in Wikimedia projects. Currently, the focus is to prepare a technical specification for automated presentation and access to this information.

Event participation and other news: Siebrand Mazeland represented the Wikimedia Language Engineering team at the Internationalization and Localization Conference organized by Lingoport in Santa Clara. (More details: presentation slides, and talk recording)

The ongoing development sprint will focus on creating a new design for the homepage, launch of the pilot phase for Language support outreach program, and publication of the Language Engineering roadmap for the next fiscal year 2013-2014. The Language Engineering team is also looking to hire JavaScript and PHP engineers with deep experience in i18n and l10n technologies. Additionally, a few of the projects that are open for participation have been listed here.

The Language Engineering team is available to answer any technical questions you may have about the tools it develops. You can join us at our monthly office hour scheduled this month on April 10, 1700 UTC and 1000 PDT or find us on at #mediawiki-i18n. Logs from the last office hour held on March 13, 2013 can be found here.

Runa Bhattacharjee, Outreach and QA coordinator, Language Engineering

Redesigning the Translation experience: An overview

The Wikimedia Language Engineering team has been regularly reporting updates about improvements to the Translate editor, as part of the “Translate User eXperience” project, or “TUX”. Pau Giner, the team’s UX expert, has also conducted online sessions to talk about these features. If you have missed these updates, here is a summary of what we are changing about the way the Translate editor is used.

Translate UX main editor screen with Spanish translations in List view

The main editor screen of Translate’s new version, with Spanish translations in List view.

Translate is a MediaWiki extension that is used for translating software and wiki pages. Besides providing translations through the web-based editor and proofreading features, it also supports export and import of gettext files for offline translation. The editor provides various features to assist in translation, such as:

  • Message documentation, also known as “context”;
  • Suggestions from translation memory and machine translation;
  • Checking translations for common syntax mistakes;
  • Translation status of messages.

Originally created by Niklas Laxström, this extension has grown in features through contributions made by other contributors, as well as by the Wikimedia Language Engineering team. The extension uses a continuous development model and, if you use the extension on a wiki you administer, you are encouraged to update it periodically using the MediaWiki Language Extension Bundle (MLEB).

The workflow and features for Translate were recently redesigned to provide users with an improved experience. The development was done based upon the designs in the workflow specification document. This included changes in navigation, editor look and feel, translation area, filters, search, and color & style. Here are some of the notable new features and changes:

Editing Modes: The translation editor will now provide two translation modes and one proofreading mode. For translation, the user will be able to choose between the ‘List’ view, more suitable for smaller messages, or the ‘Page’ view, designed for longer pieces of text like paragraphs of a wiki page. The proofreading mode will allow users to view translations by other users and mark their accuracy. Although users can view the messages translated by themselves in this mode, they cannot mark them as accepted.

Message status-based filtering: Users will have the option to select and only view messages that match a filter, depending on their status. In the editor, users can choose an appropriate filter to quickly access ‘Translated’, ‘Outdated’ or ‘Untranslated’ messages in translation mode, and ‘Translated’, ‘Outdated’ and ‘Unproofread’ in proofreading mode. Translations marked as ‘Outdated’ (equal to the jargon term “fuzzy”) need attention, for example because the source message has changed.

Message editor and translation aids: The messages in focus are shown within an editing area that is divided into two separate sections: one for translation, and the other for translation helpers, like context documentation, suggestions from previous translation and external translation services. The layout aims to make optimal use of available space and also provides users with the additional option to focus better on a message by expanding the size of the editing area to the entire width of the editor. The navigation to the next message, the ability to save drafts and the display of warnings make the translation process more fluent. Development of some exciting features for improving context-related translation aids is also on the cards.

Search and edits: Users can search translatable strings using the search field at the top of the edit section. The search results are displayed within various categories like ‘source’ or ‘translated’ messages. An additional overview displays the languages and message groups where they occur and users can further filter them based on the sub-groups. Users will be able to directly go into ‘Translation mode’ to make changes to the messages in the search results. A navigation arrow can bring them back to the list of results.

Not all of these features are available on Wikimedia wikis yet, but they will be soon. The current development version is available on If the new editor is not visible, appending “&tux=1” to the URL will enable the new features. Appending “&tux=0” will disable them.

While redesigning Translate’s User experience has been a significant project, development is continuously carried out to make the extension even better to use. And for this, we are always looking for valuable feedback from our users. Bugs and features requests can be filed through bugzilla; additionally, one can write to me at runa at wikimedia dot org with their feedback and suggestions.

Runa Bhattacharjee, Outreach and QA coordinator, Language Engineering

New release of the MediaWiki Language Extension Bundle, and other updates

Highlights from the latest development sprint of the Language Engineering team include the release of a new version of the MediaWiki Language Extension Bundle, and continued progress on Translation User Experience (UX) and the Language Coverage Matrix.

Screenshot for the redesigned proofread view for the Translate extension showing translations in Georgian.

Screenshot of the redesigned proofread view for the Translate extension showing translations in Georgian.

Design and development improvements continued for Translate UX, also known as TUX. A preliminary implementation of the Proofreading feature (per the specifications in the design document) includes features to view the messages adjacently, adding clickable markers for proofreading and switching between proofreading and translation mode. Pau Giner presented these updates at an open session and also invited users to join the ongoing usability tests.

Amir Aharoni announced the release of MediaWiki Language Extension Bundle (MLEB) 2013.02. Besides localization updates in most of the components within MLEB, more features were added to Translate UX. The Universal Language Selector however had to be rolled back to the 2012.12 version to ensure compatibility with MediaWiki 1.20.

The Language coverage matrix document was updated to include more information about web fonts and input methods that are currently available for use in MediaWiki and Wikimedia projects. The document aims to provide an overview of the internationalization and localization support in languages across Wikimedia projects.

As part of the ongoing effort to use a CLDR-based, data-driven approach for internationalization features, plural rules for many languages were analyzed and custom rules were removed for a few languages.

The Language Engineering team will be hosting an IRC office hour session on Wednesday, March 13 2013 on in #wikimedia-office (FreeNode server) at 17:00 UTC. Topics will include discussion, questions, feedback about current projects, open bugs and projects planned for the next sprint.

Runa Bhattacharjee, Outreach and QA coordinator, Language Engineering

Language engineers improve translation tool and meet with their peers

Quem não arrisca não petisca — a Portuguese proverb

During their latest development sprint, the Wikimedia Language Engineering team conducted extensive review and testing of the Translate extension, and participated and contributed to two major open source events in India: a core developers Language Summit and GNUnify.

add caption here

User experience improvements to the Translate tool will notably make it easier and more pleasant to translate content on Wikimedia sites that use it.

Translate Editor Updates

Progress continued on enhancements to the MediaWiki Translate extension. Further testing on the usability of the translation editor, search feature, and prototype of the advanced editing features were conducted by Pau Giner with five users from four different countries. The prototypes were tested in a great diversity of languages including Nepali, Chinese, Tetum, French, Breton, and Finnish. Based on this feedback, changes to the style and specifications for the prototype were made. Details about the individual tests can be found in the final report for this round of testing.

Community Participation

The Language Engineering team participated in the Open Source Language Summit and GNUnify, both held in Pune, India. The Open Source Language Summit, co-organized by the Wikimedia Foundation and Red Hat, consisted of work-sprints that focused on internationalization (i18n) and localization (l10n) features, font support, input method tools, language search, i18n testing methods and standards. More information about the event is available in the detailed event report.

The team also participated in GNUnify 2013, held at the Symbiosis Institute of Computer Studies and Research, in Pune. Besides presenting about the various projects that the team is currently working on, a translation sprint on was also organized, as well as a workshop on jQuery.IME and a BoF session to discuss issues related to Wikimedia projects in Indian languages. Details of the accomplishments from the sessions at GNUnify 2013 can be found in the event report.

Other Achievements

Additionally, some changes to MediaWiki core were backported to support the newer version of the Universal Language Selector on MediaWiki versions 1.19 and 1.20. As there is no released maintenance version yet, MediaWiki Language Extension Bundle (MLEB) users are advised to remain on MLEB version 2012.12.

Focus for the next sprint

For the next development sprint, the team will work on more features for the Translate extension, like the proofreading mode and further improving the user experience. In addition to this, focus will be on putting together the language coverage matrix as a reference for the status of language support on MediaWiki, MediaWiki Extensions and Wikimedia projects.

Runa Bhattacharjee, Outreach and QA coordinator, Language Engineering

Inching towards enabling our improvements to the Translation user experience

Lel the tacho pirrow, an’ it’s pars kaired — A Romani proverb

The Wikimedia Language Engineering team just completed its most recent development sprint, to introduce a new iteration of  the Translation Editor within the Translate Extension, and include features to make it more satisfactory as a translation workspace. The primary focus during this sprint has been to make the editor ready for production use. Some members of the team also attended FOSDEM 2013 in Brussels.

Translate interface features & enhancements

Paste Source Text  — Often found in translation editors, this feature allows for the source text to be easily copied over into the translation edit box. It’s now available in Translate and is particularly helpful when large portions of the source messages can be reused in the translation.

Message Documentation Display — Details about the messages within a project for translation can now be seen for all messages in a page, by picking the special “Message Documentation” language in the “Translate to” selector. This advanced option allows translators to view and evaluate the context for the messages that they are translating and also to see all the messages that were not documented yet.

The Message Documentation window of the MediaWiki Translate extensionprovides context for individual messages being translated.

The Message Documentation window of the MediaWiki Translate extension provides context for individual messages being translated.

Translation Editor UI  — The other enhancements that help translators to quickly review messages include:

  1. Unchanged translations marked as “outdated” can be marked as suitable for use using the Confirm Translation button.
  2. When translating a message, the translation aids of the subsequent message gets preloaded to avoid any delay during navigation.
  3. Groups of messages, especially within Translation Pages with longer content, can now be set to a different state through a button click on a redesigned interface. This feature helps in identifying the Pages that can be pushed for publication.
  4. Machine Translation suggestions from Apertium, Microsoft, and Yandex can now be dynamically presented for each message on the editor.

Besides the above, Search and Translation Editor were cross-integrated for translators, to edit Translations directly from the page displaying search results.

Search and Translation Editor were cross-integrated for translators, to edit Translations directly from the page displaying search results.

Search and Translation Editor were cross-integrated for translators, to edit Translations directly from the page displaying search results.

Pau Giner conducted a walkthrough of Translate user experience improvements, demonstrating the current state of development and the upcoming features for this extension.

Translate API changes — Changes to the Translate API now provide more information for the developers via the Web API, to help them implement customized translation interfaces.

During the development cycle, the team also engaged with the larger community to gather feedback about the new features through usability tests.

In other good news, jQuery.ime was successfully implemented on the Koha Library management system (v. 3.10) by Indranil Dasgupta. Also, do see this wonderful video about jQuery.ime by Chris Forno that blew us away.

Focus for the next sprint

Further enhancements to Translate continue to be the main focus for the next sprint. This includes review and testing of the latest designs. The Language Engineering team hopes to have more interaction in this regard at the Open Source Language Summit (organised and hosted in collaboration with Red Hat) and at GNUnify in Pune, India.

Runa Bhattacharjee, Outreach and QA coordinator, Language engineering

Universal Language Selector now has Input Methods

The Language Engineering team at the Wikimedia Foundation works on a set of tasks every two weeks. This post is about the team’s accomplishment over the past two weeks. 

Have you ever sat at a computer in a foreign country, and wondered how you were going to enter text in your language using a keyboard with a different alphabet?

“Input methods” are interfaces that allow users to enter text in a script different from the one used on their keyboard. On some Wikipedia versions (like wikis in Indic languages), such a tool has been available through the Narayam extension.

As part of Project Milkshake, this feature has recently been exported to a JavaScript library (a bundle of code, called jquery.ime) so that it could be reused by other web developers.

Another language-related tool, the Universal Language Selector (ULS), allows readers of Wikipedia and its sister sites to easily pick the language of their choice for the website’s interface.

Over the last two weeks, we’ve integrated the input methods’ functionality directly into the Universal Language Selector: it now comes with a large set of input tools that users can use to input text in non-latin languages.

The integration of the two tools makes the interface more consistent and usable when it comes to choosing languages in which to read (“display”) and to write (“input”) on the site: both settings are located in the same dialog of the Universal Language Selector.

When selecting a language in which to write, it’s possible to set an accompanying preferred input method for that language, if available. When input methods have been assigned to different writing languages, switching between languages in the menu will automatically change to the preferred input method for that language.

Other language engineering news in brief:

  • The Language Engineering team will be in India during the second week of November to participate in the OpenSource Language Summit in Pune, and the Wikimedia DevCamp in Bangalore. For new volunteers who want to get started contributing to our tools, we’ve prepared a list of bugs that you can work on at these events with our support.
  • We’ve also worked on finalizing the development plan and features for Translate UX improvements, which were identified by user testing with volunteer translators to improve translation efficiency.
  • We’ve worked on how to get metrics on the impact of our tools through URL-based usage data gathering. Feedback is welcome.
  • We’ve fixed some bugs related to the ULS and gender support in MediaWiki and MediaWiki extensions.
  • The Narayam and Webfonts extensions were deployed to Wikimedia sites in Marathi; Narayam was also deployed to sites in Amharic.
  • An early stable version of ULS was deployed on Wikidata; this first use on a production site revealed a few bugs that were fixed. It will be updated to the latest stable version periodically.

Srikanth Lakshmanan
Internationalisation/Localisation Outreach / QA Engineer

Designing for the multilingual web

User testing is essential for designing multilingual interfaces, even though it can be a time-consuming process: it ensures that the community of users are part of the design process. In this article, we share lessons learned by the Language Engineering team while designing features and interfaces that empower users to read and edit Wikipedia and its sister sites in many languages.

Designing user interfaces for the Wikimedia world comes with a lot of responsibility. To achieve our mission, we need to make sure we think of users with varying levels of technological expertise and language skills. While the internet can be a very friendly place for those who understand English, it could be like navigating the Greek Wikipedia to the 4.4 billion people who do not.

While designing the user interface (UI) for language tools like the Universal Language Selector (ULS) and Translate extension, we needed to make sure it could be understood and used by those who use the internet in languages other than English. We had to create early representations of the interface, link them together to create interactive prototypes and test them with users. Each of these steps presents various challenges in a multilingual environment.

Design tools generally have poor support for non-Latin scripts. Moreover, creating screens and prototypes in languages that you don’t speak is hard. But since the world needs these language tools, we can’t wait for our design software to improve, we just need to figure out our own ways to get things done.

Creating multilingual mock-ups

UI designers make layout comps early in the process to illustrate how the interface elements and content will be arranged.

While designing the ULS (that will display a massive list of languages), the only way to understand the effectiveness of the layout was to simulate the end result with all the language names. Common graphic design suites are not optimized to manage large number of text elements and have issues when working with non-Latin fonts.

Our workaround: After some exploration, we realized that the most painless way of creating comps that have multilingual text is to render them outside the design software:

  • Create the UI layout using your design tool;
  • Use a template language like mustache to include placeholder text within the mockup and export them as SVGs;
  • Create a translation text file to replace the placeholder text with strings in your language;
  • Perform a string replace in the SVG and rasterize it with inkscape using a script.

There is a neat illustration of the entire process in this video by Pau Giner. This process allowed us to quickly experiment and test comps in many languages by giving the text file to a translator.

Making interactive prototypes

The best way to understand if a design is effective is to observe a user using it. The fastest way to do this is to make click-through prototypes that simulate a workflow. When our multilingual comps were ready, the next task was to package them and link them by hotspots. Most of the popular tools to do this are not free. After scouting around for free alternatives, we chose a Firefox extension called Pencil because it:

Translate extension prototypes in Malayalam

  • imports raster and vector images, including copy-pasting from other design tools;
  • features master pages and a component library to reuse graphic elements;
  • has rich text support;
  • exports to a single HTML which simulates a web page experience;
  • is free and open-source.

It fulfills our requirements, even though there are a few annoying quirks in the interface which could be improved. Check out this interactive presentation of the ULS that was created using Pencil.

Remote user testing

Once our prototypes are ready, it’s finally time for the real test, with users from parts of the world where the primary language is not English (roughly 95 percent of the world’s population). Planning the logistics and schedule of remote user testing can be tricky, so here are a few key points to keep in mind:

Remote user test

  • Create a pool of volunteer user testers early in the design process. Getting a tester is usually a hit and miss, so it helps to have a volunteer base that can be easily reached when needed.
  • Tell users what the test is about. Most users will not know what happens in a user testing session and may be afraid to volunteer. Who likes to be tested anyway? We created this guide to better communicate what the sessions were about.
  • Schedule the tests initially and ask for a confirmation. We found that testers may not be available at the scheduled time and they often want to reschedule. Stay friendly and accommodating, as these people are providing you with valuable feedback.
  • Observe using a platform that meets your requirements. We found Google+ Hangouts to be the service of choice due to its ease of use across operating systems. As a bonus, it can automatically create a YouTube video of the whole session.
  • Inform the tester beforehand on privacy issues. If you want to share the observations publicly, make sure the tester knows and has agreed to those terms.
  • Have fun. Keeping the mood light with initial introductions will help to make the tester feel comfortable and give more feedback.

If you are curious, you can watch this video from our latest test sessions of the ULS to understand how we do it.

We are designing and developing your software, so keep the feedback coming!

Arun Ganesh and Pau Giner
UI/UX Designers, Language Engineering Team

Internationalisation team introduces translation memory and plan for language teams

The Internationalisation/Localisation (i18n/l10n) team at the Wikimedia Foundation works on a set of tasks every two weeks. This post is about the team’s accomplishment over the past two weeks.

You can also watch the 15 minute demonstration and check the slides.

Language Teams
Mediawiki supports over 350 languages. Supporting languages goes far beyond providing a localised interface. It includes ensuring that the overall experience of a language in which the user reads and contributes to Wikipedia (or any wiki running MediaWiki) is the same as it is to an English user. It is impossible to support without the help of volunteers in the respective languages. We have tried filling this gap through Language Support Teams. We are now starting an initiative to form and build strong language teams and have published a detailed plan. Please do let us know what you think about it.

Translation Memory on Wikimedia servers

The Translate extension is currently deployed on Meta-Wiki, and a few other Wikimedia wikis to facilitate the translation of their content. In order to make translations faster and more consistent, a shared translation memory service has been enabled in the extension, which will provide translation suggestions from past translations of similar text.

Universal Language Selector Update

ULS with Common languages listed

ULS with Common languages based on geolocation and “accept languages” listed

The Universal Language Selector (ULS) has a new top section in the default view. It now lists a set of “Common Languages”. They include languages spoken in your region (determined by geolocation), preferred languages from your browser (“Accept-Language”) and previously used languages. For many users, this should minimise the need to search for their language of choice in the list. The ULS now integrates with MediaWiki preferences, and performance was improved by using lazy loading.

Milkshake Update

jQuery.i18n, the internationalisation messaging framework library, saw the addition of support for gender, plural and grammar. All the language-specific rules that exist in Mediawiki are now available in jQuery.i18n. The framework is also built with scope for adding more extensible attributes in addition to the default ones. It supports lazy loading of translations.

Other accomplishments

  • Translation UX tests continued, and led to improvemenents of the design prototypes for the translate extension, including new translator captchas. You can watch a short video about the project.
  • We investigated solutions to support Indic languages on mobile platforms.
  • We organized a bug triage on i18n issues.
  • Apart from the usual bug fixes, a lot of Right-to-Left bugs were also fixed in the experimental PageTriage and ArticleFeedback v5 extensions, as well as in the veteran WikiHiero extension and core MediaWiki.

Srikanth Lakshmanan
Internationalisation/Localisation Outreach / QA Engineer