[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Maposmatic-dev] How to develop with translations on Transifex?

From: Hakan Tandogan
Subject: Re: [Maposmatic-dev] How to develop with translations on Transifex?
Date: Sun, 21 Apr 2013 20:17:59 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5

Hi Maxime,

you are right, this is something I should (and will) describe better in the wiki and the README files in the source.

Basically, all you need to do is to push your change to the source files, which you did with the change [1], and wait for magic to happen :-)

The script "scripts/" will then extract the new .pot file, push that change to the git repository and transifex. If you really want, you can run this script yourself from the "scripts" directory, but you can also simply wait for my Jenkins instance to pick up the git change and run that script itself.

As you might have recognized, at 20:03 today this did happen, Jenkins noticed your push and ran the script, thereby updating git [2] and Transifex [3]

We can already see on transifex that you have added translations for Dutch, German and French. Those changes will be picked up again by the script "scripts/" and the .po files will be accordingly adapted and pushed back to git. Expect this change to happen about 21:00 MET (as of the writing of this mail, this should happen in about 45 minutes).

I will put all of this information into the wiki as soon as find a few free minutes to write proper documentation.





On 21.04.2013 19:49, Maxime Petazzoni wrote:
Hi all,

Now that our translations are managed by Transifex (great tool by the
way, they fixed the bug I was hitting last time I tried it), I'm curious
as to what the process exactly looks like.

I just made a change that will make a new string translatable. What
should I do now? If I run makemessages it will regenerate all
the .po files. Should I do that? How do I then upload that to Transifex?

I see the wiki has been updated with how to *translate*, but for us
developers I'm still unclear. Can someone drive me through the process?

So far I've only pushed the change that makes this new string, but
nothing that touches translation files.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]