fixed typos
This commit is contained in:
parent
5410afbbb1
commit
1af358c4df
1 changed files with 10 additions and 10 deletions
|
@ -136,11 +136,11 @@ as `QScopedPointer`, or, less preferably, `QSharedPointer`.
|
|||
### Translations: introduction ###
|
||||
|
||||
Basic workflow for translations:
|
||||
1. developer adds a tr("foo") string in the code;
|
||||
2. every few days, a mantainer updates the *_en.ts files adding the new strings;
|
||||
3. Trasifex picks up the new files from github every 24 hours;
|
||||
1. developer adds a `tr("foo")` string in the code;
|
||||
2. every few days, a maintainer updates the `*_en.ts files` adding the new strings;
|
||||
3. Transifex picks up the new files from github every 24 hours;
|
||||
4. translators translate the new untraslated strings on Transifex;
|
||||
5. before a release, a mantainer fetches the updated translations from Transifex.
|
||||
5. before a release, a maintainer fetches the updated translations from Transifex.
|
||||
|
||||
### Translations (for developers) ###
|
||||
|
||||
|
@ -151,17 +151,17 @@ If you're about to propose a change that adds or modifies any translatable strin
|
|||
in the code, you don't need to take care of adding the new strings to the
|
||||
translation files. Every few days, or when a lot of new strings have been added,
|
||||
someone from the development team will take care of extracing all the new strings,
|
||||
adding them to the english translation file and making them available to
|
||||
adding them to the english translation files and making them available to
|
||||
translators on Transifex.
|
||||
|
||||
### Translations (for mantainers) ###
|
||||
### Translations (for maintainers) ###
|
||||
|
||||
#### step 2: updating *_en.ts files ####
|
||||
#### Step 2: updating *_en.ts files ####
|
||||
|
||||
When new translatable strings have been added to the code, it would be nice to
|
||||
make them available to translators on Transifex. Every few days, or when a lot
|
||||
of new strings have been added, a mantainer should take care of extracing all
|
||||
the new strings and add them to the english translation.
|
||||
of new strings have been added, a maintainer should take care of extracing all
|
||||
the new strings and add them to the english translation files.
|
||||
|
||||
To update the english translation files, re-run cmake enabling the appropriate
|
||||
parameter and then run make:
|
||||
|
@ -191,7 +191,7 @@ Transifex will pick up the modified files automatically (checks every 24 hours)
|
|||
and update the interface where translators will be able to translate the new
|
||||
strings.
|
||||
|
||||
#### step 5: fetch new translations ####
|
||||
#### Step 5: fetch new translations from Transifex ####
|
||||
|
||||
Before rushing out a new release, it would be nice to fetch the most up to date
|
||||
translations from Transifex and commit them into the Cockatrice source code.
|
||||
|
|
Loading…
Reference in a new issue