2,569
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 92:
Line 92: − ===progress===+ − we'll look at this later, perhaps starting with contribs − :A few links for future implementation: + + + +
→revision control using CVS/SVN
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)
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)
A few links for future implementation:
:http://subversion.tigris.org/tools_contrib.html#po_update_sh
: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#verify_po_py
:http://subversion.tigris.org/tools_contrib.html#svnmerge_py
:http://subversion.tigris.org/tools_contrib.html#svnmerge_py
:http://subversion.tigris.org/tools_contrib.html#svnmerge_sh
:http://subversion.tigris.org/tools_contrib.html#svnmerge_sh
OR, we can probably script the creation of a patch, this can be reviewed and committed in a patch,
this is close to how we add to cvs now
== Remarks ==
== Remarks ==
