2020-10-30 14:08:56 -04:00
---
2020-11-17 10:09:28 -05:00
stage: Manage
group: Import
2020-11-26 01:09:20 -05:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-30 14:08:56 -04:00
---
2017-09-26 17:15:19 -04:00
# Translating GitLab
2020-04-07 14:09:19 -04:00
For managing the translation process we use [CrowdIn ](https://crowdin.com ).
2017-09-26 17:15:19 -04:00
2020-04-07 14:09:19 -04:00
## Using CrowdIn
2017-09-26 17:15:19 -04:00
2020-04-07 14:09:19 -04:00
The first step is to get familiar with CrowdIn.
2017-10-09 05:36:07 -04:00
2017-09-26 17:15:19 -04:00
### Sign In
2019-10-11 02:06:27 -04:00
To contribute translations at < https: / / translate . gitlab . com >
2020-04-07 14:09:19 -04:00
you must create a CrowdIn account.
2017-09-26 17:15:19 -04:00
You may create a new account or use any of their supported sign in services.
### Language Selections
GitLab is being translated into many languages.
2021-03-09 13:09:41 -05:00
1. Find the language that you want to contribute to, in our
[GitLab Crowdin project ](https://crowdin.com/project/gitlab-ee ).
- If the language that you're looking for is available, proceed
to the next step.
- If the language you are looking for is not available,
[open an issue ](https://gitlab.com/gitlab-org/gitlab/-/issues?scope=all&utf8=✓&state=all&label_name[]=Category%3AInternationalization ). Notify our Crowdin
administrators by including `@gitlab-org/manage/import` in your issue.
- After the issue/Merge Request is complete, restart this procedure.
2020-12-07 13:10:36 -05:00
1. Next, you can view list of files and folders.
2021-03-09 13:09:41 -05:00
Select `gitlab.pot` to open the translation editor.
2017-09-26 17:15:19 -04:00
### Translation Editor
The online translation editor is the easiest way to contribute translations.
2020-04-07 14:09:19 -04:00
![CrowdIn Editor ](img/crowdin-editor.png )
2017-09-26 17:15:19 -04:00
1. Strings for translation are listed in the left panel
1. Translations are entered into the central panel.
2020-12-07 13:10:36 -05:00
Multiple translations are required for strings that contains plurals.
2017-09-26 17:15:19 -04:00
The string to be translated is shown above with glossary terms highlighted.
If the string to be translated is not clear, you can 'Request Context'
A glossary of common terms is available in the right panel by clicking Terms.
2017-10-06 12:16:42 -04:00
Comments can be added to discuss a translation with the community.
2017-09-26 17:15:19 -04:00
Remember to **Save** each translation.
2018-02-15 12:17:13 -05:00
## General Translation Guidelines
2017-09-26 17:15:19 -04:00
2017-10-09 05:36:07 -04:00
Be sure to check the following guidelines before you translate any strings.
2018-02-15 12:17:13 -05:00
### Namespaced strings
When an externalized string is prepended with a namespace, e.g.
`s_('OpenedNDaysAgo|Opened')` , the namespace should be removed from the final
translation.
For example in French `OpenedNDaysAgo|Opened` would be translated to
`Ouvert•e` , not `OpenedNDaysAgo|Ouvert•e` .
2017-09-26 17:15:19 -04:00
### Technical terms
2018-02-15 12:17:13 -05:00
Some technical terms should be treated like proper nouns and not be translated.
2017-09-26 17:15:19 -04:00
2018-02-15 12:17:13 -05:00
Technical terms that should always be in English are noted in the glossary when
2019-10-11 02:06:27 -04:00
using < https: / / translate . gitlab . com > .
2018-02-15 12:17:13 -05:00
This helps maintain a logical connection and consistency between tools (e.g.
`git` client) and GitLab.
2017-09-26 17:15:19 -04:00
### Formality
2020-05-25 23:08:02 -04:00
The level of formality used in software varies by language:
| Language | Formality | Example |
| -------- | --------- | ------- |
| French | formal | `vous` for `you` |
| German | informal | `du` for `you` |
2017-09-26 17:15:19 -04:00
2018-02-15 12:17:13 -05:00
You can refer to other translated strings and notes in the glossary to assist
determining a suitable level of formality.
2017-09-26 17:15:19 -04:00
2017-10-11 09:52:26 -04:00
### Inclusive language
2020-12-15 19:09:58 -05:00
[Diversity ](https://about.gitlab.com/handbook/values/#diversity ) is a GitLab value.
2018-02-15 12:17:13 -05:00
We ask you to avoid translations which exclude people based on their gender or
ethnicity.
In languages which distinguish between a male and female form, use both or
choose a neutral formulation.
2017-10-11 09:52:26 -04:00
2020-06-03 02:08:34 -04:00
<!-- vale gitlab.Spelling = NO -->
2017-10-11 09:52:26 -04:00
For example in German, the word "user" can be translated into "Benutzer" (male) or "Benutzerin" (female).
2017-10-11 17:31:03 -04:00
Therefore "create a new user" would translate into "Benutzer(in) anlegen".
2020-06-03 02:08:34 -04:00
<!-- vale gitlab.Spelling = YES -->
2017-10-11 09:52:26 -04:00
2017-09-26 17:15:19 -04:00
### Updating the glossary
To propose additions to the glossary please
2020-05-29 11:08:14 -04:00
[open an issue ](https://gitlab.com/gitlab-org/gitlab/-/issues?scope=all&utf8=✓&state=all&label_name[]=Category%3AInternationalization ).
2018-02-15 12:17:13 -05:00
## French Translation Guidelines
### Inclusive language in French
2020-06-03 02:08:34 -04:00
<!-- vale gitlab.Spelling = NO -->
2020-12-03 19:09:55 -05:00
In French, the "écriture inclusive" is now over (see on [Legifrance ](https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000036068906/ )).
2021-03-18 02:11:52 -04:00
So, to include both genders, write "Utilisateurs et utilisatrices" instead of "Utilisateur·rice·s".
2019-06-05 14:42:37 -04:00
When space is missing, the male gender should be used alone.
2020-06-03 02:08:34 -04:00
<!-- vale gitlab.Spelling = YES -->