Fwd: Are we still translating things?

[Carlos Munoz]

Hi David,

We have used a little Groovy script of our own making that all it does 
is invoke commands from one of our clients. You can have a look here 
https://github.com/zanata/repo-sync

Let me know if you have any questions about it, but it looks like you 
have something very similar in your makefiles.

About your last question, there is actually an open bug about it: 
https://bugzilla.redhat.com/show_bug.cgi?id=1010132
Per this issue, there is a workaround that requires you to edit 
zanata.xml
Feel free to comment on the bug to raise its importance :)

Regards,

Carlos A. Munoz
Software Engineering Supervisor
Engineering - Internationalization
Red Hat

On Thu 21 Aug 2014 02:01:21 PM EST, David Woodhouse wrote:
> On Thu, 2014-08-21 at 09:58 +1000, Carlos Munoz wrote:
>> Hi All,
>>
>> Zanata is not currently able to "pull" source files from an external
>> url. What we do and have helped other projects do is to set up an
>> automated process (Jenkins works well here) to constantly push and pull
>> source and translations files, and even make a commit to a git repo for
>> updated translations. We can help out with this kind of setup if it's
>> needed.
>
> If you have examples of this, that could be useful; thanks. Otherwise I
> can happily do some Makefile fragments equivalent to the ones I have for
> Transifex to do 'make update-translations' and 'make upload-pot':
> http://git.infradead.org/users/dwmw2/openconnect.git/blob/3e7c5f83:/Makefile.am#l175
>
> The former attempts to eliminate zero-value updates, as you can see.
> It's not perfect but it does a reasonable job of avoiding churn.
>
>> As for the API key being required to pull files, this is a requirement
>> we recently introduced to try and have a fairer use of the server
>> resources (i.e. someone hogging all the connections to the server). We
>> can reevaluate this requirement if there's a strong need for it, and we
>> are starting to look at scaling opportunities which might also make it
>> unnecessary.
>
> OK. I think since the maintainers are the only people who are usually
> expected to be pulling translations, it's not really the end of the
> world to expect them to have an API key installed.
>
>> I think those were the two questions mentioned in the email. Let me know
>> if I've missed any of them or if you have any others.
>
> One more... I run 'zanata-cli pull -t po --create-skeletons' and now I
> have a bunch of *.po files in my po/ directory. Including an 'en-GB.po'
> file. What is this 'en-GB'? I only have /usr/share/local/en_GB with an
> underscore...
>