Hi Doug, Thanks for continuing the effort. I have two questions. First, why do we need to use a branch again. We already set up the translation platform and IBM team can translate on Zanata directly as we discussed in Liberty cycle. There is no reason to use a branch and push translation bursty again. Second, is existing community translation guideline per language team honored in the contributed translations? When talking about Japanese, we saw a lot of different translation guidelines on wording in the last IBM translation contributed in Liberty. As a reviewer, we don't want to comment the same thing again. After we Japanese review team reviewed Liberty contribution from IBM, we don't receive any feedback/response/discussion from IBM team, so I am afraid we need to do the similar again. It need to be avoided. Otherwise reviewers will lose their energy. Could you comment on the situation? Thanks, Akihiro 2016-01-12 12:54 GMT+09:00 Douglas Fish <drfish@us.ibm.com>:

We have translations to contribute for languages de es fr it ja ko_KR pt_BR ru zh_CN zh_TW for ceilometer, cinder, glance, keystone, neutron, and nova

These are additional translations performed by the same teams that translated our previous contributions. They have been reviewed and tested. I estimate up to 35K messages will be contributed across the 10 languages and 6 components.

Following the process outlined here http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001388.ht... I am requesting that a branch be created in Zanata to facilitate review of these translations by the language coordinators.

Thanks

Doug

_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n