Changes between Version 4 and Version 5 of AdminLocalize

Timestamp:

Aug 20, 2017, 10:50:56 PM (7 years ago)

Author:

davea

Comment:

--

AdminLocalize

@@ +1 @@
+= Translations =
+
+Many parts of BOINC have translatable strings.
+The general translation process is
+ * build templates (.pot files) and upload to transifex
+ * volunteers translate on transifex
+ * download translations (.po files) from transifex
+ * deploy
+
+The set of parts is as follows.
+Each one has its own template.
+
+For each one these parts, we need to document:
+
+ * how the template is made (e.g. html/ops/build_po.php)
+ * who makes it, and when
+ * how it gets uploaded to transifex
+ * when and how the .po files are downloaded from transifex
+ * for files in the BOINC repo, when and where they're committed
+ * how the .po files are deployed
+ * the mechanism for using the .po files (e.g. translation.inc for PHP strings)
+
+== Project web sites (generic part) ==
+
+== Project web sites (project-specific part) ==
+
+== The BOINC web site ==
+
+== The Manager ==
+
+== The client ==
+
+== Mac installer ==
+
+= Translations and branches =
+
+For the parts involving software releases (server: project web; client: Manager, Client, Installer),
+I propose that the set of templates be based on master.
+The templates should be generated as a github commit action.
+Most commits won't change the templates.
+When one does, it should be automatically updated on transifex.
+
+When preparing to make a release branch (client or server)
+we'll notify the translators and encourage them to bring translations up to date.
+Before creating the release branch, we'll commit the latest .po files to master.
+
+This means that once the release branch is made, its translations won't change.
+This is correct, since the changes to release branches are bug fixes
+that don't involve changes to translatable strings.
+
+----------------------------------
 = Transifex =