Wikimedia blog

News from the Wikimedia Foundation and about the Wikimedia movement

Features

The alpha version of the VisualEditor is now in 15 languages

This post is available in 6 languages: English 100% Deutsch German • Français 7%Español 7%Svenska7%日本語 7%На русском языке 7%

English

Today the Wikimedia Foundation launched an alpha, opt-in version of the VisualEditor to fourteen Wikipedias, which follows our release to the English Wikipedia in December. The VisualEditor lets editors create and modify real articles visually, using a new system where the articles they edit will look the same as when one reads them — like writing a document in a word processor.
The VisualEditor is now on 15 language Wikipedias

The VisualEditor is now on 15 language Wikipedias

Editors on fifteen Wikipedias – Arabic, Chinese, Dutch, English, French, German, Hebrew, Hindi, Italian, Japanese, Korean, Polish, Russian, Spanish and Swedish – can now get an idea of what the VisualEditor looks like in the “real world”, so they can give us feedback about how well it integrates with their current editing processes. We also want to get their thoughts on what aspects of development we should be prioritizing in the coming months.

The editor is still at an early stage and is missing significant functions, which we will address in the coming months. Because of this, we are mostly looking for feedback from experienced editors; the alpha VisualEditor is insufficient to really give new volunteers a proper experience of editing. We don’t want to promise an easier editing experience to new editors before it is ready.

As we develop improvements, we will push them live every two weeks to the wikis, allowing you to give us feedback as we go, and tell us what you want us to work on next.

How can I try it out?
The VisualEditor is now available to all logged-in accounts as a new preference, switched off by default, on the fifteen Wikipedias listed above. If you go to your “Preferences” screen and click into the “Editing” section, it will have an option labelled “Enable VisualEditor.”

Once enabled, for each article you can edit, you will get a second editor tab labelled “VisualEditor” next to the “Edit” tab. If you click this, after a little pause you will enter the VisualEditor. From here, you can play around, edit and save real articles and get an idea of what it will be like when complete.

At this early stage in our development, we recommend that after saving any edits, you check whether they broke anything. All edits made with the VisualEditor will show up in articles’ history tabs with a “VisualEditor” tag next to them, so you can track what is happening.

How can I help?
It’s vital that our software is available in the native language of as many of our volunteers as possible. If you speak one of these languages – or any of the other 280 languages that we support, like WelshPunjabiUrdu or Scots Gaelic - please consider looking at the translations and helping us improve them!

We would love your feedback on what we have done so far — whether it’s a problem you discovered, an aspect that you find confusing, the areas you think we should work on next, or anything else, please do let us know.

James ForresterProduct Manager, VisualEditor and Parsoid

(more…)

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 translatewiki.net. 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 translatewiki.net. This is currently in development.

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

Redesigning the main page of translatewiki.net

As part of the original specifications for TUX, the translatewiki.net 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 translatewiki.net.

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 translatewiki.net

Work is underway on the design of the new main page for translatewiki.net

 

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 translatewiki.net. 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 translatewiki.net 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 irc.freenode.net 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

Breaking through walls of text: How we will create a richer Wikimedia experience

Wikimedia consists of many projects, Wikipedia most notable among them. However, the name “Wikimedia” suggests a world beyond text. Indeed, Wikimedia Commons, our repository of freely-licensed media files, already contains more than 16 million images, sound files, and videos.

Well, mostly images. Right now, there are fewer than 30,000 video files, and fewer than 170,000 audio files. And while Wikipedia articles are often richly illustrated, they still share the old-school feel of a print-based experience. Projects like Snow Fall by the New York Times show what an immersive reader experience can look like, with video elements prominently featured and blended into the core of the content. In contrast, Wikipedia articles rarely have videos, and if they do, those videos are usually very short and included at the bottom of the article.

Of course, well-written text forms the foundation of most high quality educational content.  Text is versatile, adaptable, accessible, efficient, and relatively easy to collaborate on.  It will form the core of the Wikimedia experience for a long time to come. Still, we can greatly improve the educational value of our sites by empowering everyone to share media, collaborate on improving that media, and using that media well throughout our sites.

In the last three years, Wikimedia has seen some very significant multimedia developments:

  • The Wikimedia movement has launched successful photo contests and competitions, notably the “Wiki Loves Monuments” competition, which was recognized as the world’s largest photo competition by the Guinness Book of Records. In the 2012 competition, more than 350,000 photos were taken by volunteers. It was organized by Wikimedia chapters and volunteers in 33 countries (see jury report).
  • Wikimedia chapters and volunteers have also formed partnerships into the cultural sector (e.g. museums, galleries, archives), resulting in hundreds of thousands of photographs, reproductions of paintings, and other media being made available on Wikimedia Commons.
  • Wikimedia Foundation has developed a number of enhancements and features focused on multimedia:
    • the Upload Wizard, an easy-to-use tool for uploading media files that’s been used to upload more than 2.2 million files to Wikimedia Commons;
    • upload features for the mobile web that make it easy to enrich any article requiring a photograph using a smartphone;
    • a new HTML5 video player with support for the open WebM video format and encoding of videos in multiple resolutions;
    • dedicated upload apps for iOS and Android are in development;
    • a feature to import photographs from Flickr (started as a Google Summer of Code project)
    • an experimental feature to upload files up to 500MB in size.

