launchpad help|
Size: 7711
Comment:
|
Size: 8346
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| !!!! DRAFT !!!! The development or this group is discussed here: https://blueprints.edge.launchpad.net/rosetta/+spec/launchpad-translators-group ~-[[FrontPage|Launchpad Help]] > [[Translations]] > "Launchpad Translators" translation group -~ |
~-[[FrontPage|Launchpad Help]] > [[Translations]] > Translators and Translation Teams in Launchpad -~ |
| Line 10: | Line 7: |
| * Link to [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators Group in Rosetta]] * Link to a list of translation guides for all languages * Link to a page describing upstream translation projects and how we should work togheter |
[[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators group]] is a set of teams and individuals working on translating software hosted in Launchpad. It is as a confederation of translation teams. |
| Line 14: | Line 10: |
| = Goal and Purpose = | There is one Launchpad localization ''team'' appointed for each language and translating projects hosted by Launchpad into that language. |
| Line 16: | Line 12: |
| ''Describe the goal and purpose of Launchpad Translators group and it's relations with the other translations groups, including Ubuntu, GTP , Mozilla, OpenOffice.org, The Translation Project'' | This is not yet another translations project. We belive that people translating software in the same language should work in the same team, even thought they are working at different software. |
| Line 18: | Line 14: |
| We want to build the Launchpad Translators Group as a confederation of translation teams each team working at translating project hosted by Launchpad in it's language. | We encourage Ubuntu, Debian, Fedora, GNOME, KDE, Mozilla, !OpenOffice.org and all other translators dedicated to a specific project to join the localization team appointed for their language. |
| Line 20: | Line 16: |
| All members of Launchad Translators should be experts in translating software and be aware about the work of other teams from Launchpad or not. Launchpad translators will do translations work | We encourage project maintainers to appoint '''Launchpad Translators''' ''group'', as the translation group for their project and set the translation model to ''structured''. |
| Line 22: | Line 18: |
| Project maintainers should be able to trust Launchpad Translators Group and appoint it to manage translations for their projects. | = Project maintainers = |
| Line 24: | Line 20: |
| = Working with Launchpad Translators = == Project maintainers == * first learn how to use Launchpad Translations to make translation available for your project. For more information [[https://help.launchpad.net/Translations | check the Launchpad Translations help pages]] * chose a translation model and appoint Launchpad Translators Group for doing the translation * use the announcemnt list for things that affect all languages (ex. new release, major string changes, string freeze... etc) or each team for things affecting only one language |
Every project needs high quality translation that convey with the cultural background and already established guidelines for translating software into each language. |
| Line 30: | Line 22: |
| * TODO: see how we can use Bugs and Answers to interact with project maintainers | '''Launchpad Translators''' ''group'' stands for those goals and you will find below a list of steps to follow in order to start using Launchpad Translations (Rosetta) and have your project translated in many languages and in the same time assuring translation quality. |
| Line 32: | Line 24: |
| == Translators == * First learn how to use Launchpad for translating projects/operating systems. For more information [[https://help.launchpad.net/Translations | check the Launchpad Translations help pages]] * Follow the procedure for joining a team for your language. Before joining a team you might be asked to do some translation in order to check your translation skills. * Follow the rules of your team * When translating downstream always check with the upstream project and commit your changes |
* Before procedding to the next steps, please take a moment and see how to use Launchpad Translations to make translation available for your project. You can find this information at [[https://help.launchpad.net/Translations/YourProject | Translating your project help pages]] |
| Line 38: | Line 26: |
| = Teams = ''Describe purpose of a Launchpad translation team'' |
* Chose a translation permissions policy and appoint Launchpad Translators Group for doing the translation. Follow this link to find more info about [[https://help.launchpad.net/Translations/YourProject#Choosing%20a%20permissions%20policy | Choosing permissions policy]]. We recoomend using the ''Structured'' policy, as a measure to assure translation quality. * The direct link to your project permissions policy is: https://translations.launchpad.net/<YOUR-PROJECT-NAME>/+changetranslators. * You can contact the [[https://launchpad.net/~launchpad-translators Launchpad Translators team]] for announcing things that affect all languages (ex. approaching release, major string changes, string freeze... etc) or a [[https://translations.launchpad.net/+groups/launchpad-translators/ specific language team]] for things affecting only one language. * You can also send an initial message to [[https://launchpad.net/~launchpad-translators Launchpad Translators team]] and let them know about your project. * When you are due to release a new version of your project, contact the team and let them know when you would like to release, in this way translators can better organize their work. It is good to advise them at least two weeks before a release. * If there are any translations errors or bug in your project please assign them to the [[https://launchpad.net/~launchpad-translators Launchpad Translators team]]. We will look into the problem and assign them to the proper team or person. * For your project Answers section, if people ask about specific translations or localization matters, you can assign those questions to the [[https://translations.launchpad.net/+groups/launchpad-translators/ Launchpad Translators team]]. We will try to analyze it and have a knowledgable person take care or it. = Translators = All members of a Launchpad localization teams should be knowledgable in translating software into their language and be aware about the work of other teams from Launchpad or other translations project working outside of Launchpad. Below is a list of steps you might follow in order to start using Launchpad Translations (Rosetta) for translating your favorite project or distributions into your language. * Before doing any translation work please take a moment and learn how to use Launchpad for translating projects/operating systems. For more information [[https://help.launchpad.net/Translations/StartingToTranslate | check the Launchpad Translations help pages]] * Consult the [[https://translations.edge.launchpad.net/+groups/launchpad-translators/ | list of translations teams]] and check the team assigned for your language. If there is no team assigned for your language please follow the required step to create a new one. Below you will find more information about creating a new team. * Follow the procedure for joining the team for your language. Before joining a team you might be asked to do some translation in order to check your translation skills. * Follow the rules of your team, communicate and keep in touch with the team. * You may want to join the [[https://launchpad.net/~launchpad-translators Launchpad Translators mailing list]] and get in touch with other translators = Launchpad localization teams = Launchpad localization teams are the |
| Line 42: | Line 61: |
| = Managing a team = | * As the coordinator for your team, you act as the primary contact person for the team and are responsible for organizing the other translators in your team. This includes attempting to prevent multiple translators simultaneously attempting translations of the same file. |
| Line 44: | Line 63: |
| ''General information about managing a team and a translation team'' == Relation with other translation teams == ''How each team can work and colaborate with upstream or other translation project for the same language.'' ''How each team can share best practice with the other Launchpad translators team'' == Quality assurence == ''How a team can work and comunitate in order to assure quality.'' == Common/best practice == Below you will find a set of common practices for running a team * Don't forget about other translators or translations groups. In many cases you or your are not the only one doing translation in the free software ecosystem. Always keep in touch with that other teams are doing and make sure the translation teams for your language are translating free software using the same "language". Try to create or join a communication channel channel common to all transaltion teams for your language and use it for talking about important aspect that affect all translations. * Define a procedure for accepting new team members. * The acceptance level may vary according to the percentage of already finnised translations. For languages with few translators and translations already done team acceptance could be lower than in the case of a language with many translators, tramslations made and the presence of GTP, OpenOffice , etc upstream translation projects. * Before accepting a member you may ask him/her to provide some translation. If the translations are great you may accept the new member. Otherwise giving feedback about why the translation are not good is a great help. Try to use a forum, mailinglist or IRC channel for giving feedback to potential new members. * Create a webpage/wikipage for the translations guide. This guide should contain: * First rule: "If a translation does not make sense for you / your grandmother, definetly it is wrong!". * Second rule: "Make your translation useful and adapt to the context. Don't follow always the original text". Like for example "Tile children" may sound funny in many languages so try "Arrange windows as tilea". The original text is not always the correct one. * a common terminolgy or a link to a common terminalogy dictionary or glossary. Don't forget about [[http://open-tran.eu | open-tran.eu ]] . You can also install [[http://www.i18n.ro/glosar | the glossary used by Romanian teams]] ([[ http://diacritice.svn.sourceforge.net/viewvc/diacritice/trunk/ | here is the code]]) * information about what should be translated and what not * specific rules for translating into your language * a list of frequent errors. * explaining the plurar form for your language and how to use them * how you should translate menu accelerators / shortcuts * inform the translators about other translation project and how we should cooperate and work togheter * Make sure you have a solid communication channel for all members of the team or subteam. Try to reach all communication types: maillinglist, forum, IRC channel. * add your best practice 1 * add your best practice 2 |
* Coordinators need to be subscribed to the Launchpad Translators team mailing list LINK-HERE. This is highly recommended for all Launchpad translators, but required for coordinators. |
| Line 83: | Line 66: |
| = Creating a team = Launchpad Translators Group will appoint one team for each language. To add more teams for a specific language you will need to add them as a subteam of the initial team. |
== Creating a team == Launchpad Translators Group will appoint only one team for each language. If there is already a team appointed for your language please consider joining that team. |
| Line 86: | Line 69: |
| Thus creating a new Launchpad team for a specific language and asking for it's appointment is only required if there is no team already appointed for the specific language. | To check the current status for your language, please consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | list of Launchpad localization team]]. If your language does not appers in the list, please consider starting a team for your language. |
| Line 88: | Line 71: |
| To check the current status you can consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators Group in Rosetta]]. | If the Launchpad localization team appointed to your language is no longer active, or in case you encounter problems joining or working with the team, please let us know by [[https://answers.launchpad.net/rosetta | filling an answer for Launchpad Translations]]. |
| Line 90: | Line 73: |
| If there is already a team appointed for a language you can still create your own translation team but in order to translate software in your language you will need to become a subteam of the already appointed team for your language. | |
| Line 92: | Line 74: |
| Steps to follow for creating a team and appointing to a language. * join the launchpad translators discussions/announcemnts list - ADD LINK TO THIS LIST * create a wiki page or a web page explaining how translators should work in your team . you can follow the example from our best practices -ADD LINK - and adapt them to your language/team |
* If you are already a coordinator of a translation team, let us know about this, and go to step X |
| Line 96: | Line 76: |
| 1. If you translation karma is over 5000 go to step X 1. If you are already a coordinator of a translation team, let us know about this, and go to step X 1. If there is already a GNOME, KDE, OpenOffice.org, Mozilla, etc. upstream project from your language point us some translation you have made for those projects then go to step X 1. If there is no upstream project already set for your language please consider following the required steps in creating one for your language. There is no problem if in the same time you are the coordinator for multiple translation projects. 1. '''Step X''' create a lp-l10n-CC team and ask launchpad-translation-leaders to appoint a language to this team. We use iso-639 two letters code and if not available we fallback to three letters code. |
* If there is already a GNOME, KDE, OpenOffice.org, Mozilla, etc. upstream project from your language point us some translation you have made for those projects then go to the final step * If there is no upstream project already set for your language please consider following the required steps in creating one for your language. There is no problem if in the same time you are the coordinator for multiple translation projects. Steps to follow for appointing the team to your language: * As the coordintor of a Launchpad localization team it is higly recommended to join the [[https://launchpad.net/~launchpad-translators Launchpad Translators mailing list]] * [[https://launchpad.net/people/+newteam | Create a new Launchpad localization team]] for your language. When naming the team we recommend to follow the convention: '''lp-l10n-CC''', where CC is your '''language'' code . We use iso-639 two letters code and if not available we fallback to three letters code. * On the Launchpad page for you team explain how translators should work in your team. * You can use the [[Translations/Guide | general Launchpad localization guidelines]] or adapt them to your language/team * Let Launchpad know about your translation guidelines. [[Translations/Guidelines | Read about how to do it]]. * Ask [[https://edge.launchpad.net/%7Elaunchpad-translators-leaders/+contactuser | Launchpad Translators coordinators]] to appoint your language. Please specify the name of the language and the name of the team. ||<tablestyle="width: 100%;"> ~-[[Translations/TranslationGroups|< Translations Groups]] -~ ||<style="text-align: right;"> ~- [[Translations/Guide|General translation Guide >]] -~ || |
Launchpad Help > Translations > Translators and Translation Teams in Launchpad
Overview
Launchpad Translators group is a set of teams and individuals working on translating software hosted in Launchpad. It is as a confederation of translation teams.
There is one Launchpad localization team appointed for each language and translating projects hosted by Launchpad into that language.
This is not yet another translations project. We belive that people translating software in the same language should work in the same team, even thought they are working at different software.
We encourage Ubuntu, Debian, Fedora, GNOME, KDE, Mozilla, OpenOffice.org and all other translators dedicated to a specific project to join the localization team appointed for their language.
We encourage project maintainers to appoint Launchpad Translators group, as the translation group for their project and set the translation model to structured.
Project maintainers
Every project needs high quality translation that convey with the cultural background and already established guidelines for translating software into each language.
Launchpad Translators group stands for those goals and you will find below a list of steps to follow in order to start using Launchpad Translations (Rosetta) and have your project translated in many languages and in the same time assuring translation quality.
Before procedding to the next steps, please take a moment and see how to use Launchpad Translations to make translation available for your project. You can find this information at Translating your project help pages
Chose a translation permissions policy and appoint Launchpad Translators Group for doing the translation. Follow this link to find more info about Choosing permissions policy. We recoomend using the Structured policy, as a measure to assure translation quality.
The direct link to your project permissions policy is: https://translations.launchpad.net/<YOUR-PROJECT-NAME>/+changetranslators.
You can contact the https://launchpad.net/~launchpad-translators Launchpad Translators team for announcing things that affect all languages (ex. approaching release, major string changes, string freeze... etc) or a https://translations.launchpad.net/+groups/launchpad-translators/ specific language team for things affecting only one language.
You can also send an initial message to https://launchpad.net/~launchpad-translators Launchpad Translators team and let them know about your project.
- When you are due to release a new version of your project, contact the team and let them know when you would like to release, in this way translators can better organize their work. It is good to advise them at least two weeks before a release.
If there are any translations errors or bug in your project please assign them to the https://launchpad.net/~launchpad-translators Launchpad Translators team. We will look into the problem and assign them to the proper team or person.
For your project Answers section, if people ask about specific translations or localization matters, you can assign those questions to the https://translations.launchpad.net/+groups/launchpad-translators/ Launchpad Translators team. We will try to analyze it and have a knowledgable person take care or it.
Translators
All members of a Launchpad localization teams should be knowledgable in translating software into their language and be aware about the work of other teams from Launchpad or other translations project working outside of Launchpad.
Below is a list of steps you might follow in order to start using Launchpad Translations (Rosetta) for translating your favorite project or distributions into your language.
Before doing any translation work please take a moment and learn how to use Launchpad for translating projects/operating systems. For more information check the Launchpad Translations help pages
Consult the list of translations teams and check the team assigned for your language. If there is no team assigned for your language please follow the required step to create a new one. Below you will find more information about creating a new team.
- Follow the procedure for joining the team for your language. Before joining a team you might be asked to do some translation in order to check your translation skills.
- Follow the rules of your team, communicate and keep in touch with the team.
You may want to join the https://launchpad.net/~launchpad-translators Launchpad Translators mailing list and get in touch with other translators
Launchpad localization teams
Launchpad localization teams are the
- As the coordinator for your team, you act as the primary contact person for the team and are responsible for organizing the other translators in your team. This includes attempting to prevent multiple translators simultaneously attempting translations of the same file.
- Coordinators need to be subscribed to the Launchpad Translators team mailing list LINK-HERE. This is highly recommended for all Launchpad translators, but required for coordinators.
Creating a team
Launchpad Translators Group will appoint only one team for each language. If there is already a team appointed for your language please consider joining that team.
To check the current status for your language, please consult the list of Launchpad localization team. If your language does not appers in the list, please consider starting a team for your language.
If the Launchpad localization team appointed to your language is no longer active, or in case you encounter problems joining or working with the team, please let us know by filling an answer for Launchpad Translations.
- If you are already a coordinator of a translation team, let us know about this, and go to step X
If there is already a GNOME, KDE, OpenOffice.org, Mozilla, etc. upstream project from your language point us some translation you have made for those projects then go to the final step
- If there is no upstream project already set for your language please consider following the required steps in creating one for your language. There is no problem if in the same time you are the coordinator for multiple translation projects.
Steps to follow for appointing the team to your language:
As the coordintor of a Launchpad localization team it is higly recommended to join the https://launchpad.net/~launchpad-translators Launchpad Translators mailing list
Create a new Launchpad localization team for your language. When naming the team we recommend to follow the convention: lp-l10n-CC, where CC is your language code . We use iso-639 two letters code and if not available we fallback to three letters code.
- On the Launchpad page for you team explain how translators should work in your team.
You can use the general Launchpad localization guidelines or adapt them to your language/team
Let Launchpad know about your translation guidelines. Read about how to do it.
Ask Launchpad Translators coordinators to appoint your language. Please specify the name of the language and the name of the team.
