aly/servatrice
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

fixed typos

Browse source
This commit is contained in:
tooomm 2015-04-29 15:30:30 +02:00
parent 5410afbbb1
commit 1af358c4df
1 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
CONTRIBUTING.md
View file

@ -136,11 +136,11 @@ as `QScopedPointer`, or, less preferably, `QSharedPointer`.
### Translations: introduction ### ### Translations: introduction ###
Basic workflow for translations: Basic workflow for translations:
1. developer adds a tr("foo") string in the code; 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; 2. every few days, a maintainer updates the `*_en.ts files` adding the new strings;
3. Trasifex picks up the new files from github every 24 hours; 3. Transifex picks up the new files from github every 24 hours;
4. translators translate the new untraslated strings on Transifex; 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) ### ### 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 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, 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, 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. 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 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 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 of new strings have been added, a maintainer should take care of extracing all
the new strings and add them to the english translation. the new strings and add them to the english translation files.
To update the english translation files, re-run cmake enabling the appropriate To update the english translation files, re-run cmake enabling the appropriate
parameter and then run make: 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 and update the interface where translators will be able to translate the new
strings. 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 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. translations from Transifex and commit them into the Cockatrice source code.