Diff for "Translations/LaunchpadTranslators"

Not logged in - Log In / Register

Differences between revisions 19 and 42 (spanning 23 versions)
Revision 19 as of 2009-01-18 02:55:09
Size: 11996
Editor: 78
Comment:
Revision 42 as of 2010-07-01 08:04:05
Size: 7471
Editor: g224055209
Comment: corrected link
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
 * In Launchpad Translations (Rosetta) there is one translators group called [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators translation group]]. The [[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 a confederation of translation teams, it is not yet another translation project.
Line 9: Line 9:
 * This unique translators group is comprised of serveral Launchpad translations teams, each team assigned for doing translations in a specific language. The have names like "Launchpad Swedish Translators". Members of such translations teams have permissions for translation into the language appointed for their team. We believe that people translating software in the same language should work in the same team, even thought they are working at different software.
Line 11: Line 11:
 * There is one "[[https://launchpad.net/~lp-translators | Launchpad Translators]]" team gathering all persons involved in translating or managing translations using Launchpad Translators. There is one Launchpad localization team appointed for each language.
Line 13: Line 13:
 * On the following page you can check the [[Translations/GuidesList | translation guide for your 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 15: Line 15:
 * The development or this group is discussed [[https://blueprints.edge.launchpad.net/rosetta/+spec/launchpad-translators-group | in this blueprint]] We also encourage project maintainers to appoint the '''Launchpad Translators''' group as the translation group for their project.
Line 17: Line 17:
= Goal and Purpose = = Project Maintainers =
Line 19: Line 19:
== Launchpad Translators group ==
Launchpad Translators group is a set of teams and individual supervisors working on translating software hosted in Launchpad.
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.
Every project needs high quality translation that convey with the cultural background and the already established guidelines of each language.
Line 23: Line 21:
Project maintainers should be able to trust Launchpad Translators Group and appoint it to manage translations for their projects in all languages. The '''Launchpad Translators''' group stands for those goals. Here you can find a list of steps to follow in order to use Launchpad Translations as the translation tool for you project and have it translated into many languages.
Line 25: Line 23:
== Launchpad translation teams ==
Launchpad translations teams are groups of translators doing translations in a specific language for projects hosted in Launchpad.
 * Before proceeding, please take a moment and see how you can use Launchpad and what you should do in order to have your project translated. You can find these information at [[https://help.launchpad.net/Translations/YourProject | Translating your project help pages]].
Line 28: Line 25:
There is one Launchpad translation team assigned for each language.  * Choose a translation permissions policy and appoint the "Launchpad Translators" group for doing the translation. Follow this link to find more info about [[https://help.launchpad.net/Translations/YourProject/PermissionPolicies | Choosing permissions policy]]. We recommend using the ''Structured'' policy, as a measure to assure translation quality.
Line 30: Line 27:
All members of Launchpad translation teams should be experts in translating software and be aware about the work of other teams from Launchpad or other translations project working outside of Launchpad.  * The direct link to your project permissions policy is: [[https://translations.launchpad.net/<YOUR-PROJECT-NAME>/+settings]].
Line 32: Line 29:
Launchpad translation teams are not the only translation groups in the free software ecosystem. We are aware of other translation groups or projects like the Gnome Translation Project, The Translation Project (GNU), OpenOffice.org or Mozilla localization teams and we promote the collaboration with these projects.  * 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.
Line 34: Line 31:
= Working with Launchpad translators =  * You can also send an initial message to the [[https://launchpad.net/~launchpad-translators | Launchpad Translators Team]] and let them know about your project.
Line 36: Line 33:
== Project maintainers ==  * 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.
Line 38: Line 35:
Below is a list of steps you might follow in order to start using Launchpad Translations (Rosetta) and have your project translated in many languages.  * 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 at the problems and assign them to the proper team or person.
Line 40: Line 37:
 * 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 | Launchpad Translations help pages]]  * 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.
Line 42: Line 39:
 * 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]]. = Translators =
Line 44: Line 41:
 * The direct link to your project permissions policy is: https://translations.launchpad.net/<YOUR-PROJECT-NAME>/+changetranslators. All members of a Launchpad localization teams should be knowledgable in translating software into their own language, be aware about the work of other localization teams and about other translation projects.
Line 46: Line 43:
 * Use the Launchpad Translators team announcement list for announcing things that affect all languages (ex. new release, major string changes, string freeze... etc) or each team for things affecting only one language - LINK TO LIST Below is a list of steps you might follow in order to start using Launchpad Translations for translating your favorite project or distributions.
Line 48: Line 45:
 * If there are any translations errors or bug in your project please assign them to the Launchpad Translators team. We will look into the problem and assign them to the proper team or person.- LINK TO TEAM  * Before doing any translation work please take a moment and learn how to use Launchpad as your translation tool. For more information [[https://help.launchpad.net/Translations/StartingToTranslate | check the Launchpad Translations help pages]].
Line 50: Line 47:
 * In case in your project's Answers section people ask about specific translations or localization matters, you can assign those questions to the Launchpad Translators teams. We will try to analyze it and have a knowledgable person take care or it. - LINK TO TEAM  * Consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | list of translations teams]] and check the team assigned to 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 on how to create a new team.
Line 52: Line 49:
== Translators ==

Below is a list of steps you might follow in order to start using Launchpad Translations (Rosetta) for translating your favorite project of distribution in 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. You can find more information about creating a new team at the end of this page.

 * 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 procedure for joining the team for your language. Before joining a team you might be asked to do some translation in order to test your translation skills.
Line 64: Line 53:
 * Follow the translation guide for your language. You can find it in the list of [[Translations/GuidesList | translation guides]]  * You may want to join the [[https://launchpad.net/~launchpad-translators | Launchpad Translators mailing list]] and get in touch with other translators and teams.
Line 66: Line 55:
= Launchpad Localization Teams =
Line 67: Line 57:
 * When translating downstream always check with the upstream project and commit your changes. Launchpad localization teams are the driving force behind the Launchpad translation process. Each localization team will translate and check translations on behalf of the language appointed to it.
Line 69: Line 59:
= Managing a team = Launchpad Translators Group will only have one team appointed to each language.
Line 71: Line 61:
Below you will find general information about managing a team and running a translation team: To check the current status of Launchpad Translators Group, please consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | list of Launchpad localization teams]]:
 * If your language does not appear in the list, please consider starting a new team for your language.
 * If your language is in the list, please consider joining that team (or request that your current team to be added as a subteam).
Line 73: Line 65:
 * Create a webpage / wiki where people could find general information about your team, such as:
  * short and long term team goal
  * new membership acceptance conditions
  * translation guide
  * common terminology (ex a link to a glossary, terminology list, dictionary)
  * how to get in contact with the team (team contact or team members)
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://launchpad.net/%7Elaunchpad-translators-leaders/+contactuser | contacting the Launchpad Translation Coordinators]].
Line 80: Line 67:
 * Add your translation guide for your language to the list of [[Translations/GuidesList | translation guides]] == Steps to Follow for Appointing a Team ==
Line 82: Line 69:
 * Make sure the team act as a team.
  * Keep the team members up to date with the latest actions
  * keep in contact with team members and try to collect feadback and status
 * As the coordintor of a Launchpad localization team, it is higly recommended to join the [[https://launchpad.net/~launchpad-translators | Launchpad Translators mailing list]].
Line 86: Line 71:
 * From time to time take a look at what other people are doing. In many cases you are not the only team/person translationg software in your language.  * If you don't have a Launcpad team dedicated to translations into your language, please [[https://launchpad.net/people/+newteam |create a new Launchpad localization team]]. 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.
Line 88: Line 73:
== Quality assurance ==
 
Below is a list of ways you can improve the translations quality.
 * 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 for your language/team.
  * [[Translations/Guidelines | Let Launchpad know about your translation guidelines]].
Line 92: Line 77:
 * when you have translated a string, read it again and see if there are any error or the translations sound right in your language. If the translated string does not make sense for you, definelty it is wrong and you should redo/rephrase it.  * Ask [[https://launchpad.net/~launchpad-translations-coordinators/+contactuser | Launchpad Translators Coordinators]] to appoint your language. Please specify the name of the language and the name of the team.
Line 94: Line 79:
 * Translations consistency is an important aspect of translation quality. You can check the translation of a word / phrase in multiple free software project using the [[http://open-tran.eu/ Open Tran]] website
 
== Common/best practice ==
 * As the coordinator, you are the primary contact person for the team and the person who make things happen.
Line 98: Line 81:
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 translation 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 finished 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, translations 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, definitely 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 tile". The original text is not always the correct one.
   * a common terminology or a link to a common terminology 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 together
 
 * Make sure you have a good communication channel for all members of the team or subteam. Try to reach all communication types: mailinglist, forum, IRC channel.

= 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 new Launchpad team for a language and asking to be assigned for that language is only required if already there is no team appointed for that language.

To check the current status you can consult the [[https://translations.launchpad.net/+groups/launchpad-translators/ | Launchpad Translators Group in Rosetta]].

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.
To do so please ask one of the Launchpad team administrators assigned for you language.

If the Launchpad team assigned for your language is no longer active, please let us know by [[https://answers.launchpad.net/rosetta | filling an answer in Launchpad Translations (Rosetta)]].

Steps to follow for creating a team and appointing to a language.
 * Join the launchpad translators discussions/announcements 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 hints from our best practices section and adapt them to your language/team
  * Add your translation guide for your language to the list of [[Translations/GuidesList | translation guides]]

 * If you translation karma is over 5000 go to the final step
 * 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.
 * '''Final step''' - create a lp-l10n-CC team and ask [[https://edge.launchpad.net/%7Elaunchpad-translators-leaders/+contactuser | Launchpad Translators Leaders]] to appoint a your language to this team. We use iso-639 two letters code and if not available we fallback to three letters code.
||<tablestyle="width: 100%;"> ~-[[Translations/TranslationGroups|< Translations Groups]] -~ ||<style="text-align: right;"> ~- [[Translations| Translations help page >]] -~ ||

Launchpad Help > Translations > Translators and Translation Teams in Launchpad

Overview

The Launchpad Translators group is a set of teams and individuals working on translating software hosted in Launchpad. It is a confederation of translation teams, it is not yet another translation project.

We believe that people translating software in the same language should work in the same team, even thought they are working at different software.

There is one Launchpad localization team appointed for each 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.

We also encourage project maintainers to appoint the Launchpad Translators group as the translation group for their project.

Project Maintainers

Every project needs high quality translation that convey with the cultural background and the already established guidelines of each language.

The Launchpad Translators group stands for those goals. Here you can find a list of steps to follow in order to use Launchpad Translations as the translation tool for you project and have it translated into many languages.

  • Before proceeding, please take a moment and see how you can use Launchpad and what you should do in order to have your project translated. You can find these information at Translating your project help pages.

  • Choose a translation permissions policy and appoint the "Launchpad Translators" group for doing the translation. Follow this link to find more info about Choosing permissions policy. We recommend 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>/+settings.

  • You can contact the Launchpad Translators Team for announcing things that affect all languages (ex. approaching release, major string changes, string freeze... etc.) or a specific language team for things affecting only one language.

  • You can also send an initial message to the 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 Launchpad Translators team. We will look at the problems 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 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 own language, be aware about the work of other localization teams and about other translation projects.

Below is a list of steps you might follow in order to start using Launchpad Translations for translating your favorite project or distributions.

  • Before doing any translation work please take a moment and learn how to use Launchpad as your translation tool. For more information check the Launchpad Translations help pages.

  • Consult the list of translations teams and check the team assigned to 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 on how to create 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 test your translation skills.
  • Follow the rules of your team, communicate and keep in touch with the team.
  • You may want to join the Launchpad Translators mailing list and get in touch with other translators and teams.

Launchpad Localization Teams

Launchpad localization teams are the driving force behind the Launchpad translation process. Each localization team will translate and check translations on behalf of the language appointed to it.

Launchpad Translators Group will only have one team appointed to each language.

To check the current status of Launchpad Translators Group, please consult the list of Launchpad localization teams:

  • If your language does not appear in the list, please consider starting a new team for your language.
  • If your language is in the list, please consider joining that team (or request that your current team to be added as a subteam).

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 contacting the Launchpad Translation Coordinators.

Steps to Follow for Appointing a Team

< Translations Groups

Translations help page >

Translations/LaunchpadTranslators (last edited 2010-12-23 13:33:10 by 94)