... | ... | @@ -19,7 +19,14 @@ Now, for the string to exist on Transifex, we need to run the extraction from th |
|
|
|
|
|
Once the new strings are added to Transifex, translators can go and translate. After 24h, the translation files are updated on gcloud (from the first process above), and admin can manually update their translation files if they want to, or wait for the next CiviCRM release.
|
|
|
|
|
|
# Stack prerequisites
|
|
|
## Supported CiviCRM versions
|
|
|
|
|
|
* Latest RC
|
|
|
* Latest ESR
|
|
|
|
|
|
# Requirements
|
|
|
|
|
|
## Stack prerequisites
|
|
|
|
|
|
* Install Git, e.g. sudo apt-get install git
|
|
|
* Install [Transifex Client](https://docs.transifex.com/client/introduction/), e.g. `sudo easy_install transifex-client` or `sudo apt-get install transifex-client`
|
... | ... | @@ -27,7 +34,7 @@ Once the new strings are added to Transifex, translators can go and translate. A |
|
|
* Install the PHP command line interface (CLI) and MySQL bindings, e.g. `sudo apt-get install php-cli php-mysql`
|
|
|
* Install [civistrings](https://github.com/civicrm/civistrings) and composer, and have them available in your $PATH.
|
|
|
|
|
|
# Get a copy of the git repositories
|
|
|
## Get a copy of the git repositories
|
|
|
|
|
|
Clone [the Git repositories](https://github.com/civicrm/) from github:
|
|
|
|
... | ... | @@ -52,17 +59,14 @@ The "po" files use a different file hierarchy than the default Transif |
|
|
|
|
|
With Transifex, files are structured in the form of "civicrm.<component>/<lang>.po". In the l10n git repository, we use the structure "<lang>/<component>.po". It makes it easier to extract and compile only part of the translation. The magic for making this happen is in the file: l10n/.tx/config.
|
|
|
|
|
|
# Supported CiviCRM versions
|
|
|
|
|
|
* Latest RC
|
|
|
* Latest ESR
|
|
|
|
|
|
# Refreshing POT files
|
|
|
|
|
|
The .pot files are the source translation files that will be sent to Transifex for translation. They contain the source US-English strings.
|
|
|
|
|
|
We should regenerate the .pot files when a new release branch is created (ex: 5.14) when the new release goes RC (to allow translators a bit of time to translate before the official release). If we do not refresh the files, translators will not be able to find the string in Transifex.
|
|
|
|
|
|
In the following examples: 5.21 is the ESR and 5.22 is the RC.
|
|
|
|
|
|
To run the extraction process, run:
|
|
|
|
|
|
```
|
... | ... | |