Changes

From SME Server
Jump to navigationJump to search
1,167 bytes removed ,  12:15, 1 March 2008
updates
Line 25: Line 25:  
*[[Bugzilla:3782]]  
 
*[[Bugzilla:3782]]  
   −
== revision control using CVS/SVN ==
+
== Subversion ==
   −
Today I had a quick look at the pootle pages and found a wiki as well, which has some valuable information like for instance revision control using CVS/SVN: http://translate.sourceforge.net/wiki/pootle/version_control - [[User:Cactus|Cactus]] 03:26, 25 January 2008 (MST)
+
Translations are under version control.
:I have setup a SVN repository and linked with Pootle. Run very well, but I want to setup this repo with commit (write) access authenticate, and public read-only access. I have setup with smeserver-subversion and the only authenticate option work for read and write. Can you help me?
     −
:For this reason I do not want to reveal the SVN address, and only is browsable via trac at http://www.unixlan.com.ar/viewvc
+
The subversion repository is browseable via trac at http://www.unixlan.com.ar/viewvc
   −
:Users can't use the "update" function within pootle because I have disabled. Only can "commit". I have add a cron entry to auto-commit every 15 minutes.
+
Translators may commit file changes after you have finished your translation work (partially or totally). For this, you must click at the top language menu "Show Editing Functions" link, and then click at the "Commit" link of the file you have translated.  
:I have added the following text at the top of each project in pootle:
     −
:'''''You can (must) commit your file changes everytime you have finished your tranlation work (partially or totally). For this, you must click at the top language menu "Show Editing Functions" link, and then click at the "Commit" link of the file you have translated. The system also has an automatic commit every 15 minutes, but not append your username in the svn commit log.'''''
+
The system also has an automatic commit every 15 minutes,
:--[[User:PicsOne|Normando Hall]] 23:14, 21 February 2008 (MST)
+
this doesn't append your username in the svn commit log.
   −
 
+
Developers upload new or updated .pot files in the templates repository.  
A few links for future implementation: (not delete this links, maybe are usesful when we implement an automatic commit)
+
Changes are pushed to the other language .po files automatically.
:http://subversion.tigris.org/tools_contrib.html#po_update_sh
  −
:http://subversion.tigris.org/tools_contrib.html#verify_po_py
  −
:http://subversion.tigris.org/tools_contrib.html#svnmerge_py
  −
:http://subversion.tigris.org/tools_contrib.html#svnmerge_sh
      
==Translation Workflow==
 
==Translation Workflow==
Line 51: Line 45:  
===.po files===
 
===.po files===
 
*gettext strings are in various files in cvs  
 
*gettext strings are in various files in cvs  
: we use xgettext to creates .po files from the original files to by extracting gettext strings [1]
+
: we use xgettext to creates .pot files from the original files to by extracting gettext strings [1]
: we load these into pootle as .pot template files and update other languages from these
+
: developers load these into pootle as .pot template files using subversion
    
* .po files have been converted to UTF-8, they will be converted back to ISO-8859-1 when patching SME
 
* .po files have been converted to UTF-8, they will be converted back to ISO-8859-1 when patching SME
    
*changes to original files, ie changed gettext strings, have to be tracked as usual in the bug tracker
 
*changes to original files, ie changed gettext strings, have to be tracked as usual in the bug tracker
: these are imported into the templates and other languages by above method
+
: these are imported into the template .pot files using subversion
    
*at some point we diff updated po files against cvs po files, the patch is checked and applied.
 
*at some point we diff updated po files against cvs po files, the patch is checked and applied.
Line 64: Line 58:  
*these are XML files with a <base> and <trans> pair of strings
 
*these are XML files with a <base> and <trans> pair of strings
 
: we create .po files from the english versions [2]
 
: we create .po files from the english versions [2]
: using subversion we load these into pootle as .pot template files and update other languages from these
+
: using subversion we load these into pootle as .pot template files
    
* changes to original files, have to be tracked as usual in the bug tracker
 
* changes to original files, have to be tracked as usual in the bug tracker
: new <base> strings only have to be added (or removed) to the cvs xml file for english
+
: <base> strings only have to be added (or removed) to the cvs xml file for english
    
*at some point we apply the new translation back to the xml file [3]   
 
*at some point we apply the new translation back to the xml file [3]   

Navigation menu