summaryrefslogtreecommitdiff
path: root/doc/development
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2019-09-25 03:06:21 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2019-09-25 03:06:21 +0000
commit7bb7a8d529fd1155a35a2e9e9cdddd7953f3776d (patch)
treee0cedf3ea8732ab14cd918242279619c3c7d7072 /doc/development
parent504ab1e32cbd3a529fe61f6c9a30823febce796c (diff)
downloadgitlab-ce-7bb7a8d529fd1155a35a2e9e9cdddd7953f3776d.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development')
-rw-r--r--doc/development/i18n/externalization.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/development/i18n/externalization.md b/doc/development/i18n/externalization.md
index a97719fe901..ff75ba8c73b 100644
--- a/doc/development/i18n/externalization.md
+++ b/doc/development/i18n/externalization.md
@@ -313,17 +313,22 @@ Developer documentation][mdn].
## Updating the PO files with the new content
-Now that the new content is marked for translation, we need to update the PO
-files with the following command:
+Now that the new content is marked for translation, we need to update
+`locale/gitlab.pot` files with the following command:
```sh
bin/rake gettext:regenerate
```
-This command will update the `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
file in. Once the changes are on master, they will be picked up by
-[Crowdin](http://translate.gitlab.com) and be presented for translation.
+[Crowdin](http://translate.gitlab.com) and be presented for
+translation.
+
+We don't need to check in any changes to the
+`locale/[language]/gitlab.po` files. Those will be updated in a [when
+translations from Crowdin are merged](merging_translations.md).
If there are merge conflicts in the `gitlab.pot` file, you can delete the file
and regenerate it using the same command.