Editing Community localization
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 5: | Line 5: | ||
* third party commercial 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 maemo.org infrastructure. | |
- | All translations | + | 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 maemo.org repository. |
- | Community applications will ship Debian packages including the translations as usual. For preinstalled software | + | 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. |
- | + | ||
- | + | ||
== Glossary == | == Glossary == | ||
- | * Team: Logical team consisting of translators working on a language (eg. de, | + | * Team: Logical team consisting of translators working on a language (eg. de, cat, id) |
- | * Collection: Groups of projects (eg. Maemo, GNOME, KDE) | + | * 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 | + | * Component: A specific branch/release of aproject |
* Team Owner: Person who creates a team | * Team Owner: Person who creates a team | ||
* Coordinator: Person who manages the team | * Coordinator: Person who manages the team | ||
- | == | + | ==Process Notes== |
This is how the system works in several point of views. | This is how the system works in several point of views. | ||
=== Developer point of view === | === Developer point of view === | ||
- | ==== | + | ==== Initial creation ==== |
- | * Create | + | * Create a project in garage, tick "[] I want my project to be translatable by community" |
- | + | or | |
- | + | * 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 | |
- | * Give authorization to system to submit translations to the | + | |
==== String freeze ==== | ==== String freeze ==== | ||
- | In the component view, developer selects date for upcoming | + | In the component view, developer selects date for upcoming release date and string freeze. Translators can see the dates in the calendar in dashboard. |
==== Communication ==== | ==== Communication ==== | ||
- | Developer can initiate mass message for subscriber of the project | + | Developer can initiate mass message for subscriber of the project |
=== Translator point of view === | === Translator point of view === | ||
- | |||
- | |||
==== Team building ==== | ==== Team building ==== | ||
* Team owner requests a team creation for a language | * Team owner requests a team creation for a language | ||
- | * After team | + | * After team owner can add translators/coordinator/reviewers |
* translator joining a team, getting approval from coordinator to commit translations for all of the projects. | * translator joining a team, getting approval from coordinator to commit translations for all of the projects. | ||
Line 57: | Line 52: | ||
* Reviewer gets notifications of a ready-to-review translation | * Reviewer gets notifications of a ready-to-review translation | ||
* Reviewer reviews the translations, | * 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 | |
=== Coordinator === | === Coordinator === | ||
Line 67: | Line 62: | ||
There will be no special interface for coordinator to do tasks above. | There will be no special interface for coordinator to do tasks above. | ||
+ | |||
+ | ==Other Notes== | ||
=What needs to be done= | =What needs to be done= | ||
- | There are three parties needed to realize the community localizations. Those are | + | There are three parties needed to realize the community localizations. Those are Noka, Transifex.net and Maemo.org. For each of them we collected a prioritized list of deliverables. |
==Nokia== | ==Nokia== | ||
Line 87: | Line 84: | ||
* Needs to support for roles (Owner, Coordinator, Translator, Reviewer, Developer) | * Needs to support for roles (Owner, Coordinator, Translator, Reviewer, Developer) | ||
* Needs to provide a reviewing system | * 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 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 maemo.org projects without having to request permissions to each single project. | * Should support access rights on collections. With that translators can get commit rights to all maemo.org projects without having to request permissions to each single project. | ||
Line 103: | Line 99: | ||
* Could include translation-toolkit to catch common translation errors. | * 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 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. | ||
+ | |||
==Maemo.org== | ==Maemo.org== | ||
- | * Needs to write | + | * 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 | + | * Should add support for Karma generated by translation work on transifex.net |
* Should offer single sign on with transifex.net | * Should offer single sign on with transifex.net | ||
* Could offer new garage projects to automatically create a corresponding transifex.net project. | * Could offer new garage projects to automatically create a corresponding transifex.net project. | ||
- | * Could write | + | * Could write Maemo 5 software to let users switch between community supported languages, because the default tool uses a hard coded list of languages. |
- | + | ||
- | + |
Learn more about Contributing to the wiki.