Changes between Version 6 and Version 7 of TranslationSystem

Timestamp:

May 29, 2015, 1:08:53 PM (9 years ago)

Author:

romw

Comment:

--

TranslationSystem

@@ -4 +4 @@
 
  * Generate "templates" (.pot files) containing translatable strings from the BOINC source code.
- * Import these templates into Pootle.
- * Volunteers translate the strings in Pootle.
- * Export the translations (*.po files) from Pootle to the BOINC Git repo
+ * Commit updated template(s).
+ * Volunteers translate the strings on Transifex.
+ * Updated translations are automatically committed to the BOINC Git repo on GitHub.
  * Deploy the new translations.
 
@@ -24 +24 @@
 == Software releases ==
 
-Translation activity takes place in trunk.
+Translation activity takes place in master.
 When a release branch (client or server) is created,
 its translations are the contents of '''locale/''' at that point.
@@ -36 +36 @@
 all existing translations will be lost.
 Therefore manual validation is used.
+
 The process is as follows:
 
- * Once a day, a script '''build_pos''' is run as a cron job.
-    This script generates a template for each component,
-    leaving the .pot file in the component directory.
-    It then compares the .pot file with the one in '''locale/templates'''.
-    If they differ (not counting comments) it sends an email to Rom and David.
- * On receiving this email, Rom and/or David examines the new template file.
+ * Templates are updated as needed, Rom and/or David generate a new template file.
     If it's valid, they move it to '''locale/templates''' and commit it.
 
 == Translation ==
 
-Twice daily a cron job (~boincam/pootle/update.sh) pulls modified templates from 
-the BOINC repo and adds them to the Pootle database.
-
-Various [http://docs.translatehouse.org/projects/pootle/en/stable-2.5.0/server/commands.html Pootle Commands].
-
-update.sh should perform the following functions for each supported pootle project (boinctrunk, setiweb):
-1. Commit to VCS all existing changes to PO files. (pootle command: commit_to_vcs)
-2. Update from VCS all templates for each project. (pootle command: update_from_vcs)
-3. Apply template changes to all projects/languages. (pootle command: update_against_templates)
-4. Compile all catalogs used by the client software into MO files. (Execute: boinc/locale/updatetrans.sh)
-5. Commit to VCS all existing changes to MO files. (git command: commit)
-
-All pootle operations are limited to just the boinc/locale directory structure.  Projects are expected to
-have a similar structure.
-
-'boinc/locale/updatetrans.sh' compiles BOINC-Manager.po, BOINC-Client.po, BOINC-Web.po, and BOINC-Setup.po if
-the datestamps on the po and mo file are different.  After completing the compilation process it touches both
-files.
-
-== Post Translation Updates ==
-
-Converting the Android PO file back into the native Android localization system XML files involves executing:
-{{{
-a2po export -v
-}}}
+Translation is handled via the Transifex web portal.  Using the TransifexGithub bridge software,
+templates and completed translations are kept in sync between Transifex and Github.
 
 == Deployment ==