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
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
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.
Carlos A. Munoz
Software Engineering Supervisor
Engineering - Internationalization
On 08/20/2014 09:10 PM, Noriko Mizumoto wrote:
I added Carlos to get help.
(2014年08月19日 22:26), David Woodhouse wrote:
> Hi Noriko-san,
> Thank you for your helpful response.
> On Tue, 2014-08-19 at 13:45 +1000, Noriko Mizumoto wrote:
>> Now we are currently planning to move from Transifex to Zanata
>> (fedora.zanata). 'fedora.zanata' instance will be newly created to
>> accept translation for F22 onwards, but not set up yet. I am going to
>> attend FESCO meeting sometime to discuss and find best timing to move
>> for all maintainers. Then all necessary information will be sent out to
>> each maintainer. I like to add your package in my list for this purpose,
>> can you tell me the module name?
> There are two projects which need translation, although neither of them
> are actually mine. One is gss-ntlmssp, which is Simo's project:
> The other is krb5, which has NLS support upstream, but actual
> *translations* are left for OS distributors to provide:
Okay, I added two of them in the list of 'Upstream' group .
If those packages rather should belong to 'Main' group (which means
Fedora package following Fedora development schedule), please advise.
>> Also if you like to receive translation for F21, your module can be
>> added to 'translate.zanata.org' instance just for F21, where various
>> open source projects including non-Fedora are registered. Please read
>> the section 'Maintainers' on the workflow-overview page . For F22,
>> your module is required to move to 'fedora.zanata' instance.
> It might be worthwhile to set up gss-ntlmssp for F21, and that way I can
> work on the integration — ensuring that translatable strings get into
> Zanata automatically, and providing a makefile target to pull the latest
> translations down from Zanata and commit them to the repository.
> I'd already offered Simo a 'make update-translations' target which
> pulled from Transifex¹, so I'll update that for Zanata. Unless you
> already have one?
> For the *source* documents, is Zanata able to automatically download
> from a URL or does it have to be manually pushed?
> Also, is an API key required for zanata-cli to pull translations, or can
> that be done anonymously?
Carlos, could you kindly help and answer the above questions?