In combination, these efforts have already borne fruit. The number of contributors to Wikimedia Commons has increased significantly in the last 3 years.  In January 2010, only 13219 users had contributed at least one upload.  That number increased to 20161 users by January 2013.

At the same time, we haven’t invested enough. With the exception of the work of our mobile team, much of the above work has been done by one or two developers at a time, often in between other priorities or by engineers working as volunteers. There has never been a well-resourced team fully dedicated to multimedia engineering work at the Wikimedia Foundation. This is about to change.

The Wikimedia Foundation is hiring at least three engineers and additional product/design support to fully focus on improving the user experience for contributing, curating and reviewing multimedia. Right now, you can apply for the following positions:

Here are some of the key challenges for the new team:

  • further improvements to the upload experience. Contributing an image or video to an article while you’re editing should not require leaving the “edit mode” — it should be integrated with the editing process.
  • solidifying experimental features such as large file uploads;
  • improving transcoding features for video files to reduce the learning curve for video uploaders;
  • improving media search and discovery;
  • improving display of images, videos and sound files in Wikipedia articles, including a standard lightbox viewer for media embedded in an article and related media from Wikimedia Commons (building on some of the excellent submissions in our October 2011 Coding Challenge).

As we continue to provide new means for uploading media, we need to ensure that the Wikimedia community is empowered to curate and categorize the images. Curation includes removal of content that is out of scope or incorrectly licensed. To more effectively patrol content, the development of curation tools similar to the Page Curation feature developed for Wikipedia may become necessary.

Beyond Wikimedia’s category system, we will likely want to explore implementation of lightweight tagging systems, possibly in partnership with the Wikidata team.

As if this weren’t enough, the long term frontiers for multimedia include web-based editing of images, video and sounds, improvement for subtitle editing, browser-based audio recording features, and more.

In short, breaking through walls of text and creating a richer media experience for all our projects will keep the Wikimedia Foundation and the Wikimedia movement busy for many years to come. Please help us expand our library of freely-licensed educational media, and help us ensure it gets used effectively on the world’s fifth-most popular website.  Apply today.

Rob Lanphier, Director of Platform Engineering
Erik Möller, Deputy Director; Vice President of Engineering and Product Development

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 translatewiki.net. 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

Putting Commons contributions in your hand: mobile app uploads

Wikimedia Commons holds millions of images and thousands of audio and video clips, created by Wikimedians or contributed from the outside through free content licenses.

Many of the high-end photographs are created with professional-level equipment and post-processing software, but it’s often said that “the best camera is the one you have with you.” And in this day and age, that usually means the mobile phone.

Wikimedia’s Mobile Apps team has been putting together Android and iOS apps for Wikimedia Commons, allowing you to take photos on the camera you always have with you and upload them to Commons either immediately or at your leisure.

  • The Android beta is available now on the Google Play store.
  • iOS betas are distributed on an opt-in invite basis; sign up here on your iPhone or iPad and you’ll be notified when the next beta is ready. (Due to Apple restrictions, you won’t be able to install betas from before you signed up.)

At this stage of development we’re mostly looking for testers who are experienced Commons users — you’ll need to sign in to the app with an existing Wikimedia account — and hoping for feedback on the workflows and on any bugs we haven’t ironed out yet.

So far we’ve had 55 unique uploaders using the apps in the last two weeks (49 on Android, 9 on iOS, and of course a little overlap!), uploading images like these:

Taken with iPhone 4S

Taken with Samsung Galaxy S3

Our goal is to hit 1000 uploaders per month once we’re in full release.

As always, these tools are completely open source — you’re all welcome to follow our progress on the project page, file bugs, or even submit patches directly on GitHub (Android, iOS).

And for those using different mobile operating systems, we haven’t abandoned you. Photo upload support is in beta on the mobile web site as well… stay tuned for more information!

Brion Vibber, Lead Software Architect, Wikimedia Foundation


Footnotes

Parsoid: How Wikipedia catches up with the web

Wikitext, as a Wikipedia editor has to type it in (above), and the resulting rendered HTML that a reader sees in her browser (below)

When the first wiki saw the light of the world in 1995, it simplified HTML syntax in a revolutionary way, and its inventor Ward Cunningham chose its name after the Hawaiian word for “fast.” When Wikipedia launched in 2001, its rapid success was thanks to the easy collaboration using a wiki. Back then, the simplicity of wiki markup made it possible to start writing Wikipedia with Netscape 4.7 when WYSIWYG editing was technically impossible. A relatively simple PHP script converted the Wikitext to HTML. Since then, Wikitext has always provided both the edit interface and the storage format of MediaWiki, the software underlying Wikipedia.

About 12 years later, Wikipedia contains 25 million encyclopedia articles written in Wikitext, but the world around it has changed a bit. Wikitext makes it very difficult to implement visual editing, which is now supported in browsers for HTML documents, and expected by web users from many other sites they are familiar with. It has also become a speed issue: With a lot of new features, the conversion from Wikitext to HTML can be very slow. For large Wikipedia pages, it can take up to 40 seconds to render a new version after the edit has been saved.

