Hello Suhartono, Yep it is so important for translators not to translate the same document with different versions again. Zanata supports "Merge Translations" functionality (see: http://docs.zanata.org/en/release/user-guide/versions/merge-translations/ ) , and I can run this functionality when needed. I cannot find language specific translation merge, but it seems that it is a good time to merge translations from stable-newton to master in openstack-manuals, since I18n team focused Document translation for Newton by last December. Now you surely see Indonesian networking-guide for master version has more translated strings :) Note that since merging translations for document projects has not discussed a lot, (On the other hand, Horizon translation merges are relatively well defined : http://docs.openstack.org/developer/i18n/release_management.html ) I would like to discuss later the good timing for document translation merge via IRC meeting, PTG, or future Forum. I am worried that translation merge actions for all languages in some specific period may cause undesired results. With many thanks, /Ian Cloud Suhartono wrote on 1/27/2017 11:48 AM:
One networking-guide document is in the stable-newton directory. Our team have translated it into Bahasa Indonesia reaching 100%.
Now,our team are going to proceed the similar document but in the master directory, while this document having reached up 6% translated. How to made it done effectively and efficiently ?
Thank you for your guides, /Suhartono & Indonesian Team.
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n