How to translate into your language

The following instructions are work in progress. Translations are usually coordinated inside the L10n teams, please check with them first.

Get the English file you want to translate

The blog articles are written using ?MarkDown and these "source code" files are hosted in a git repository in Salsa, the Debian source code forge. You can use git and Salsa to work with translations, or you can just download the ?MarkDown file that you want to translate, translate it, and send it to your language team for review and upload, if you prefer to work without using Git or Salsa.

Get the file without using Git/Salsa

Get the markdown file of the article you want to translate from here:

(e.g. for the article about Debian 25 anniversary you can go to and then press the "Download" button).

Get the file using Git/Salsa

If you prefer to work with Salsa, Debian's Gitlab instance, but still don't have account, create a guest account: (your account name will be something like USER-guest)

Then login and go to the Publicity group in Salsa:

You can fork the "bits" repository (create a local copy in your userspace in Salsa), and send Merge Requests with your contributions, or request to join the Publicity group to get commit permissions directly in the bits repo.

If you are Debian Developer, you already have commit access, no need to join the publicity group in Salsa.

If this is the first time you are working with git, you will need to install git in your machine.

1. In your local machine, clone the git repository. Open a terminal and type:

or if you prefer to work with your fork and send merge requests via salsa, type:

If you already cloned the repo some time ago, just update your local copy with:

(or if you forked, the repo, see to configure your fork to be up-to-date with the Publicity team repository).

Prepare the post to translate

1. If you work inside a established translation group, they might have a process to reserve the file you want to translate; please follow it.

2. Copy the post you want to translate adding the suffix -XX, where XX is the code of the language, for example:

Now you can edit it with a text editor. The posts are in markdown so a editor with syntax highlight would make it easier.

3. Below the Tags line add the following line: Lang: es

where "es" should be the code for your language, "es" is the code for Spanish. Check the code for your language in this page

4. Add your name in an Translator line below the Author line:

Translator: Juana Smith

5. Change the Status line from "published" to "draft".

6. Check the header is something like this:

Title: translated title
Date: leave it as is
Tags: leave it as is
Slug: leave it as is
Author: translate the "and" (if several authors)
Translator: add name+surname, or nick
Lang: xx  (where xx is the language code, e.g. es for Spanish, tr for Turkish)
Status: draft

7. And now, finally, translate the Title line and the text of the post! Beware of the markdown syntax. You can read about markdown at

Send your translation for review/upload

You can send your translated file to the mailing list of your language team for others to review and upload. If you have no language team, or the review process is already done and you need the publicity team to upload the translation, you can send the file to the debian-publicity mailing list requesting an upload, or you can use git and Salsa to send a Merge Request or commit directly the file.

Push your translation in git

If you prefer to upload your translation yourself, using git, then commit the post and push it:

    $ git add content/2018/
    $ git commit -m "lang xx: initial translation post foo"
    $ git push 

If you were maintaining a fork in Salsa, the push will be sent to your local copy in Salsa; send a Merge Request to the Publicity team repository to get your translation into the original bits repo.