Commit 6a933340 authored by Marcia Ramos's avatar Marcia Ramos

Merge branch 'docs-crowdin-caps' into 'master'

Update capitalization of CrowdIn

See merge request gitlab-org/gitlab!28990
parents c2db4e3e 1321b165
...@@ -455,11 +455,11 @@ bin/rake gettext:regenerate ...@@ -455,11 +455,11 @@ bin/rake gettext:regenerate
This command will update `locale/gitlab.pot` file with the newly externalized This command will update `locale/gitlab.pot` file with the newly externalized
strings and remove any strings that aren't used anymore. You should check this strings and remove any strings that aren't used anymore. You should check this
file in. Once the changes are on master, they will be picked up by file in. Once the changes are on master, they will be picked up by
[Crowdin](https://translate.gitlab.com) and be presented for [CrowdIn](https://translate.gitlab.com) and be presented for
translation. translation.
We don't need to check in any changes to the `locale/[language]/gitlab.po` files. We don't need to check in any changes to the `locale/[language]/gitlab.po` files.
They are updated automatically when [translations from Crowdin are merged](merging_translations.md). They are updated automatically when [translations from CrowdIn are merged](merging_translations.md).
If there are merge conflicts in the `gitlab.pot` file, you can delete the file If there are merge conflicts in the `gitlab.pot` file, you can delete the file
and regenerate it using the same command. and regenerate it using the same command.
......
...@@ -30,7 +30,7 @@ See [Externalization for GitLab](externalization.md). ...@@ -30,7 +30,7 @@ See [Externalization for GitLab](externalization.md).
### Translate strings ### Translate strings
The translation process is managed at <https://translate.gitlab.com> The translation process is managed at <https://translate.gitlab.com>
using [Crowdin](https://crowdin.com/). using [CrowdIn](https://crowdin.com/).
You will need to create an account before you can submit translations. You will need to create an account before you can submit translations.
Once you are signed in, select the language you wish to contribute translations to. Once you are signed in, select the language you wish to contribute translations to.
...@@ -51,4 +51,4 @@ able to proofread and instructions on becoming a proofreader yourself. ...@@ -51,4 +51,4 @@ able to proofread and instructions on becoming a proofreader yourself.
Translations are typically included in the next major or minor release. Translations are typically included in the next major or minor release.
See [Merging translations from Crowdin](merging_translations.md). See [Merging translations from CrowdIn](merging_translations.md).
# Merging translations from Crowdin # Merging translations from CrowdIn
Crowdin automatically syncs the `gitlab.pot` file with the Crowdin service, presenting CrowdIn automatically syncs the `gitlab.pot` file with the CrowdIn service, presenting
newly added externalized strings to the community of translators. newly added externalized strings to the community of translators.
[GitLab Crowdin Bot](https://gitlab.com/gitlab-crowdin-bot) also creates merge requests [GitLab CrowdIn Bot](https://gitlab.com/gitlab-crowdin-bot) also creates merge requests
to take newly approved translation submissions and merge them into the `locale/<language>/gitlab.po` to take newly approved translation submissions and merge them into the `locale/<language>/gitlab.po`
files. Check the [merge requests created by `gitlab-crowdin-bot`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&author_username=gitlab-crowdin-bot) files. Check the [merge requests created by `gitlab-crowdin-bot`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&author_username=gitlab-crowdin-bot)
to see new and merged merge requests. to see new and merged merge requests.
## Validation ## Validation
By default Crowdin commits translations with `[skip ci]` in the commit By default CrowdIn commits translations with `[skip ci]` in the commit
message. This is done to avoid a bunch of pipelines being run. Before message. This is done to avoid a bunch of pipelines being run. Before
merging translations, make sure to trigger a pipeline to validate merging translations, make sure to trigger a pipeline to validate
translations, we have static analysis validating things Crowdin translations, we have static analysis validating things CrowdIn
doesn't do. Create a new pipeline at `https://gitlab.com/gitlab-org/gitlab/pipelines/new` doesn't do. Create a new pipeline at `https://gitlab.com/gitlab-org/gitlab/pipelines/new`
(need Developer access permissions) for the `master-i18n` branch. (need Developer access permissions) for the `master-i18n` branch.
If there are validation errors, the easiest solution is to disapprove If there are validation errors, the easiest solution is to disapprove
the offending string in Crowdin, leaving a comment with what is the offending string in CrowdIn, leaving a comment with what is
required to fix the offense. There is an required to fix the offense. There is an
[issue](https://gitlab.com/gitlab-org/gitlab/issues/23256) [issue](https://gitlab.com/gitlab-org/gitlab/issues/23256)
suggesting to automate this process. Disapproving will exclude the suggesting to automate this process. Disapproving will exclude the
invalid translation, the merge request will be updated within a few invalid translation, the merge request will be updated within a few
minutes. minutes.
It might be handy to pause the integration on the Crowdin side for a It might be handy to pause the integration on the CrowdIn side for a
little while so translations don't keep coming. This can be done by little while so translations don't keep coming. This can be done by
clicking `Pause sync` on the [Crowdin integration settings clicking `Pause sync` on the [CrowdIn integration settings
page](https://translate.gitlab.com/project/gitlab-ee/settings#integration). page](https://translate.gitlab.com/project/gitlab-ee/settings#integration).
When all failures are resolved, the translations need to be double When all failures are resolved, the translations need to be double
...@@ -37,16 +37,16 @@ checked once more as discussed in [confidential issue](../../user/project/issues ...@@ -37,16 +37,16 @@ checked once more as discussed in [confidential issue](../../user/project/issues
When all translations are found good and pipelines pass the When all translations are found good and pipelines pass the
translations can be merged into the master branch. When merging the translations, translations can be merged into the master branch. When merging the translations,
make sure to check the **Remove source branch** checkbox, so Crowdin recreates the make sure to check the **Remove source branch** checkbox, so CrowdIn recreates the
`master-i18n` from master after the new translation was merged. `master-i18n` from master after the new translation was merged.
We are discussing [automating this entire process](https://gitlab.com/gitlab-org/gitlab/issues/19896). We are discussing [automating this entire process](https://gitlab.com/gitlab-org/gitlab/issues/19896).
## Recreate the merge request ## Recreate the merge request
Crowdin creates a new merge request as soon as the old one is closed CrowdIn creates a new merge request as soon as the old one is closed
or merged. But it won't recreate the `master-i18n` branch every or merged. But it won't recreate the `master-i18n` branch every
time. To force Crowdin to recreate the branch, close any [open merge time. To force CrowdIn to recreate the branch, close any [open merge
request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&author_username=gitlab-crowdin-bot) request](https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&author_username=gitlab-crowdin-bot)
and delete the and delete the
[`master-18n`](https://gitlab.com/gitlab-org/gitlab/-/branches/all?utf8=✓&search=master-i18n). [`master-18n`](https://gitlab.com/gitlab-org/gitlab/-/branches/all?utf8=✓&search=master-i18n).
......
This diff is collapsed.
# Translating GitLab # Translating GitLab
For managing the translation process we use [Crowdin](https://crowdin.com). For managing the translation process we use [CrowdIn](https://crowdin.com).
## Using Crowdin ## Using CrowdIn
The first step is to get familiar with Crowdin. The first step is to get familiar with CrowdIn.
### Sign In ### Sign In
To contribute translations at <https://translate.gitlab.com> To contribute translations at <https://translate.gitlab.com>
you must create a Crowdin account. you must create a CrowdIn account.
You may create a new account or use any of their supported sign in services. You may create a new account or use any of their supported sign in services.
### Language Selections ### Language Selections
...@@ -24,7 +24,7 @@ GitLab is being translated into many languages. ...@@ -24,7 +24,7 @@ GitLab is being translated into many languages.
The online translation editor is the easiest way to contribute translations. The online translation editor is the easiest way to contribute translations.
![Crowdin Editor](img/crowdin-editor.png) ![CrowdIn Editor](img/crowdin-editor.png)
1. Strings for translation are listed in the left panel 1. Strings for translation are listed in the left panel
1. Translations are entered into the central panel. 1. Translations are entered into the central panel.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment