Language tools

From MediaWiki.org
Jump to: navigation, search
  • 2014-11-monthly:
    The team fixed several bugs in UniversalLanguageSelector. A bug was fixed that caused JavaScript errors on a few special pages without headings. The font size for button text was fixed to improve display on Monobook skin for Mozilla Firefox. The team also added support for the WOFF2 webfont format. Experiments revealed significant improvement in overheads. However, there are no WOFF2 webfonts in the font repository yet due to pending issues in WOFF2 font generation.21 new languages are now supported in the language selector, and autonyms for 5 languages were updated.

The team migrated the translation memory service of the Translate extension to ElasticSearch. Thanks to WMF's ElasticSearch cluster, this migration increases the speed and reliability of the service. We have identified one issue with the suggestions, which is being fixed during December. Thanks to Chad and Nik for helping Niklas.

Last, the team also made RTL fixes in MobileFrontend and VisualEditor.

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]


Impact Measurement and Metrics[edit | edit source]

Communications[edit | edit source]