Fortuna i forti aiuta, e i timidi rifiuta — an Italian proverb

The Wikimedia Foundation and Red Hat jointly organized the Second Open Source Language Summit on February 12th and 13th, 2013. The summit was held at the Red Hat engineering center in Pune, India. Similar to the previous summit, this face-to-face work session was focused on internationalization (i18n) and localization (l10n) features, font support, input method tools, language search, i18n testing methods and standards. The sessions were work sprints, each with special focus on a key area. Participants included core contributors from the Wikimedia Foundation, Red Hat (including Fedora SIG members), KDE, FUEL, Google and C-DAC. Below is a summary of what was accomplished during these two days.

During the summit, teams from different organizations came together to discuss language-related challenges, and worked together on features and tools to address them.

Input Methods

Parag Nemade and Santhosh Thottingal worked on making additional input methods available for the jQuery.IME library. 60 input methods, covering languages like Assamese, Esperanto, Russian, Greek, Hebrew were added bringing the total to 144. Also IMEs from the m17n library missing from the jQuery.IME library were identified.

Translation tools, translatewiki.net & FUEL Sprint

Siebrand Mazeland and Niklas Laxström, together with Ankit Patel, Rajesh Ranjan and Red Hat language maintainers, worked to identify more tools that could be used as Translation aids in a translation system. The FUEL project aims to standardize translations for frequently used terms, translation style and assessment methodology. Until now it has focused mostly on languages of India. The FUEL project can now be translated in translatewiki.net. Pau Giner demonstrated new designs for the translation editor and terminology usage, remotely from Spain.

Language Coverage Matrix

To better evaluate the needs for enabling support for languages, a matrix detailing the requirements and availability of basic and extended features is being drawn up. With 285 languages currently supported in Wikimedia and more than 100 in Fedora, this document will be instrumental in bridging the gaps and porting features across projects and platforms. Key areas of evaluation include input methods, fonts, translation aids like glossaries and spell-checkers, testing and validation methods, etc. A preliminary draft was created during the summit by Alolita Sharma, Runa Bhattacharjee and Amir E. Aharoni.

Fonts, WebFonts

An initiative to document the technical aspects of fonts for scripts for languages spoken in India started during the language summit. For each of the scripts, a reference font will be chosen and each font will be explained in detail to intersect with the Open Type font specification as a standard. It will aim to act as a reference document for any typographer working on Indian language fonts. Initial draft and outline of this document was prepared during the second day of the language summit, mainly by Santhosh Thottingal and Pravin Satpute.

Testing Internationalization Tools

Finding suitable methods for testing internationalized components and contents was the major focus of this sprint, with the Fedora Localization Testing Group (FLTG) and Wikimedia’s Language Engineering team sharing details of their testing methods. The FLTG conducts Test Days prior to Fedora beta releases with a test matrix targeted at specific core components, and Wikimedia uses unit tests for frequent testing of their development features. The FLTG showed its plans to integrate the screenshot comparison method for testing localized interfaces. This method will be useful for Wikimedia too. Extending the method for web-based applications and Wikimedia’s language requirements (e.g. right-to-left) were identified as areas for collaboration.

More news from the Language Summit can be found in the tweets, the session notes and the full report.

Runa Bhattacharjee, Outreach and QA coordinator, Language Engineering

The Wikimedia Foundation and Red Hat co-organized an Open Source Language Summit in Pune, India on November 6-7, 2012. The summit focused on language tools and technology development to support languages on Wikipedia, the Web, Linux and other Open Source platforms.

Santhosh Thottingal presenting his talk on jquery.ime

In total, 45 core language technology developers, open source contributors, typographers and technology evangelists from the Wikimedia Language Engineering and Mobile teams, Red Hat, Mozilla Foundation, KDE, GNOME, translatewiki.net and other open source projects participated in sessions and work sprints on internationalization and localization features supporting various open source projects on the web and Linux. After brief introductory talks, we focused our work on font support, input method tools, language search, and web and localisation standards.

Highlights: 

