short description on how to integrate pootle translations
This commit is contained in:
parent
3500b67a40
commit
c27d4f31ef
1 changed files with 33 additions and 0 deletions
33
stuff/pootle-updates.txt
Normal file
33
stuff/pootle-updates.txt
Normal file
|
@ -0,0 +1,33 @@
|
|||
We use a pootle server to allow online translation of our language data
|
||||
|
||||
The following text should give you guide lines on how to:
|
||||
- update and merge language data to (A) and from (B) the pootle server
|
||||
- change english original texts (C)
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
|
||||
A) update the pootle language files via svn
|
||||
- log in to the pootle server (thorax)
|
||||
- become root
|
||||
- su - pootle
|
||||
- svn up svn
|
||||
- svn stat svn
|
||||
- resolve potential conflicts
|
||||
|
||||
|
||||
B) commit pootle translations to svn
|
||||
- log in to the pootle server (thorax)
|
||||
- become root
|
||||
- su - pootle
|
||||
- use "svn stat" and "svn diff" to check local changes
|
||||
- svn up
|
||||
- resolve potential conflicts (svn stat)
|
||||
- svn commit
|
||||
|
||||
|
||||
C) update language template files (after changing english texts)
|
||||
- change the language.hdf file (of the base cryptobox or of a plugin)
|
||||
- run scripts/update_po_files.py
|
||||
- review the changes
|
||||
- commit the changes
|
||||
|
Loading…
Reference in a new issue