Deployment Guide/Localization: Difference between revisions

From OLPC
Jump to navigation Jump to search
(See Talk:Deployment_Guide for rationale)
(add GoogleTrans-en)
Line 1: Line 1:
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
==3. Localization==
==3. Localization==



Revision as of 20:10, 31 May 2008

Translate this page with Google -español -български -中文(中国大陆) -中文(臺灣) -hrvatski -čeština -dansk -Nederlands -suomi -français -Deutsch -Ελληνικά -हिन्दी -italiano -日本語 -한국어 -norsk -polski -português -română -русский -svenska


3. Localization

Almost every aspect of the one laptop per child system is amenable to localization and customization. The list below highlights features that can be customized, along with examples of such from our experiences in the field.

  • Keyboards can be country or language-group specific. (In both Nigeria and Afghanistan, we designed a keyboard to work with four major language groups. Alternatively, in the Indian subcontinent, at least ten different keyboards will be required to give broad coverage.)
  • Translation of the software is handled by volunteers. OLPC has set up a “Pootle Server”, a public server that enables anyone to help with translations. While we already have more than 50 translation projects underway, you are welcome to add new ones to suit the needs of your country. (Note that since the translations are done by volunteers, you may need to apply some resources to speed the process up and to ensure the accuracy of the work.)
  • Content, including texts, dictionaries, documentation, etc. can all be localized. OLPC maintains a wiki (a community-editable website) with numerous materials, guides, etc. that may already be translated. Also, the various in-country deployment teams have prepared materials that they are generally willing to share. Please ask OLPC for pointers to potentially useful materials.
    • Some materials will necessarily need to be localized in country. For example, Linux currently has no spelling dictionary for Igbo. Not to be deterred, the children at the Galadima school in Abuja wrote one themselves. One sub-goal of OLPC is self-sufficiency—localization is by definition a local problem—the open nature of our system enables community involvement and ownership.
    • The voice model used by the laptop's speech synthesizer supports approximately 50 languages; developing new models is somewhat tedious, but may be worth the investment, as text-to-speech is a useful tool for both learning to read and accessibility.
  • The base software system distributed on the laptop can also be customized to some extent. OLPC has developed a mechanism where by the collection of “activities” and content “bundles” loaded onto the laptop can be readily pre-configured. It is also reasonably easy to reconfigure in the field. It is the responsibility of the in-country deployment team to determine which activities beyond the core set distributed by OLPC should be included on the laptop. While OLPC does QA on the core activities, it is advised that in-country QA be done on any additional activities to be bundled with the base system. (Most activities are developed by volunteers from the open source community—the translations and the activities themselves must be tested in country as part of your evaluation as to what to activities to ship with the laptops.) Electronic books—PDF, DOC, HTML, etc.—and other media can be pre-loaded onto the laptop as a content bundle. Please consult with OLPC regarding pre-loaded content preparation.

Next Section: Connectivity