The event had short talks on the following topics:

The following people won prizes for their code contributions during the event:

• Anish Patil ported Universal Language Selector’s cross-language search algorithm to gnome language search
• Aravinda VK wrote a set of font-forge python wrappers to make changes to fonts programmatically. Aravinda fixed a few bugs in Kannada Gubbi font for Harfbuzz rendering engine and also wrote Kannada KGP keymap for jquery.ime
• G Karunakar added Hindi inscript keyboard layout to Firefox OS GAIA

Other accomplishments included:

• Kushal Das added patches to deploy Universal Language Selector on http://www.mozilla.org and also a patch for a bug on Mozilla localization platform.
• Alolita, Sankarshan, Runa, Satish worked on discussing APIs for various translation workflows and putting together an initial specification.
• Rajeesh Nambiar, Hussain KH, Ani Peter, Praveen A and Pravin Satpute fixed and filed upstream bugs for Malayalam, Kannada, Gujarati and Punjabi fonts with Harfbuzz.
• Parag Nemade added InScript2 keyboards for Sanskrit, Nepali, Marathi and Konkani to jquery.ime.
• Ankit Gadgil wrote over 200 unit tests for Marathi and Hindi input methods in jquery.ime.
• Yuvaraj Pandian, Pau Giner, Arun Ganesh and Siebrand Mazeland developed an initial version of an Android-native app for Translatewiki.net for translation reviews.
• Pau Giner conducted user testing with new translation prototypes with translators. Arun Ganesh created an icon for gnome-transliteration.

You can browse through tweets and more notes from the event. Happy reading!

Srikanth Lakshmanan
Internationalisation/Localisation Outreach / QA Engineer

When a text is written, when it is printed for a first time, it will have a contemporary look. When you then look at historic texts, at a first publication, you will notice the many details that show its age. It can be in differences in orthography, differences in vocabulary and also differences in the layout, the fonts used.

When sources are published in Wikisource, maintaining the atmosphere of the original text is very important. It is why the original orthography and vocabulary are maintained and with the availability of the  WebFonts extension there is a potential to use fonts that give this impression of age.

In the Office hours of the Localisation team, the question was raised if we could support cuneiform. The answer to that was that we can when there is a freely licensed font. We found a freely licensed cuneiform font and it is made available on the Wikis that support WebFonts. The bigger question however is about all the other scripts that are of  historic significance. This is of particular relevance to the Sanskrit Wikisource; the Sanskrit language is written in many scripts and it is only recent when the Devanagari script became the default script.

For sources like the Quran maintaining the original orthography and characters is an article of faith. It is for this reason that characters were added to Unicode because alternate representations of the same characters were missing. We do have a beautiful freely license font, the Amiri font and we would love to support it in MediaWiki but we are struggling with technical issues.

For the Wikimedia Localisation team, it is impossible to identify all the needs for fonts, for historic text representation. This is why we have language support teams. They know their language, they can identify a need and hopefully they can identify usable freely licensed fonts. When they do, we can and will support fonts. In the mean time we will continue our work on a unified language selector.  This will make the use of WebFonts easy and obvious. At this time it works, but it is hard work for you as a user.

Thanks,
Gerard Meijssen
Internationalization / Localization outreach consultant

Firefox 3.5 will be launching this summer (betas available now!) and will include support for downloading and using regular TrueType and OpenType fonts referenced from a style sheet.

This is also supported in Safari 3.1 and later, and apparently by the latest Opera betas as well.

It might be helpful for some language wikis to link in a free font this way, when standard fonts supporting their script are often unavailable. Right now on such sites there tends to be a little English link at the top such as ‘font help’ leading to a page like this telling you how to download and install a suitable font.

Internet Explorer afaik still only supports converted embedded (EOT) font files, which would require that we can either get our hands on an existing .eot version of each free font, or be able to generate one ourselves.

Note there’s an old feature request with an .eot copy of a Tamil font, but we never had authorship info on the font or cross-browser support, since .eot is only supported by IE.