Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 68 and Version 69 of ReleaseProcess


Ignore:
Timestamp:
Feb 2, 2014, 5:28:57 AM (10 years ago)
Author:
MarkDoliner
Comment:

Minor improvements to translation steps.

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcess

    v68 v69  
    1919
    2020'''Steps'''
    21  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].
    22  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].
     21 1. Upload [query:?status=new&type=translation&order=priority pending translation updates] from our Trac to Transifex.
     22 1. Find translations that have been committed directly since the last release and upload these to Transifex.
    2323{{{
    2424hg log -b BRANCH_NAME po/
    2525}}}
    2626 1. Fetch and commit all translations from Transifex.
    27   a. {{{tx pull --force}}} - Pulls all translations from Transifex, even if local timestamp is newer than remote.
    2827  a. {{{cd po}}}
    2928  a. {{{make pidgin.pot}}}
     29  a. {{{tx pull --force}}} - Pulls all translations from Transifex, even if local timestamp is newer than remote.
    3030  a. {{{XGETTEXT_ARGS=--no-location intltool-update --report}}} - Merges current strings into translations and strips filename and line numbers to keep diffs smaller.
     31
    3132
    3233TODO: 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 {} \;`
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!