The language team continued maintenance of the UniversalLanguageSelector, in particular improving performance and integration testing, and completed its integration with EventLogging, which will provide metrics useful e.g. to choose the best default font for a language. Counts from translatewiki.net are live and a deployment plan for Wikimedia projects is under analysis. The team also released its monthly version of the MediaWiki Language Extension Bundle (MLEB) which is used by third party developers and community members to add language support for their MediaWiki applications.
The team continued mentoring four Google Summer of Code (GSoC) students. Praveen Singh, mentored by Santhosh Thottingal, released a Chrome extension for Wikimedia Input Tools and contributed to the Indic Font Specification, a collaborative open source project. Team members also continued to work with Red Hat on various language initiatives.
The team participated at Wikimania in Hong Kong, which was an opportunity to meet face to face, as well as to interact with Wikipedians and community members to solve a variety of issues, including dealing with Chinese language variants and adding language assets for Javanese. The team also presented various talks on language engineering.
Rationale[edit | edit source]
If you can't type in your language, or if your operating system doesn't natively have the ability to display your language on the web, you are impeded from reading or editing Wikimedia projects. As Wikimedia reaches into strategic priority regions like India, ensuring that we eliminate all barriers to access and participation is escalating in priority.
Key deliverables[edit | edit source]
Deliverables of this project will likely include:
- Consistent support for web fonts as needed, building on the web fonts extension
- Consistent availability of input methods for all supported languages in any Wikimedia projects (e.g. it should be possible to type in Hindi on the English Wikipedia), building on the Narayam extension
- Support for new input methods (including potentially on-screen keyboards) and new character sets
- Porting/implementing relevant support on mobile devices
- Improvement of RTL support, especially in a bidirectional context
- Resolution of other critical issues, e.g. resolve encoding conflicts with search engines
Timeline[edit | edit source]
- The team formed in July/August 2011, at which point requirements gathering, prioritization and development began to officially kick off.
- You can access the full list of the team's todos for this sprint (two weeks period) on Mingle.
Additional documents[edit | edit source]
- User requirements:
- Software design document:
- Test plan:
- Documentation plan:
- User interface design docs:
- Task management:
- Release management plan:
- Communications plan:
- Status updates