Difference between revisions of "Babel / Large Contribution Import Process"

From Eclipsepedia

Jump to: navigation, search
Line 20: Line 20:
 
# 'run' the above file using wget: wget http://babel.eclipse.org/staging/import_XXXX_zip.php  <-- file name fudged to avoid crawlers
 
# 'run' the above file using wget: wget http://babel.eclipse.org/staging/import_XXXX_zip.php  <-- file name fudged to avoid crawlers
 
# Check the translations using the http://babel.eclipse.org/staging/recent.php
 
# Check the translations using the http://babel.eclipse.org/staging/recent.php
 +
# If something went wrong, you can still delete whatever you contributed by logging into the Mysql database and running this query for example (it deletes all the records contributed during the current day):
 +
<code lang="sql">delete from translations WHERE UNIX_TIMESTAMP(created_on) BETWEEN UNIX_TIMESTAMP(CURDATE()) AND UNIX_TIMESTAMP(DATE_ADD(CURDATE(), INTERVAL + 86399 SECOND));</code>
 +
  
  

Revision as of 09:16, 9 March 2009

This document describes the process the Babel committer uses to import large contributions into the Babel server.

Submitting such a contribution is documented here: http://www.eclipse.org/babel/development/large_contributions.php

Preparation

  1. Make sure the contribution follows the spec, and that is has been approved by Eclipse Legal by submitting it to IPZilla
  2. Unzip the file to babel.eclipse.org:/tmp/tmp-babel/import
  3. Inspect some files in each language to ensure they are properly encoded. Run/hack convertiso.sh as needed.
  4. Determine the accuracy of the contribution.
    1. Reviewed: Translations were done by professionals, and were reviewed and tested in context by loading them up in Eclipse
    2. Fuzzy: Translations were not done by professional translators; translations were done using software and dictionaries; translations were done by professional translators, but were not reviewed and tested in context.
    3. If unsure, ask the contributor. If unsure, choose Fuzzy.

Import on Staging

  1. su - genie
  2. copy the CVS version of import_translation_zip.php to the STAGING web root: cp /home/data/httpd/babel.eclipse.org/staging/classes/export/import_translation_zip.php /home/data/httpd/babel.eclipse.org/staging/html/import_translation_zip.php
  3. Edit /home/data/httpd/babel.eclipse.org/staging/html/import_translation_zip.php to ensure the target project_id and version are set (see note, below)
  4. Set the Fuzzy factor according to the accuracy of the contribution.
  5. 'run' the above file using wget: wget http://babel.eclipse.org/staging/import_XXXX_zip.php <-- file name fudged to avoid crawlers
  6. Check the translations using the http://babel.eclipse.org/staging/recent.php
  7. If something went wrong, you can still delete whatever you contributed by logging into the Mysql database and running this query for example (it deletes all the records contributed during the current day):

delete from translations WHERE UNIX_TIMESTAMP(created_on) BETWEEN UNIX_TIMESTAMP(CURDATE()) AND UNIX_TIMESTAMP(DATE_ADD(CURDATE(), INTERVAL + 86399 SECOND));


Import on Live

  1. su - genie
  2. copy the STAGING version of import_translation_zip.php to the LIVE web root: cp /home/data/httpd/babel.eclipse.org/staging/html/import_translation_zip.php /home/data/httpd/babel.eclipse.org/babel/html/import_translation_zip.php
  3. 'run' the above file using wget: wget http://babel.eclipse.org/babel/import_XXXX_zip.php <-- file name fudged to avoid crawlers
  4. Check the translations using the http://babel.eclipse.org/babel/recent.php
  5. Delete the import script: rm /home/data/httpd/babel.eclipse.org/babel/html/import_translation_zip.php
  6. Delete the translation files.

Note: If a contributions crosses many projects, such as those from the JapanWG, simply delete the following line in the SQL statements (there are currently two occurrences of this line) :

   AND F.project_id = '" . $PROJECT_ID . "' AND F.version = '" . $VERSION . "'