Changes

Jump to navigation Jump to search
added latest screenshot
Line 36: Line 36:  
The final step in ensuring that the translations are merged back into the master source tree of the software is to "Commit" them. Committing is a pretty straightforward process, but you should ideally do it only after you have done the relevant checks and reviews. We recommend that you follow a 'release early and release often policy'<ref>http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html</ref> while committing, as that would get the maximum amount of exposure and testing for your translations.
 
The final step in ensuring that the translations are merged back into the master source tree of the software is to "Commit" them. Committing is a pretty straightforward process, but you should ideally do it only after you have done the relevant checks and reviews. We recommend that you follow a 'release early and release often policy'<ref>http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html</ref> while committing, as that would get the maximum amount of exposure and testing for your translations.
   −
To Commit, you will have to first click on the "Show Editing Functions" link in your main project page (the page which shows the list of PO files).
+
To Commit, click on the "Commit to VCS" link that appears below each file:
    +
[[Image:Translate-translate1.png]]
   −
[[Image:Pootle_admin_view1.png]]
+
..and you are done. If you don't see this link, it means "can commit to version control" permission is off. The link may also disappear if the contact with project repository is broken. Send a request to mailing list to fix this.
 
  −
 
  −
Once the Show Editing Functions link is activated, click on the "Commit" link below each PO file you want to commit.
  −
 
  −
 
  −
[[Image:Pootle_admin_view2.png]]
  −
 
  −
..and you are done.
      
=== Catching up with new strings to translate ===
 
=== Catching up with new strings to translate ===
21

edits

Navigation menu