Re: [Openstack] Proposal for manuals translation process

2012-05-07 Thread Ying Chun Guo
; To > > openstack@lists.launchpad.net, > > cc > > Subject > > Re: [Openstack] Proposal for manuals translation process > > Ying Chun Guo wrote: > > Thank you for your comments. I'm glad to know that you are working for a > > larger "goal". I don&

Re: [Openstack] Proposal for manuals translation process

2012-05-03 Thread Thierry Carrez
Ying Chun Guo wrote: > I agree that we should define our objectives with respect to translations. > And we should also define the criteria of the translation web tool. > There are three > tools mentioned in the community now: Launchpad, Transifex and Pootle. > They have their own characteristics. T

Re: [Openstack] Proposal for manuals translation process

2012-05-03 Thread Ying Chun Guo
rez > Sent by: openstack-bounces+guoyingc=cn.ibm@lists.launchpad.net > > 05/02/2012 11:55 PM > > To > > openstack@lists.launchpad.net, > > cc > > Subject > > Re: [Openstack] Proposal for manuals translation process > > Ying Chun Guo wrote: > > Than

Re: [Openstack] Proposal for manuals translation process

2012-05-02 Thread Thierry Carrez
Ying Chun Guo wrote: > Thank you for your comments. I'm glad to know that you are working for a > larger "goal". I don't know > Launchpad is broken with code strings now. What do you mean when you > said "Launchpad to be > broken with code strings now "? Actually it's our tooling around that (and

Re: [Openstack] Proposal for manuals translation process

2012-04-28 Thread Ying Chun Guo
m > > 04/28/2012 03:21 AM > > To > > Ying Chun Guo/China/IBM@IBMCN, > > cc > > openstack@lists.launchpad.net > > Subject > > Re: [Openstack] Proposal for manuals translation process > > Hi Daisy, > > Thanks so much for this detailed proposal.

Re: [Openstack] Proposal for manuals translation process

2012-04-27 Thread Anne Gentle
Hi Daisy, Thanks so much for this detailed proposal. I'd like you to put it on the OpenStack wiki, at http://wiki.openstack.org/Translations. My first read-through and discussion with the CI team brings up a few comments: - Whatever we do for docs, we should also do for code strings. So unfortuna