Changes between Version 67 and Version 68 of ReleaseProcess

Timestamp:

Feb 2, 2014, 2:20:33 AM (10 years ago)

Author:

MarkDoliner

Comment:

Update translation process.

ReleaseProcess

@@ -20 +20 @@
 '''Steps'''
  1. Upload [query:?status=new&type=translation&order=priority pending translation updates] from our Trac to [https://www.transifex.com/projects/p/pidgin/resources/ Transifex].
- 2. Find translations that have been committed directly since the last release and upload these to [https://www.transifex.com/projects/p/pidgin/resources/ Transifex].
+ 1. Find translations that have been committed directly since the last release and upload these to [https://www.transifex.com/projects/p/pidgin/resources/ Transifex].
 {{{
 hg log -b BRANCH_NAME po/
 }}}
- 3. Fetch and commit all translations from Transifex.
-{{{
-TODO
-}}}
+ 1. Fetch and commit all translations from Transifex.
+  a. {{{tx pull --force}}} - Pulls all translations from Transifex, even if local timestamp is newer than remote.
+  a. {{{cd po}}}
+  a. {{{make pidgin.pot}}}
+  a. {{{XGETTEXT_ARGS=--no-location intltool-update --report}}} - Merges current strings into translations and strips filename and line numbers to keep diffs smaller.
 
-TODO: Need to strip location info or does Transifex do this for us? `XGETTEXT_ARGS=--no-location intltool-update LL`[[br]]
-TODO: Need to check for mismatched c-format specifiers or does Transifex do this for us? `msgfmt -cv NN`
+TODO: Need to check for mismatched c-format specifiers or does Transifex do this for us? `msgfmt -cv NN` or `find -name \*.po -exec msgfmt -cv {} \;`
 
 == Other Pre-Release Steps ==