Willing to make using Tails easier in your own language? Welcome aboard!
Most of Tails developers are not native English speakers so you're more than welcome to correct or improve our English. For this, you can either follow the Git workflow or propose another way that suits you better to share your improvements with us.
You can help correct, improve, or complete the translations of Tails programs and documentation into your native language:
- For French and Portuguese (Brazil), the existing translators team uses Git. So, read translating with Git.
- For other languages, read translating with Transifex.
Most of Tails can be translated directly online with Transifex:
- Tails Greeter
- Tails Persistence Setup
- Tails Installer
- Tails Upgrader
- Tails Perl library
- A set of various translatable strings
You are now doing translation work for Tails on Transifex. This is great, thanks!
- It would be awesome if you did follow-up on translation needs.
- You might want to translate the Tails website too.
For each custom program, you can download the PO files via Transifex or the Git web interface:
- Tails Greeter: PO files, see also the README for translators
- Tails Persistence Setup: PO files
- Tails Installer: PO files
- Tails Upgrader: PO files
- Tails Perl library: PO files
- WhisperBack: PO files, see also the README for translators
- Some smaller programs written for Tails: PO files
For the website, you can browse its source code via the Git web interface as well. Each page is translated in a specific PO file.
If there is no existing PO file for your language, you can copy and rename the
.pot file into a
Once your translation work is done, you can email it to the mailing list for translators.
On the long run, translators team often decide to use Git to share and synchronize their work, and ask us to integrate it within the official repositories.
Various bits of text can be translated:
- Custom programs (Tails Greeter, Tails Persistence Setup, Tails
Installer, Tails Upgrader, Tails Perl library and WhisperBack): each
one has its own Git repository, where PO files
live in the
podirectory. Some have a
README.translatorsat the root of their source tree: please read it.
- A set of various translatable strings live in the
podirectory, in the
develbranch of the main Tails Git repository.
- This website must be translated in the
masterbranch of the main Tails Git repository. Please note there are requirements to translate the website into a new language.
To edit these PO files, we recommend that you use Poedit, a cross-platform editor for PO files. Poedit is included in Tails.
If there is no existing PO file for your language, you can copy the
.pot file into a new
You can take advantage of Git to send us your work by asking us to pull from your Git branch. Here is the typical workflow used by Tails translators teams:
- Set up your personal Git repository: if you already know where to host it in a public place, this is great; else, fork us on repo.or.cz or ask the Tails system administrators to host your repository.
- Translate whatever you can in your preferred PO file editor.
- Commit the changes you made to
- Merge our main repository into yours.
- Push your changes to your online Git repository.
- Ask other members of your translation team to review your work.
- The reviewer, once happy with the result, should ask on the mailing list for translators to pull from the branch that was worked on.
You are now doing translation work for Tails using Git. This is great, thanks! It would be awesome if you did follow-up on translation needs.
Our custom programs can be translated using Transifex. Work done there is not automatically synchronized with the translations your team does in Git.
It is nice to minimize time wasted by unknown people who work, with Transifex, on the same thing as your translation team.
So, a translation team using Git should regularly contact Transifex
translators (listed in the
Last-translator field of the PO files one
can download from Transifex), either over email or using the Transifex
- Thank them for translating Tails stuff.
- Make it clear their work is not imported (and is therefore, well, useless).
- Invite them to join the team and share the team's preferred workflow.
- Invite them to subscribe to the mailing list for translators.
So, you want the Tails website to be available in a new language. Please keep in mind that it represents quite a lot of work.
Therefore, here are a few things that would be required in order to start translating the Tails website to a new language:
A team of translators, not just one person, is necessary. That also allows for peer reviews between the team, more flexibility for example when an important deadline arrives.
At least part of the team should subscribe to the mailing list for translators.
Since the content of the website is sensitive in terms of privacy protection, Tails developers need to establish contacts with trusted people to review the work from time to time.
For translations to be useful, they need to be maintained in the long run. This takes a few hours a month.
Once those conditions are fulfilled, the new team can start working on a first batch of translations.
The Tails custom programs, as documented earlier
Important parts of our website:
Do not hesitate to report the progress of your work on the mailing list for translators.
Translators coordinate on the tails-l10n mailing list (l10n stands for localization). Important changes to translatable strings are announced there.
Please subscribe to the list if you want to become a regular translator.
Any message sent to this list is stored in a public archive, so beware of what your email content and headers reveal about yourself: location, IP address, email subject and content, etc.
You can consult this archive to search for recent translation requests.
See also the tickets with the
Translate Type of work