On 2015/5/27 17:00, Daniel P. Berrange wrote:
> On Wed, May 27, 2015 at 08:45:09AM +0800, zhang bo wrote:
>> On 2015/3/6 21:20, Daniel P. Berrange wrote:
>>
>>> As of current GIT master, libvirt is fully using Zanata for po file
>>> translation
>>>
>>> After some trouble with the zanata python cli
On Wed, May 27, 2015 at 08:45:09AM +0800, zhang bo wrote:
> On 2015/3/6 21:20, Daniel P. Berrange wrote:
>
> > As of current GIT master, libvirt is fully using Zanata for po file
> > translation
> >
> > After some trouble with the zanata python client, I have now successfully
> > refreshed & push
On 2015/3/6 21:20, Daniel P. Berrange wrote:
> As of current GIT master, libvirt is fully using Zanata for po file
> translation
>
> After some trouble with the zanata python client, I have now successfully
> refreshed & pushed the current libvirt.pot file, and synchronized all
> the translation
On Fri, Mar 06, 2015 at 02:35:12PM +0100, Ján Tomko wrote:
> On Fri, Mar 06, 2015 at 01:20:53PM +, Daniel P. Berrange wrote:
> > As of current GIT master, libvirt is fully using Zanata for po file
> > translation
> >
> > After some trouble with the zanata python client, I have now successfully
On Fri, Mar 06, 2015 at 01:20:53PM +, Daniel P. Berrange wrote:
> As of current GIT master, libvirt is fully using Zanata for po file
> translation
>
> After some trouble with the zanata python client, I have now successfully
> refreshed & pushed the current libvirt.pot file, and synchronized
As of current GIT master, libvirt is fully using Zanata for po file
translation
After some trouble with the zanata python client, I have now successfully
refreshed & pushed the current libvirt.pot file, and synchronized all
the translation po files back down to GIT master.
For ongoing refreshes o
