Commit cde4a645 authored by Evan Read's avatar Evan Read

Merge branch 'bvl-don-t-update-po-files-docs' into 'master'

Blurb about not checking in changes to `.po` files

See merge request gitlab-org/gitlab!17497
parents afbca754 6921a75a
...@@ -313,17 +313,22 @@ Developer documentation][mdn]. ...@@ -313,17 +313,22 @@ Developer documentation][mdn].
## Updating the PO files with the new content ## Updating the PO files with the new content
Now that the new content is marked for translation, we need to update the PO Now that the new content is marked for translation, we need to update
files with the following command: `locale/gitlab.pot` files with the following command:
```sh ```sh
bin/rake gettext:regenerate 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 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](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 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.
......
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