Update i18n docs
This commit is contained in:
parent
75212feefd
commit
5a25fc1ed8
3 changed files with 15 additions and 10 deletions
|
@ -2,22 +2,21 @@
|
||||||
|
|
||||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10669) in GitLab 9.2.
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10669) in GitLab 9.2.
|
||||||
|
|
||||||
For working with internationalization (i18n) we use
|
For working with internationalization (i18n),
|
||||||
[GNU gettext](https://www.gnu.org/software/gettext/) given it's the most used
|
[GNU gettext](https://www.gnu.org/software/gettext/) is used given it's the most
|
||||||
tool for this task and we have a lot of applications that will help us to work
|
used tool for this task and there are a lot of applications that will help us to
|
||||||
with it.
|
work with it.
|
||||||
|
|
||||||
## Setting up GitLab Development Kit (GDK)
|
## Setting up GitLab Development Kit (GDK)
|
||||||
|
|
||||||
In order to be able to work on the [GitLab Community Edition](https://gitlab.com/gitlab-org/gitlab-ce) project we must download and
|
In order to be able to work on the [GitLab Community Edition](https://gitlab.com/gitlab-org/gitlab-ce)
|
||||||
configure it through [GDK](https://gitlab.com/gitlab-org/gitlab-development-kit), we can do it by following this [guide](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/set-up-gdk.md).
|
project you must download and configure it through [GDK](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/set-up-gdk.md).
|
||||||
|
|
||||||
Once we have the GitLab project ready we can start working on the
|
Once you have the GitLab project ready, you can start working on the translation.
|
||||||
translation of the project.
|
|
||||||
|
|
||||||
## Tools
|
## Tools
|
||||||
|
|
||||||
We use a couple of gems:
|
The following tools are used:
|
||||||
|
|
||||||
1. [`gettext_i18n_rails`](https://github.com/grosser/gettext_i18n_rails): this
|
1. [`gettext_i18n_rails`](https://github.com/grosser/gettext_i18n_rails): this
|
||||||
gem allow us to translate content from models, views and controllers. Also
|
gem allow us to translate content from models, views and controllers. Also
|
||||||
|
|
|
@ -13,6 +13,8 @@ Translating strings will help complete and improve each language.
|
||||||
|
|
||||||
## How to contribute
|
## How to contribute
|
||||||
|
|
||||||
|
There are many ways you can contribute in translating GitLab.
|
||||||
|
|
||||||
### Externalize strings
|
### Externalize strings
|
||||||
|
|
||||||
Before a string can be translated, it must be externalized.
|
Before a string can be translated, it must be externalized.
|
||||||
|
@ -69,6 +71,6 @@ Requests to become a proof reader will be considered on the merits of previous t
|
||||||
|
|
||||||
If you would like to be added as a proof reader, please [open an issue](https://gitlab.com/gitlab-org/gitlab-ce/issues).
|
If you would like to be added as a proof reader, please [open an issue](https://gitlab.com/gitlab-org/gitlab-ce/issues).
|
||||||
|
|
||||||
### Release
|
## Release
|
||||||
|
|
||||||
Translations are typically included in the next major or minor release.
|
Translations are typically included in the next major or minor release.
|
||||||
|
|
|
@ -4,6 +4,8 @@ For managing the translation process we use [Crowdin](https://crowdin.com).
|
||||||
|
|
||||||
## Using Crowdin
|
## Using Crowdin
|
||||||
|
|
||||||
|
The first step is to get familiar with Crowdin.
|
||||||
|
|
||||||
### Sign In
|
### Sign In
|
||||||
|
|
||||||
To contribute translations at [translate.gitlab.com](https://translate.gitlab.com)
|
To contribute translations at [translate.gitlab.com](https://translate.gitlab.com)
|
||||||
|
@ -37,6 +39,8 @@ Remember to **Save** each translation.
|
||||||
|
|
||||||
## Translation Guidelines
|
## Translation Guidelines
|
||||||
|
|
||||||
|
Be sure to check the following guidelines before you translate any strings.
|
||||||
|
|
||||||
### Technical terms
|
### Technical terms
|
||||||
|
|
||||||
Technical terms should be treated like proper nouns and not be translated.
|
Technical terms should be treated like proper nouns and not be translated.
|
||||||
|
|
Loading…
Reference in a new issue