translation process after autotools - needs update #2992

See: https://github.com/bitcoin/bitcoin/blob/master/doc/translation_process.md

We generated the bitcoin_en.ts via:

<pre> python share/qt/extract_strings_qt.py lupdate bitcoin-qt.pro -no-obsolete -locations relative -ts src/qt/locale/bitcoin_en.ts </pre>

AFAIK this no longer works, as we don't have any working .pro file. We need a working translations process and as I'm no Python script guy, nor have any autotools knowledge, someone needs to look into this :). @laanwj @theuni Can you please take a look?

will have a look.

That's going to be interesting, I wonder if lupdate has other ways of locating the source files.

You can just pass a list of source files, apparently.

On Sat, Sep 14, 2013 at 1:38 PM, Wladimir J. van der Laan < notifications@github.com> wrote:

That's going to be interesting, I wonder if lupdate has other ways of locating the source files.

— Reply to this email directly or view it on GitHubhttps://github.com/bitcoin/bitcoin/issues/2992#issuecomment-24443504 .

So what we need is a "make translation" or something that runs the above commands, and automatically provides all the source files (including .ui forms IIRC) to it. Can this be done using autoconf/automake or do we need an additional script?

As I didn't yet switch to autotools, I can create a current translations update and will maintain the .pro file localy until Qt5 support is included and it's mature enough for me to switch to autotools.

I have this changed locally (almost word-for-word what @laanwj said, coincidentally). Will push it up in a few min.

See #2996

So can anyone with autotools generate a current english master file and create a pull for it :)? I would love to see it's working.

@diapolo https://github.com/bitcoin/bitcoin/commit/9a4a7d3c6a6413b952dde12c899cf74a3fab8452