The Wikimedia Foundation’s Parsoid project is working on these issues by complementing existing Wikitext with an equivalent HTML5 version of the content. In the short term, this HTML representation lets us use HTML technology for visual editing. In the longer term, using HTML as the storage format can eliminate conversion overhead when rendering pages, and can also enable more efficient updates after an edit that only affect part of the page. This might all sound pretty straightforward. So why has this not been done before?

Lossless conversion between Wikitext and HTML is really difficult

For the Wikitext and HTML5 representations to be considered equivalent, it should be possible to convert between Wikitext and HTML5 representations without introducing any semantic differences. It turns out that the ad-hoc structure of Wikitext makes such a lossless conversion to HTML and back extremely difficult.

In Wikitext, italic text is enclosed in double apostrophes (”…”), and bold text in triple apostrophes (”’…”’), but here these notations clash. The interpretation of a sequence of three or more apostrophes depends on other apostrophe-sequences seen on that line.
Center: Wikitext source. Below: As interpreted and rendered by MediaWiki. Above: Alternative interpretation.

  • Context-sensitive parsing: The only complete specification of Wikitext’s syntax and semantics is the MediaWiki PHP-based runtime implementation itself, which is still heavily based on regular expression driven text transformation. The multi-pass structure of this transformation combined with complex heuristics for constructs like italic and bold formatting make it impossible to use standard parser techniques based on context-free grammars to parse Wikitext.
  • Text-based templating: MediaWiki’s PHP runtime supports an elaborate text-based preprocessor and template system. This works very similar to a macro processor in C or C++, and creates very similar issues. As an example, there is no guarantee that the expansion of a template will parse to a self-contained DOM structure. In fact, there are many templates that only produce a table start tag (<table>), a table row (<tr>...</tr>) or a table end tag (</table>). They can even only produce the first half of an HTML tag or Wikitext element (e.g. ...</tabl), which is practically impossible to represent in HTML. Despite all this, content generated by an expanded template (or multiple templates) needs to be clearly identified in the HTML DOM.
  • (more…)

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 translatewiki.net 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

Language Engineering team participates in GNUnify 2013

Det vatten du hämtar ur bäcken lär dig känna källan – a Swedish Proverb.

GNUnify is an annual gathering consisting of workshops, talks & seminars, held to help increase the awareness of free and open-source software in India.

GNUnify is an annual gathering consisting of workshops, talks & seminars, held to help increase the awareness of free and open-source software in India.

The Wikimedia Language Engineering team participated in GNUnify 2013 held in Pune, India on February 15–17. The team presented their work, conducted a translation sprint, organized workshops and also participated in discussions with local Wikipedians about using MediaWiki and Wikimedia projects in their languages.

Presentations by the team

Runa Bhattacharjee presented about the changing dynamics in the adoption of localized content and the need for developing tools that facilitate new demands. She introduced the projects that the Language Engineering team is working on. Siebrand Mazeland and Niklas Laxström gave a walkthrough of the MediaWiki Translate extension and the translatewiki.net platform, and showcased the new design and features of the updated translation editor.

Santhosh Thottingal presented how the jQuery libraries of Project Milkshake can be used to prepare multilingual web applications for internationalization; he also presented a tutorial on their use. Amir Aharoni demonstrated the easy use of the input methods provided by the jQuery.IME library and how to contribute using phonetic keymaps. He encouraged use in web applications of the currently more than 140 input methods of the library. Yuvaraj Pandian demonstrated how he ported jQuery.IME for use in Android devices.

Alolita Sharma spoke about technologies and tools that help contributing to Wikipedia in various languages. She highlighted the need for features and tools to support non-English Wikipedias and the solutions that the Language Engineering team is developing that would help eliminate fundamental hindrances that contributors face while trying to create content for Indian languages. She also spoke about the other Wikimedia projects that are open for participation.

Workshops

Amir Aharoni conducted a workshop on the jQuery.IME library, in which he demonstrated the procedure to add a new input method and submit it for inclusion on GitHub. A two-hour translation sprint was conducted in which almost 40 participants translated various projects hosted on translatewiki.net. At the end of the session, more than 1000 completed translations were logged and prizes were distributed for the most significant contributions. Yuvaraj Pandian, Sucheta Ghoshal and Harsh Kothari conducted a workshop on building MediaWiki gadgets. Participants were introduced to the process of creating gadgets using JavaScript and CSS, and making them available for other users.

Language Engineering BOF session

The Language Engineering team also organized a session to discuss technical issues related to Wikimedia projects in Indian languages, which was attended by local Wikipedians. Issues related to following up on internationalization and localization bugs and building local technical user groups were discussed.

To conclude, participation in open source conferences such as GNUnify helps get more open source developers as well as language Wikipedians aware of the latest tools that the Language Engineering team is developing which they can use as well as receive direct feedback from the global communities the team serves.

More information can be found in the detailed report.

Runa Bhattacharjee, Outreach and QA coordinator, Language Engineering