[tor-commits] [bridgedb/develop] Update instructions on requesting translations.

[phw@xxxxxxxxxxxxxx]

commit ad2178a8ae2b6a2d8e7bb9fa229aa6b49fab3cd7
Author: Philipp Winter <phw@xxxxxxxxx>
Date:   Thu Oct 17 14:09:16 2019 -0700

    Update instructions on requesting translations.
    
    As far as I understand the process, it's not necessary to run
    'update_catalog' when requesting new translations.  We're requesting new
    translations by *only* updating bridgedb/i18n/templates/bridgedb.pot
    because it's the only file that Transifex pays attention to.
    
    Once our translators did their job, we're pulling the updated,
    language-specific .po files using the script
    maint/get-completed-translations.
---
 README.rst | 37 +++++++++++++++----------------------
 1 file changed, 15 insertions(+), 22 deletions(-)

diff --git a/README.rst b/README.rst
index 4f05ea5..2576fa7 100644
--- a/README.rst
+++ b/README.rst
@@ -162,6 +162,10 @@ Enabling additional features
 Translations
 ------------
 
+For general information on the translation process, take a look at
+`our translation guidelines for developers
+<https://trac.torproject.org/projects/tor/wiki/doc/translation/developers>`__.
+
 **Using New Translations**:
 
 This should be done when newly completed translations are available in
@@ -180,31 +184,20 @@ This should be done whenever any of the strings requiring translation --
 ``_("the ones inside the weird underscore function, like this")`` -- are
 changed, or new ones are added. See ``lib/bridgedb/strings.py``.
 
-Translations for Tor Project repos are kept `in a separate
-repo <https://gitweb.torproject.org/translation.git>`__. You'll need to
-extract the strings from BridgeDB's source code into .pot templates, and
-place these .po files into the ``translation`` repo in the ``bridgedb``
-branch. After than the .po files should be put into Transifex (don't ask
-me how this worksâ?¦) and translated. After the translations are complete,
-the finished .po files should be placed into the ``bridgedb_completed``
-branch.
-
--  To extract all strings from BridgeDB's source::
+Translations for Tor Project repos are kept `in a separate repo
+<https://gitweb.torproject.org/translation.git>`__. To request new or updated
+translations, you'll need to extract the strings from BridgeDB's source code
+into our ./i18n/templates/bridgedb.pot template, and then commit it to our
+``develop`` branch.  From there, the translation system takes over and
+eventually, new translations will be available.  To extract all strings from
+BridgeDB's source, run::
 
          python setup.py extract_messages
 
-   A .pot file will be created in ./i18n/templates/bridgedb.pot
-
-
--  Initialise catalogs for each desired language::
-
-         python setup.py init_catalog -l LANG
-
-   where ``LANG`` is the 2 or 4 letter country-code, eg. 'es'. If you've
-   already initialised a particular language, do instead::
-
-         python setup.py update_catalog
-
+Transifex uses the resulting file ./i18n/templates/bridgedb.pot (and this file
+only) as input and fetches it from BridgeDB's ``develop`` branch, so we don't
+need to release a new BridgeDB version (which we only do in the ``master``
+branch) to request translations.
 
 -------
 



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits