[Openstack-i18n] [OpenStack-Infra] Pootle and Zanata trial

Andreas Jaeger aj at suse.com
Fri Oct 24 08:11:51 UTC 2014


On 10/24/2014 01:43 AM, Carlos Munoz wrote:
> My personal recommendation is to use the Java client, at least to begin with. I know it isn't as easy to install as a pure python client, but it does offer far more functionality and flexibility. Installation is a one-time thing, and once it's up and running there's no need to change it. The main maintainer for the python client is another Red Hatter outside of our core team; I can put you in contact with him as well so he can answer some questions and maybe start adapting some of the newer features to the python client.

With our CI infrastructure, where we have virtual machines that we start
up for each job, we either would need to add the client to our own
images and integrate them so that whenever we generate a new image, it
keeps included - or install it whenever we start.


> In terms of workflow (and I must admit I'm not all that familiar with yours), most projects simply keep their zanata.xml in the source repos and update manually, but in most cases adding or removing languages is very infrequent. I have created a bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1156236) so we can get the conversation started on auto-updating those language codes.

thanks!

Andreas

> Regards,
> 
> Carlos
> 
> Carlos A. Munoz
> Software Engineering Supervisor
> Engineering - Internationalization
> Red Hat
> 
> ----- Original Message -----
> From: "Andreas Jaeger" <aj at suse.com>
> To: camunoz at redhat.com
> Cc: openstack-i18n at lists.openstack.org, openstack-infra at lists.openstack.org
> Sent: Thursday, October 23, 2014 9:58:23 PM
> Subject: Re: [Openstack-i18n] [OpenStack-Infra]  Pootle and Zanata trial
> 
> On 10/23/2014 03:01 AM, Carlos Munoz wrote:
>> Hi Andreas,
>>
>> The reason why the python client doesn't find your PO files is because
>> it is expecting them to be in a strictly standard place for po files.
>> Because you have that LC_MESSAGES directory, that throws the python
>> client off base. This is one of the things we have improved in our java
>> client. So I'm going to guide you through the same exact steps you are
>> trying here, but with the java client.
> 
> Thanks!
> 
> So, the question is whether this gets fixed in the python client - or
> whether we should use the java client...
> 
>> [...]
> 
>> Now, to answer your specific questions at the end:
>>
>> * (ad 7): How can I upload the translation files via command line for an
>> initial import?
>>
>> I think I covered that in my series of steps above, as it was really an
>> initial push from the source repo. Let me know if you still have
>> questions there.
> 
> No, looks fine.
> 
>> * (ad 5) What happens if more languages get added on the server, how to
>> update the local zanata.xml file? Or is there a way to download it
>> automatically using the client?
>>
>> That is currently a manual process because the server doesn't contain
>> all the information that you might have customized (like I did in my
>> example) in your zanata.xml. Having said that, it should not be very
>> difficult to implement a client feature that lets you update the
>> languages from the project in Zanata.
> 
> Yes, with our workflow this is needed.
> 
> Do you have a proposal for a better workflow than the one we're using?
> What are others doing?
> 
>>
>> I hope I've shed some light on the zanata client workings. As usual, let
>> me know if you have any other questions.
> 


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126



More information about the Openstack-i18n mailing list