launchpad help|
Size: 3900
Comment:
|
Size: 3136
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''DRAFT: this page is a work in progress. Please [:Feedback:seek further help] or check the [:TitleIndex:wiki index] for a complete page on this topic.''' | ~-[[FrontPage|Launchpad Help]] > [[Translations]] > Your project -~ |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">[[TableOfContents]]|| | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 11: | Line 11: |
| * anyone can translate or suggest translations * translations are automatically shared between projects. Importantly, Launchpad's simple web interface makes it easy for anyone to help translate your software, while its support of the popular GNU GetText file formats makes it easy to integrate their work into your project. |
* anyone can translate and/or suggest translations * translations are easily shared between projects. Importantly, Launchpad's simple web interface provides a friendly environment in which non-technical people can help translate your software, while its support of the popular GNU Get``Text file formats makes it easy to integrate their work into your project. = Licensing = ||<style="background: #2a2929; font-weight: bold; color: #f6bc05;">Important:|| We require that all translations '''made in Launchpad''' are BSD licensed. This does not apply to translations imported from elsewhere. [[Translations/LicensingFAQ|Read more about translation licensing]].|| |
| Line 20: | Line 27: |
| 1. Enable translation on your project's ```Change details``` page - ```https://launchpad.net/<yourproject>/+edit``` 1. Upload a translation template. |
1. Enable translation by following the ```Change details``` link on your project's overview page and selecting ```Translations for this project are done in Launchpad```. 1. Upload a translation template and any existing translation files to the series you want to translate. |
| Line 23: | Line 30: |
| Let's take a look at those last two, in turn. | |
| Line 26: | Line 31: |
| = Uploading a translation template = | Let's take a look at those in more detail. |
| Line 28: | Line 33: |
| Launchpad uses GNU GetText's file formats to import and and export translations: | == Preparing your software for translation == Launchpad uses GNU gettext's file formats to import and and export translations: |
| Line 31: | Line 38: |
| * '''.po:''' the translations for a particular language. * '''.mo:''' |
* '''.po:''' translations for one language in a human-readable and editable form. * '''.mo:''' a compiled binary form of a .po file. |
| Line 34: | Line 41: |
| You can find out more about these file formats and using GNU gettext in the [[http://www.gnu.org/software/gettext/manual/gettext.html|GetText manual]]. | |
| Line 35: | Line 43: |
| ||<tablestyle="width: 100%;" style="width: 10%; background: #2a2929; font-weight: bold; color: #f6bc05;">Quick tip:|| You may also find Malcolm Tredinnick's [[http://www.gnome.org/~malcolm/i18n/|Gnome internationalisation guide]] useful, although some of the Gnome policies mentioned in that guide are now out of date.|| | |
| Line 36: | Line 45: |
| Before anyone can translate your project, you need to upload your software's English user-interface text. | To make your project available for translation, you must upload at least one .pot translation template file. This file tells Launchpad which English strings you want to make available for translation. |
| Line 38: | Line 47: |
| By default, translation is switched off for all new projects. This helps avoid wasted work. | = Next steps = |
| Line 40: | Line 49: |
| To enable translations for your project, visit | Let us now look at how to [[Translations/YourProject/ImportingTemplates|get your translation templates into Launchpad]]. |
| Line 42: | Line 51: |
Use the first two paragraphs to summarise all the important points about this article. Tell the reader if this is the information they need as soon as possible. = Instructional text = Where appropriate, use step by step instructions: '''Step 1:''' Give concise and unambiguous instructions. '''Step 2:''' Try not to state the obvious, unless you're writing for a novice user. {i} '''Note:''' Highlight important information with a note. '''Step 3:''' Use a well cropped screen shot if it will help orient the reader. Don't let the screen shot replace instructional text: not everyone can see your screen shot. Don't worry about borders or annotation for small, cropped screen shots such as this. attachment:screen-shot.png {i} '''Warning:''' If you're about to tell the reader to delete or otherwise change something that would be hard to restore, warn them. == Full screen shots == ||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">attachment:proj-announce.png|| ||<style="text-align: center;">'''Describe the screen shot here'''|| Some screen shots will be better placed to the right of your text. As they're not placed directly below the text that they support, use a border and short description. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam sagittis. Aliquam eros dui, scelerisque id, consequat in, accumsan vitae, pede. Suspendisse neque ligula, scelerisque ac, mattis ut, aliquam quis, odio. Proin nunc nisi, fringilla ac, congue ac, luctus eu, lacus. Maecenas ac purus. Cras felis metus, ultricies non, euismod ac, accumsan eleifend, leo. Quisque imperdiet tempus tellus. Ut euismod, diam nec adipiscing interdum, tortor orci fringilla nisi, vel blandit erat magna at nisi. Fusce hendrerit odio non metus. Mauris nisl massa, dapibus id, feugiat quis, blandit a, quam. Integer tincidunt feugiat nunc. Curabitur iaculis egestas elit. Nam imperdiet suscipit odio. |
||<tablestyle="width: 100%;"> ~-[[Translations/Guidelines|< Make guidelines visible to local translators]] -~ ||<style="text-align: right;"> ~- [[Translations/YourProject/ImportingTemplates|Importing translation templates >]] -~ || |
Launchpad Help > Translations > Your project
Overview
While development usually takes place in English, free software is used by people in hundreds of different languages across the globe.
Launchpad applies two of the great benefits of the open source development model to translating your software:
- anyone can translate and/or suggest translations
- translations are easily shared between projects.
Importantly, Launchpad's simple web interface provides a friendly environment in which non-technical people can help translate your software, while its support of the popular GNU GetText file formats makes it easy to integrate their work into your project.
Licensing
Important: |
We require that all translations made in Launchpad are BSD licensed. This does not apply to translations imported from elsewhere. Read more about translation licensing. |
Getting started
You need to do three things before people can use Launchpad to translate your project:
Enable translation by following the Change details link on your project's overview page and selecting Translations for this project are done in Launchpad.
- Upload a translation template and any existing translation files to the series you want to translate.
- Choose a permissions policy - i.e. decide who can make what sorts of changes to your translations.
Let's take a look at those in more detail.
Preparing your software for translation
Launchpad uses GNU gettext's file formats to import and and export translations:
.pot: a template that includes the English text that you want people to translate.
.po: translations for one language in a human-readable and editable form.
.mo: a compiled binary form of a .po file.
You can find out more about these file formats and using GNU gettext in the GetText manual.
Quick tip: |
You may also find Malcolm Tredinnick's Gnome internationalisation guide useful, although some of the Gnome policies mentioned in that guide are now out of date. |
To make your project available for translation, you must upload at least one .pot translation template file. This file tells Launchpad which English strings you want to make available for translation.
Next steps
Let us now look at how to get your translation templates into Launchpad.
