Community localization



It should be easy for translators to create high quality translations of

  • published Nokia applications
  • community provided applications
  • third party commercial applications

The system should provide a web based tool based on a customized version of Transifex and it needs to integrate nicely with the whole infrastructure.

All translations should be added to the upstream projects if possible. If that is not possible (or not wanted) the translations will be stored in a repository.

Community applications will ship Debian packages including the translations as usual. For preinstalled software we will provide Debian packages containing only the translations. One packages for each language.


  • Team: Logical team consisting of translators working on a language (eg. de, cat, id)
  • Collection: Groups of projects (eg. Maemo, GNOME, KDE)
  • Project: Project to be translated (eg. conboy, gPodder)
  • Developer (Owner): A person who create a project
  • Maintainer : A person who has permissions to edit Project, Components and grant permissions for submissions to other users.
  • Component: A specific branch/release of aproject
  • Team Owner: Person who creates a team
  • Coordinator: Person who manages the team

Process Notes

This is how the system works in several point of views.

Developer point of view

Initial creation

  • Create a project in garage, tick "[] I want my project to be translatable by community"


  • Create a project somewhere else (eg. GitHub) and create the translation project in the system
  • Give authorization to system to submit translations to the VCS of the project

String freeze

In the component view, developer selects date for upcoming release date and string freeze. Translators can see the dates in the calendar in dashboard.


Developer can initiate mass message for subscriber of the project

Translator point of view

Team building

  • Team owner requests a team creation for a language
  • After team owner can add translators/coordinator/reviewers
  • translator joining a team, getting approval from coordinator to commit translations for all of the projects.

Doing the translation

  • Go to project's component
  • Translator select the component she wants to translate, and this effectively lock the translation file
  • When translator thinks she is done with the translation, the review request is sent, the lock is released


  • Reviewer gets notifications of a ready-to-review translation
  • Reviewer reviews the translations,
 * If the translation is accepted, the state of the translation is now "Approved" and pushed to upstream (or exported as packages)
 * If the translation is rejected then the translation state is "Rejected" and the translator gets notification



  • Prioritizing projects
  • Adding/removing translators
  • Monitoring that the translation process is moving and act accordingly

There will be no special interface for coordinator to do tasks above.

Other Notes

What needs to be done

There are three parties needed to realize the community localizations. Those are Noka, and For each of them we collected a prioritized list of deliverables.


  • Needs to provide the funds.
  • Needs to provide translatable strings of all closed applications.
  • Should open the official language selection dialog in order to make it display not only official translations but also community translations. The language selection dialog in Fremantle uses a hard coded list. This should be changed in Harmattan. Instead of a hard coded list it should display all installed translations.
  • Could integrate community translations into the first-start setup dialog. There are currently only official translations selectable. There could be an option to let the user download and install community translations. If needed of course with a disclaimer.
    • If the above is too intrusive the user could get a message telling him that there are community translations available for download.
  • Could provide the existing translations (after sales start). Those translations could be used to bootstrap the translation system, fill the glossary, etc.

  • Needs to support translation teams (grouped by languages)
  • Needs to provide running installation on As soon as possible open for beta user. Later open for everyone.
  • Needs to support for roles (Owner, Coordinator, Translator, Reviewer, Developer)
  • Needs to provide a reviewing system
  • Should get support for .po files using logical IDs. Logical IDs are used by Nokia internal software like, for example, the media player.
  • Should be able to show a license page to translators. Translators have to agree to commit there translations using that license.
  • Should support access rights on collections. With that translators can get commit rights to all projects without having to request permissions to each single project.
  • Should offer a way to get statistics (like number of translated strings) into the karma system.
  • Should offer a subscription/communication system. This can be used for automatic notifications and also for communications between different people.
  • Should let the developer set the date of the next planned release. This would help translators to finish up translations on time.
  • Should offer a calender with the collected release dates. This calender can be used to prioritize translation work.
  • Should offer a way to lock selected languages for certain projects. E.g. the German translation of Nokias media player does already officially exist - therefore it would be a waste of time if the community would translate it again.
  • Should provide single sign on with
  • Should support project states like Started, Reviewed, Completed
  • Could include translator credits in the .po files. With that translators could properly be credited in the package/application.
  • Could offer automatic glossary lookup
  • Could offer translation memory
  • Could include translation-toolkit to catch common translation errors.
  • Needs to support 1:n translations. They will be used in Maemo 6 to provided strings with different length (e.g. portrait/landscape orientation). The number of variants may vary from language to language.

  • Needs to write a system to create Debian packages out of translations for closed applications. (E.g. Arabic translation of Nokias media player)
  • Should add support for Karma generated by translation work on
  • Should offer single sign on with
  • Could offer new garage projects to automatically create a corresponding project.
  • Could write Maemo 5 software to let users switch between community supported languages, because the default tool uses a hard coded list of languages.