Context Navigation

Changes between Version 27 and Version 28 of TracL10N/Transifex

Timestamp:: Aug 1, 2016, 7:31:43 PM (8 years ago)
Author:: figaro
Comment:: Further cosmetic changes

Legend:

: Unmodified
: Added
: Removed
: Modified

TracL10N/Transifex

-              v27
+              v28
+[[PageOutline(2-5,Contents,pullout)]]
 = Transifex and Trac
 [https://www.transifex.com/ Transifex] is a modern, open-source localization platform. It is a web system which automates the translation workflow for complex international projects. It is the alternative to the more laborious [[TracL10N]] process, involving svn, Babel, make, etc.
+Trac is available in a number of languages and the translations for the captions are performed in [https://www.transifex.com/ Transifex], which is a modern, open-source localization platform. It is a web system which automates the translation workflow for complex international projects. It is the alternative to the more laborious [[TracL10N]] process, involving svn, Babel, make, etc.
 {{{#!box info
 …
 If you just want to contribute translations by using Transifex, you can read the [#Translationteammember section for team members below] and then head directly on the [transifex: Transifex project].
 }}}
-[[PageOutline]]
 The key is to keep all sources in sync, if there is more than one:
 …
 == Roles
 Once you're familiar with Transifex (and they have some very good [http://help.transifex.com/ documentation] on their site), you can apply for membership to one translation team for a language, or create a new team if your language of choice isn't yet represented there. Be aware that a new translation for Trac represents a //lot// of work.
+Once you're familiar with Transifex (and they have some very good [http://help.transifex.com/ documentation] on their site), you can apply for membership to one translation team for a language, or create a new team if your language of choice isn't yet represented there. Be aware that a new translation for Trac usually involves a //lot// of work.
 === Translation team coordinator
 …
 |-----------------------------------------------------------------------------
  - for the languages in [#group1], the translation maintainers are primarily in charge for doing the synchronization
  - for [#group2], there is only "normal" maintenance to do
  - for [#group3], the translation team coordinators are invited to ask for commit privileges and integrate [#group1]
+ - for the languages in [#group1] the translation maintainers are primarily in charge for doing the synchronization
+ - for [#group2] there is only the usual maintenance to do
+ - for [#group3] the translation team coordinators are invited to ask for commit privileges and integrate [#group1]
  - for [#group4] the translations will be "promoted" to [#group3], ie integrated in the repository, as soon as a decent coverage is reached (say > 50%)
 {{{#!comment
  - for the languages in [#group5]
 }}}
  - for the languages in [#group6], there's nothing to do as long as there's no content
+ - for the languages in [#group6] there's nothing to do as long as there's no content
 === Translation team member
 …
 You first need to install the [http://help.transifex.com/features/client/index.html#user-client Transifex client]:
 {{{
 easy_install transifex-client
+{{{#!sh
+$ easy_install transifex-client
 }}}
 or a [http://help.transifex.com/features/client/index.html#getting-the-client variation of the above].
 …
 If you're on Windows, you'll also need a [https://github.com/cboos/transifex-client/tree/0.8/tx-config-posix-paths-on-windows hack].
+Of course, you also need to have a [TracRepositories checkout of the source] of the branch you want to work on. [source:branches//0.12-stable] will be maintained for the foreseeable future, so you may want to continue contributing there, but [source:branches//1.0-stable] is now the official stable release branch. [source:trunk] is where the new interesting stuff happen (TracDev/Proposals/ConfigEnumTranslation?).
+Of course, you also need to have a [TracRepositories checkout of the source] of the branch you want to work on:
+ * [source:branches//0.12-stable] will be maintained for the foreseeable future, so you may want to continue contributing there
+ * [source:branches//1.0-stable] is now the official stable release branch
+ * [source:trunk] is where the new interesting stuff happen (TracDev/Proposals/ConfigEnumTranslation?).
 Now let's go through a complete example, starting from one update to the resource corresponding to the messages catalog on 0.12 for the [Transifex:language/fr/ French translation], more specifically, on that page: Transifex:resource/0_12-stable-messages-pot/l/fr/.
 …
 }}}
 A very important preparation task that must be done before pulling is to make sure the `.po` file was updated. Even if you think it must be because there are no local changes, it's a good idea to `make update-..` (`fr` in this example). Perhaps the Babel version you're using at the moment is different from the one which was used before the last version was committed, or a manual change was done at the last minute.
 Doing a catalog update ensures that we have a "normalized" content to compare with  the version of the catalog pulled from Transifex, after the latter has been "normalized" as well by another Babel update, as the automatic formatting done by Transifex is completely different.
+An important preparation task that must be done before pulling is to make sure the `.po` file was updated. Even if you think it must be because there are no local changes, it's a good idea to `make update-..` (`fr` in this example). Perhaps the Babel version you're using at the moment is different from the one which was used before the last version was committed, or a manual change was done at the last minute.
+Doing a catalog update ensures that we have a "normalized" content to compare with the version of the catalog pulled from Transifex, after the latter has been "normalized" as well by another Babel update, as the automatic formatting done by Transifex is completely different.
 Make sure to "freeze" that updated Trac version, by making a commit in a local branch (if you use git or hg) or even a "maintenance" commit in Subversion.
 …
 For some languages, push can fail like this:
 {{{
+{{{#!sh
 $ tx push -t -l gl
 Pushing translations for resource trac.0_12-stable-messages-js-pot:
 …
 The workaround is to push explicitly this one, by using the `-r` option:
 {{{
+{{{#!sh
 $ tx push -t -r trac.0_12-stable-messages-pot -l gl
 Pushing translations for resource trac.0_12-stable-messages-pot:
 …
 That can be done for several languages at once:
 {{{
+{{{#!sh
 $ tx push -t -r trac.0_12-stable-messages-pot -l fa,gl,ko,pt,ro,vi
 Pushing translations for resource trac.0_12-stable-messages-pot:
 …
 == Notes about the Transifex "Releases"  #Releases
 Transifex is not exactly clear if a release should be a line of development (branch) or a given released version. It supports both and let you choose to organize the way you wish.
 I opted to make the "releases" match our maintenance branches, and not individual releases; well, we still have a [Transifex:r/012-stable-3/ few of these], as apparently you can't delete a release.
+In Transifex is not exactly clear if a release should be a line of development (branch) or a given released version. It supports both and lets you choose to organize the way you wish.
+I opted to make the "releases" match our maintenance branches, and not individual releases; we still have a [Transifex:r/012-stable-3/ few of these], as apparently you can't delete a release.
 The downside is that string freeze periods and release dates will need to be adjusted constantly on the same release. The alternative, creating a new "release" for each actual version we release bears as much overhead (moreover, are there's no //copy// operation) and doesn't bring any benefit besides keeping a record of the versions we made, record that we obviously maintain here anyway in the [/roadmap].
 On the other hand, the big benefit is that all the links from t.e.o to Tx won't need to be updated after each minor release. The only updates needed will be when introducing a new major release (i.e. for 1.2).
+On the other hand, the big benefit is that all the links from t.e.o to Tx won't need to be updated after each minor release. The only updates needed will be when introducing a new major release, for example for Trac 1.2.