Re: [Openstack-i18n] IBM translations to contribute: update
From: Douglas Fish/Rochester/IBM@IBMUS To: guoyingc@cn.ibm.com Cc: openstack-i18n@lists.openstack.org Date: 09/18/2015 05:14 AM Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi Daisy,
We have translations to contribute for ceilometer, cinder, glance, heat, ironic, keystone, nova and swift for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW
We are working to upload those to the Zanata test server to make sure there are no technical issues.
Doug
----- Original message ----- From: Ying Chun Guo <guoyingc@cn.ibm.com> To: Douglas Fish/Rochester/IBM@IBMUS Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] IBM translations to contribute: update Date: Thu, Sep 17, 2015 11:04 AM
Hi Doug, Hi team,
In today's IRC meeting, we talked about the process to get IBM
Hi, team I have made enough tests on the test server with the help from Doug and his colleagues. In the test server, I created versions for nova, glance, cinder, swift, ceilometer, heat, keystone, and ironic. Doug and his colleagues uploaded their po files for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I tested merging two versions. Things are running well. The test server is still in good condition. So there is no technical issues block me to do the same in the production server. I even tried "Group" in the test server. The "Group" feature looks wonderful. So if there is no objections, I will go to production server, doing the same as what I did in the test server. Best regards Ying Chun Guo (Daisy) Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM: translations.
I'm going to normalize the process to contribute translations by uploading po files.
Here are some key points during the meeting:
1. It is strongly discouraged to use the offline editor other than web tool. Because the offline editor could not take the advantages of translation memory and glossary, which might affect the translation quality. 2. Simply uploading po files are not allowed because it has a risk that the po files might contain bad translations. 3. In some special cases, if people who want to contribute translations by uploading po files, following below steps 3.1 Send email to I18n mailing list, describing the source documents and languages he/she is going to upload. 3.2 Zanata admin will create a branch. Then contributors could upload po files to the proposed branch. 3.3 When the uploading is done, language coordinators could review the translations. The coordinators could have two kinds of review results: agree to merge or deny to merge. If the coordinators deny to merge, coordinators should give some comments, either to delete this branch, or to suggestions to improve. 3.4 If the coordinators agree to merge to the master branch, Zanata admin will make the merge. A option could set during the branches merging to make sure not overwrite translated/approved translations in the source branch. After merging, the proposed branch will be deleted.
I have been testing branches in the Zanata test server for several days. When I make sure it works fine, I will go to the production server.
@Doug, please let us know which resources and which languages you are going to propose ?
Best regards Ying Chun Guo (Daisy)
"Douglas Fish" <drfish@us.ibm.com> wrote on 09/16/2015 08:05:52 PM:
From: "Douglas Fish" <drfish@us.ibm.com> To: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Date: 09/16/2015 08:06 PM Subject: [Openstack-i18n] IBM translations to contribute: update
Here's the revised approach we are taking to contributing our IBM translations to the community, based on feedback on suggestions:
We are planning to make the proposed translations available for a pre-review as a separate branch in Zanata, but they are not there yet. While testing out this upload on the development server we discovered that uploading PO files caused the server to become unresponsive for a while. Thanks to pleia2 and the infra team for sorting that out and addressing the issue. We'll try the upload on dev again tomorrow and if it goes well we will make the translations available for pre-review in a separate Zanata branch.
I had originally proposed ending the pre-review on Monday. Obviously that's not going to happen! I understand that different language teams have differing levels of readiness to accept these contributions. I understand some groups are ready at this time, while others would like to have more time, possibly even into Mitaka to review. We aren't going to upload PO files for any language were the team does not want them.
Language coordinators, please let me know how you'd like to proceed with these contributions for your language. Do you want 1) us to upload them to Zanata's current master translations for normal review and editing as soon as we can, 2) us to upload them to Zanata as a separate branch for further pre-review, or 3) hold off any submission or preview at this time.
Please note that it important to us that we upload these translations. The translations are a valued IBM asset, it's important to us that they are recognized as contributed by IBM.
I'll be at the Thursday i18n team meeting, and am available by IRC (doug-fish) or email if you have questions or further concerns.
Thanks!
Doug_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Daisy, Good to hear that you got good results so far. Daisy, Doug and his colleagues, thanks for your hard work. One confirmation. Is the translation memory isolated until the branch is merged into the master branch? I don't see any concern except the above. Akihiro 2015-09-18 23:40 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Hi, team
I have made enough tests on the test server with the help from Doug and his colleagues.
In the test server, I created versions for nova, glance, cinder, swift, ceilometer, heat, keystone, and ironic. Doug and his colleagues uploaded their po files for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I tested merging two versions. Things are running well. The test server is still in good condition. So there is no technical issues block me to do the same in the production server. I even tried "Group" in the test server. The "Group" feature looks wonderful.
So if there is no objections, I will go to production server, doing the same as what I did in the test server.
Best regards Ying Chun Guo (Daisy)
Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM:
From: Douglas Fish/Rochester/IBM@IBMUS To: guoyingc@cn.ibm.com Cc: openstack-i18n@lists.openstack.org Date: 09/18/2015 05:14 AM Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi Daisy,
We have translations to contribute for ceilometer, cinder, glance, heat, ironic, keystone, nova and swift for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW
We are working to upload those to the Zanata test server to make sure there are no technical issues.
Doug
----- Original message ----- From: Ying Chun Guo <guoyingc@cn.ibm.com> To: Douglas Fish/Rochester/IBM@IBMUS Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] IBM translations to contribute: update Date: Thu, Sep 17, 2015 11:04 AM
Hi Doug, Hi team,
In today's IRC meeting, we talked about the process to get IBM translations. I'm going to normalize the process to contribute translations by uploading po files.
Here are some key points during the meeting:
1. It is strongly discouraged to use the offline editor other than web tool. Because the offline editor could not take the advantages of translation memory and glossary, which might affect the translation quality. 2. Simply uploading po files are not allowed because it has a risk that the po files might contain bad translations. 3. In some special cases, if people who want to contribute translations by uploading po files, following below steps 3.1 Send email to I18n mailing list, describing the source documents and languages he/she is going to upload. 3.2 Zanata admin will create a branch. Then contributors could upload po files to the proposed branch. 3.3 When the uploading is done, language coordinators could review the translations. The coordinators could have two kinds of review results: agree to merge or deny to merge. If the coordinators deny to merge, coordinators should give some comments, either to delete this branch, or to suggestions to improve. 3.4 If the coordinators agree to merge to the master branch, Zanata admin will make the merge. A option could set during the branches merging to make sure not overwrite translated/approved translations in the source branch. After merging, the proposed branch will be deleted.
I have been testing branches in the Zanata test server for several days. When I make sure it works fine, I will go to the production server.
@Doug, please let us know which resources and which languages you are going to propose ?
Best regards Ying Chun Guo (Daisy)
"Douglas Fish" <drfish@us.ibm.com> wrote on 09/16/2015 08:05:52 PM:
From: "Douglas Fish" <drfish@us.ibm.com> To: "Openstack-i18n Openstack-i18n" < openstack-i18n@lists.openstack.org> Date: 09/16/2015 08:06 PM Subject: [Openstack-i18n] IBM translations to contribute: update
Here's the revised approach we are taking to contributing our IBM translations to the community, based on feedback on suggestions:
We are planning to make the proposed translations available for a pre-review as a separate branch in Zanata, but they are not there yet. While testing out this upload on the development server we discovered that uploading PO files caused the server to become unresponsive for a while. Thanks to pleia2 and the infra team for sorting that out and addressing the issue. We'll try the upload on dev again tomorrow and if it goes well we will make the translations available for pre-review in a separate Zanata branch.
I had originally proposed ending the pre-review on Monday. Obviously that's not going to happen! I understand that different language teams have differing levels of readiness to accept these contributions. I understand some groups are ready at this time, while others would like to have more time, possibly even into Mitaka to review. We aren't going to upload PO files for any language were the team does not want them.
Language coordinators, please let me know how you'd like to proceed with these contributions for your language. Do you want 1) us to upload them to Zanata's current master translations for normal review and editing as soon as we can, 2) us to upload them to Zanata as a separate branch for further pre-review, or 3) hold off any submission or preview at this time.
Please note that it important to us that we upload these translations. The translations are a valued IBM asset, it's important to us that they are recognized as contributed by IBM.
I'll be at the Thursday i18n team meeting, and am available by IRC (doug-fish) or email if you have questions or further concerns.
Thanks!
Doug_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 09/18/2015 11:34 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi Daisy,
Good to hear that you got good results so far. Daisy, Doug and his colleagues, thanks for your hard work.
One confirmation. Is the translation memory isolated until the branch is merged into the master branch?
I don't see any concern except the above.
Akihiro
2015-09-18 23:40 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>: Hi, team
I have made enough tests on the test server with the help from Doug and his colleagues.
In the test server, I created versions for nova, glance, cinder, swift, ceilometer, heat, keystone, and ironic. Doug and his colleagues uploaded their po files for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I tested merging two versions. Things are running well. The test server is still in good condition. So there is no technical issues block me to do the same in the production server. I even tried "Group" in the test server. The "Group" feature looks wonderful.
So if there is no objections, I will go to production server, doing the same as what I did in the test server.
Best regards Ying Chun Guo (Daisy)
Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM:
From: Douglas Fish/Rochester/IBM@IBMUS To: guoyingc@cn.ibm.com Cc: openstack-i18n@lists.openstack.org Date: 09/18/2015 05:14 AM Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi Daisy,
We have translations to contribute for ceilometer, cinder, glance, heat, ironic, keystone, nova and swift for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW
We are working to upload those to the Zanata test server to make sure there are no technical issues.
Doug
----- Original message ----- From: Ying Chun Guo <guoyingc@cn.ibm.com> To: Douglas Fish/Rochester/IBM@IBMUS Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] IBM translations to contribute: update Date: Thu, Sep 17, 2015 11:04 AM
Hi Doug, Hi team,
In today's IRC meeting, we talked about the process to get IBM
The TM is not isolated. But after I remove the branch, the translations in the branch will be removed from TM. So if you don't like these translations, you could remove the the whole branch or reject some translations, TM will be clean. Best regards Ying Chun Guo (Daisy) Akihiro Motoki <amotoki@gmail.com> wrote on 09/18/2015 11:33:43 PM: translations.
I'm going to normalize the process to contribute translations by uploading po files.
Here are some key points during the meeting:
1. It is strongly discouraged to use the offline editor other thanweb tool. Because the offline editor could not take the advantages of translation memory and glossary, which might affect the translation quality. 2. Simply uploading po files are not allowed because it has a risk that the po files might contain bad translations. 3. In some special cases, if people who want to contribute translations by uploading po files, following below steps 3.1 Send email to I18n mailing list, describing the source documents and languages he/she is going to upload. 3.2 Zanata admin will create a branch. Then contributors could upload po files to the proposed branch. 3.3 When the uploading is done, language coordinators could review the translations. The coordinators could have two kinds of review results: agree to merge or deny to merge. If the coordinators deny to merge, coordinators should give some comments, either to delete this branch, or to suggestions to improve. 3.4 If the coordinators agree to merge to the master branch, Zanata admin will make the merge. A option could set during the branches merging to make sure not overwrite translated/approved translations in the source branch. After merging, the proposed branch will be deleted.
I have been testing branches in the Zanata test server for several days. When I make sure it works fine, I will go to the production server.
@Doug, please let us know which resources and which languages you are going to propose ?
Best regards Ying Chun Guo (Daisy)
"Douglas Fish" <drfish@us.ibm.com> wrote on 09/16/2015 08:05:52 PM:
From: "Douglas Fish" <drfish@us.ibm.com> To: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Date: 09/16/2015 08:06 PM Subject: [Openstack-i18n] IBM translations to contribute: update
Here's the revised approach we are taking to contributing our IBM translations to the community, based on feedback on suggestions:
We are planning to make the proposed translations available for a pre-review as a separate branch in Zanata, but they are not there yet. While testing out this upload on the development server we discovered that uploading PO files caused the server to become unresponsive for a while. Thanks to pleia2 and the infra team for sorting that out and addressing the issue. We'll try the upload on dev again tomorrow and if it goes well we will make the translations available for pre-review in a separate Zanata branch.
I had originally proposed ending the pre-review on Monday. Obviously that's not going to happen! I understand that different language teams have differing levels of readiness to accept these contributions. I understand some groups are ready at this time, while others would like to have more time, possibly even into Mitaka to review. We aren't going to upload PO files for any language were the team does not want them.
Language coordinators, please let me know how you'd like to proceed with these contributions for your language. Do you want 1) us to upload them to Zanata's current master translations for normal review and editing as soon as we can, 2) us to upload them to Zanata as a separate branch for further pre-review, or 3) hold off any submission or preview at this time.
Please note that it important to us that we upload these translations. The translations are a valued IBM asset, it's important to us that they are recognized as contributed by IBM.
I'll be at the Thursday i18n team meeting, and am available by IRC (doug-fish) or email if you have questions or further concerns.
Thanks!
Doug_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
From: Ying Chun Guo/China/IBM@IBMCN To: openstack-i18n@lists.openstack.org Date: 2015/09/18 22:42 Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi, team
I have made enough tests on the test server with the help from Doug and his colleagues.
In the test server, I created versions for nova, glance, cinder, swift, ceilometer, heat, keystone, and ironic. Doug and his colleagues uploaded their po files for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I tested merging two versions. Things are running well. The test server is still in good condition. So there is no technical issues block me to do the same in the production server. I even tried "Group" in the test server. The "Group" feature looks wonderful.
So if there is no objections, I will go to production server, doing the same as what I did in the test server.
Best regards Ying Chun Guo (Daisy)
Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM:
From: Douglas Fish/Rochester/IBM@IBMUS To: guoyingc@cn.ibm.com Cc: openstack-i18n@lists.openstack.org Date: 09/18/2015 05:14 AM Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi Daisy,
We have translations to contribute for ceilometer, cinder, glance, heat, ironic, keystone, nova and swift for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW
We are working to upload those to the Zanata test server to make sure there are no technical issues.
Doug
----- Original message ----- From: Ying Chun Guo <guoyingc@cn.ibm.com> To: Douglas Fish/Rochester/IBM@IBMUS Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] IBM translations to contribute: update Date: Thu, Sep 17, 2015 11:04 AM
Hi Doug, Hi team,
In today's IRC meeting, we talked about the process to get IBM
Versions have been created for IBM to import their translations in the production server. These resources could be browsed through a "group" view. https://translate.openstack.org/version-group/view/ibm-translations-group @ Doug, I think you could start uploading now. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM@IBMCN wrote on 2015/09/18 22:40:39: translations.
I'm going to normalize the process to contribute translations by uploading po files.
Here are some key points during the meeting:
1. It is strongly discouraged to use the offline editor other thanweb tool. Because the offline editor could not take the advantages of translation memory and glossary, which might affect the translation quality. 2. Simply uploading po files are not allowed because it has a risk that the po files might contain bad translations. 3. In some special cases, if people who want to contribute translations by uploading po files, following below steps 3.1 Send email to I18n mailing list, describing the source documents and languages he/she is going to upload. 3.2 Zanata admin will create a branch. Then contributors could upload po files to the proposed branch. 3.3 When the uploading is done, language coordinators could review the translations. The coordinators could have two kinds of review results: agree to merge or deny to merge. If the coordinators deny to merge, coordinators should give some comments, either to delete this branch, or to suggestions to improve. 3.4 If the coordinators agree to merge to the master branch, Zanata admin will make the merge. A option could set during the branches merging to make sure not overwrite translated/approved translations in the source branch. After merging, the proposed branch will be deleted.
I have been testing branches in the Zanata test server for several days. When I make sure it works fine, I will go to the production server.
@Doug, please let us know which resources and which languages you are going to propose ?
Best regards Ying Chun Guo (Daisy)
"Douglas Fish" <drfish@us.ibm.com> wrote on 09/16/2015 08:05:52 PM:
From: "Douglas Fish" <drfish@us.ibm.com> To: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Date: 09/16/2015 08:06 PM Subject: [Openstack-i18n] IBM translations to contribute: update
Here's the revised approach we are taking to contributing our IBM translations to the community, based on feedback on suggestions:
We are planning to make the proposed translations available for a pre-review as a separate branch in Zanata, but they are not there yet. While testing out this upload on the development server we discovered that uploading PO files caused the server to become unresponsive for a while. Thanks to pleia2 and the infra team for sorting that out and addressing the issue. We'll try the upload on dev again tomorrow and if it goes well we will make the translations available for pre-review in a separate Zanata branch.
I had originally proposed ending the pre-review on Monday. Obviously that's not going to happen! I understand that different language teams have differing levels of readiness to accept these contributions. I understand some groups are ready at this time, while others would like to have more time, possibly even into Mitaka to review. We aren't going to upload PO files for any language were the team does not want them.
Language coordinators, please let me know how you'd like to proceed with these contributions for your language. Do you want 1) us to upload them to Zanata's current master translations for normal review and editing as soon as we can, 2) us to upload them to Zanata as a separate branch for further pre-review, or 3) hold off any submission or preview at this time.
Please note that it important to us that we upload these translations. The translations are a valued IBM asset, it's important to us that they are recognized as contributed by IBM.
I'll be at the Thursday i18n team meeting, and am available by IRC (doug-fish) or email if you have questions or further concerns.
Thanks!
Doug_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
From: Ying Chun Guo/China/IBM@IBMCN To: openstack-i18n@lists.openstack.org Date: 2015/09/21 17:24 Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Versions have been created for IBM to import their translations in the production server. These resources could be browsed through a "group" view. https://translate.openstack.org/version-group/view/ibm-translations-group
@ Doug, I think you could start uploading now.
Best regards Ying Chun Guo (Daisy)
Ying Chun Guo/China/IBM@IBMCN wrote on 2015/09/18 22:40:39:
From: Ying Chun Guo/China/IBM@IBMCN To: openstack-i18n@lists.openstack.org Date: 2015/09/18 22:42 Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi, team
I have made enough tests on the test server with the help from Doug and his colleagues.
In the test server, I created versions for nova, glance, cinder, swift, ceilometer, heat, keystone, and ironic. Doug and his colleagues uploaded their po files for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW. I tested merging two versions. Things are running well. The test server is still in good condition. So there is no technical issues block me to do the same in the production server. I even tried "Group" in the test server. The "Group" feature lookswonderful.
So if there is no objections, I will go to production server, doing the same as what I did in the test server.
Best regards Ying Chun Guo (Daisy)
Douglas Fish/Rochester/IBM wrote on 09/18/2015 05:14:22 AM:
From: Douglas Fish/Rochester/IBM@IBMUS To: guoyingc@cn.ibm.com Cc: openstack-i18n@lists.openstack.org Date: 09/18/2015 05:14 AM Subject: Re: [Openstack-i18n] IBM translations to contribute: update
Hi Daisy,
We have translations to contribute for ceilometer, cinder, glance, heat, ironic, keystone, nova and swift for languages de, es, fr, it, ja ko-KR, pr-BR, ru, zh-CN, and zh-TW
We are working to upload those to the Zanata test server to make sure there are no technical issues.
Doug
----- Original message ----- From: Ying Chun Guo <guoyingc@cn.ibm.com> To: Douglas Fish/Rochester/IBM@IBMUS Cc: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Subject: Re: [Openstack-i18n] IBM translations to contribute: update Date: Thu, Sep 17, 2015 11:04 AM
Hi Doug, Hi team,
In today's IRC meeting, we talked about the process to get IBM translations. I'm going to normalize the process to contribute translations by uploading po files.
Here are some key points during the meeting:
1. It is strongly discouraged to use the offline editor other thanweb tool. Because the offline editor could not take the advantages of translation memory and glossary, which might affect the translation quality. 2. Simply uploading po files are not allowed because it has a risk that the po files might contain bad translations. 3. In some special cases, if people who want to contribute translations by uploading po files, following below steps 3.1 Send email to I18n mailing list, describing the source documents and languages he/she is going to upload. 3.2 Zanata admin will create a branch. Then contributors could upload po files to the proposed branch. 3.3 When the uploading is done, language coordinators could review the translations. The coordinators could have two kinds of review results: agree to merge or deny to merge. If the coordinators deny to merge, coordinators should give some comments, either to delete this branch, or to suggestions to improve. 3.4 If the coordinators agree to merge to the master branch, Zanata admin will make the merge. A option could set during the branches merging to makesure not overwrite translated/approved translations in the source branch. After merging, the proposed branch will be deleted.
I have been testing branches in the Zanata test server for several days. When I make sure it works fine, I will go to the production server.
@Doug, please let us know which resources and which languages you are going to propose ?
Best regards Ying Chun Guo (Daisy)
"Douglas Fish" <drfish@us.ibm.com> wrote on 09/16/2015 08:05:52 PM:
From: "Douglas Fish" <drfish@us.ibm.com> To: "Openstack-i18n Openstack-i18n" <openstack-i18n@lists.openstack.org> Date: 09/16/2015 08:06 PM Subject: [Openstack-i18n] IBM translations to contribute: update
Here's the revised approach we are taking to contributing our IBM translations to the community, based on feedback on suggestions:
We are planning to make the proposed translations available for a pre-review as a separate branch in Zanata, but they are not there yet. While testing out this upload on the development server we discovered that uploading PO files caused the server to become unresponsive for a while. Thanks to pleia2 and the infra team for sorting that out and addressing the issue. We'll try the upload on dev again tomorrow and if it goes well we will make the
Hi, team Doug and his team have uploaded translations of following documents: * nova.pot in Nova * glance.pot in Glance * swift.pot in Swift * ceilometer.pot in Ceilometer, * cinder.pot in Cinder, * heat.pot in Heat, * ironic.pot in Ironic, * keystone.pot in Keystone, * neutron.pot in Neutron Please notice there is no translations for log files, and there is no overwritten of existing translations. Coordinators of Italian, French, German, Japanese, Spanish, Chinese(China), Chinese(Taiwan), Korean(South Korea),Portuguese (Brazil) and Russian: You could start the review now: https://translate.openstack.org/version-group/view/ibm-translations-group. If you have busy time, please review Nova as the high priority. I hope to merge Nova in Liberty release. Thank you for your corporation. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM@IBMCN wrote on 2015/09/21 17:21:38: translations
available for pre-review in a separate Zanata branch.
I had originally proposed ending the pre-review on Monday. Obviously that's not going to happen! I understand that different language teams have differing levels of readiness to accept these contributions. I understand some groups are ready at this time, while others would like to have more time, possibly even into Mitaka to review. We aren't going to upload PO files for any language were the team does not want them.
Language coordinators, please let me know how you'd like to proceed with these contributions for your language. Do you want 1) us to upload them to Zanata's current master translations for normal review and editing as soon as we can, 2) us to upload them to Zanata as a separate branch for further pre-review, or 3) hold off any submission or preview at this time.
Please note that it important to us that we upload these translations. The translations are a valued IBM asset, it's important to us that they are recognized as contributed by IBM.
I'll be at the Thursday i18n team meeting, and am available by IRC (doug-fish) or email if you have questions or further concerns.
Thanks!
Doug_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 2015-09-22 07:31, Ying Chun Guo wrote:
Hi, team
Doug and his team have uploaded translations of following documents: * nova.pot in Nova * glance.pot in Glance * swift.pot in Swift * ceilometer.pot in Ceilometer, * cinder.pot in Cinder, * heat.pot in Heat, * ironic.pot in Ironic, * keystone.pot in Keystone, * neutron.pot in Neutron
Please notice there is no translations for log files, and there is no overwritten of existing translations.
Coordinators of Italian, French, German, Japanese, Spanish, Chinese(China), Chinese(Taiwan), Korean(South Korea),Portuguese (Brazil) and Russian: You could start the review now: https://translate.openstack.org/version-group/view/ibm-translations-group. If you have busy time, please review Nova as the high priority. I hope to merge Nova in Liberty release.
Thank you for your corporation.
Today's import includes all the translations, see: https://review.openstack.org/#/q/status:open++branch:master+topic:zanata/tra... Thanks Doug and team for this! Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen. Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj@suse.com> wrote on 09/22/2015 03:52:04 PM:
From: Andreas Jaeger <aj@suse.com> To: Ying Chun Guo/China/IBM@IBMCN, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 09/22/2015 03:52 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
On 2015-09-22 07:31, Ying Chun Guo wrote:
Hi, team
Doug and his team have uploaded translations of following documents: * nova.pot in Nova * glance.pot in Glance * swift.pot in Swift * ceilometer.pot in Ceilometer, * cinder.pot in Cinder, * heat.pot in Heat, * ironic.pot in Ironic, * keystone.pot in Keystone, * neutron.pot in Neutron
Please notice there is no translations for log files, and there is no overwritten of existing translations.
Coordinators of Italian, French, German, Japanese, Spanish, Chinese(China), Chinese(Taiwan), Korean(South Korea),Portuguese (Brazil) and Russian: You could start the review now:
https://translate.openstack.org/version-group/view/ibm-translations-group.
If you have busy time, please review Nova as the high priority. I hope to merge Nova in Liberty release.
Thank you for your corporation.
Today's import includes all the translations, see:
https://review.openstack.org/#/q/status:open++branch:master +topic:zanata/translations,n,z
Thanks Doug and team for this!
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these: https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/ That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as translator, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
As Andreas pointed out, some IBM translations are uploaded into MASTER branch. I checked Zanata and see this in Japanese at least for neutron master branch. Daisy, Could you check the situation? 2015-09-22 23:41 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these:
https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/
That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as translator,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
My first feeling is that it is filled from TM automatically. I need a deeper check. Best regards Ying Chun Guo (Daisy) Andreas Jaeger <aj@suse.com> wrote on 09/22/2015 10:41:00 PM:
From: Andreas Jaeger <aj@suse.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 09/22/2015 10:41 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these:
https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/
That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as translator,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
I finally understand the cause. Those translations are copied from IBM branches to master branches. The copy action is trigged by the update of pot files. There are Jenkins jobs automatically uploading pot files by CLI when there are changes. This caused the translations copied from IBM branches to master. Refer to Zanata help document[1], it is said: Copy Trans usually runs automatically when a document is uploaded using the cli-client. While I did test on the test server ( http://translate-dev.openstack.org ), there was no such auto jobs running for test server, so I didn't recognize uploading of pot files could cause the copy action. I apologize for missing this point. What we should do now is to figure out how to handle the situation. Best regards Ying Chun Guo (Daisy) [1] http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/ Andreas Jaeger <aj@suse.com> wrote on 09/22/2015 10:41:00 PM:
From: Andreas Jaeger <aj@suse.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 09/22/2015 10:41 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these:
https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/
That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as translator,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Daisy, I suggest disable copy trans when pushing, `--copy-trans false`. We are currently working on disable the copy trans: https://zanata.atlassian.net/browse/ZNTA-664 --------------------------------------------- Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Wed, Sep 23, 2015 at 2:13 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
I finally understand the cause. Those translations are copied from IBM branches to master branches.
The copy action is trigged by the update of pot files. There are Jenkins jobs automatically uploading pot files by CLI when there are changes. This caused the translations copied from IBM branches to master.
Refer to Zanata help document[1], it is said: Copy Trans usually runs automatically when a document is uploaded using the cli-client.
While I did test on the test server ( http://translate-dev.openstack.org ), there was no such auto jobs running for test server, so I didn't recognize uploading of pot files could cause the copy action. I apologize for missing this point.
What we should do now is to figure out how to handle the situation.
Best regards Ying Chun Guo (Daisy)
[1] http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/
Andreas Jaeger <aj@suse.com> wrote on 09/22/2015 10:41:00 PM:
From: Andreas Jaeger <aj@suse.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" < openstack-i18n@lists.openstack.org> Date: 09/22/2015 10:41 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these:
https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/
That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as translator,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Daisy, To add a bit more detail to what Alex said, we are planning in disabling copy trans *by default*. It will still be available to use by providing a command line option. But to your point, I was certain that we had specified the option to disable copy trans when pushing. Maybe this was just on the migration scripts and not the Jenkins jobs perhaps? Carlos. On Wednesday, 23 September 2015, Alex Eng <aeng@redhat.com> wrote:
Daisy,
I suggest disable copy trans when pushing, `--copy-trans false`.
We are currently working on disable the copy trans: https://zanata.atlassian.net/browse/ZNTA-664
---------------------------------------------
Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com
On Wed, Sep 23, 2015 at 2:13 AM, Ying Chun Guo <guoyingc@cn.ibm.com <javascript:_e(%7B%7D,'cvml','guoyingc@cn.ibm.com');>> wrote:
I finally understand the cause. Those translations are copied from IBM branches to master branches.
The copy action is trigged by the update of pot files. There are Jenkins jobs automatically uploading pot files by CLI when there are changes. This caused the translations copied from IBM branches to master.
Refer to Zanata help document[1], it is said: Copy Trans usually runs automatically when a document is uploaded using the cli-client.
While I did test on the test server ( http://translate-dev.openstack.org ), there was no such auto jobs running for test server, so I didn't recognize uploading of pot files could cause the copy action. I apologize for missing this point.
What we should do now is to figure out how to handle the situation.
Best regards Ying Chun Guo (Daisy)
[1] http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/
Andreas Jaeger <aj@suse.com <javascript:_e(%7B%7D,'cvml','aj@suse.com');>> wrote on 09/22/2015 10:41:00 PM:
From: Andreas Jaeger <aj@suse.com <javascript:_e(%7B%7D,'cvml','aj@suse.com');>> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','openstack-i18n@lists.openstack.org');>" < openstack-i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','openstack-i18n@lists.openstack.org');>> Date: 09/22/2015 10:41 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these:
https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/
That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as translator,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','Openstack-i18n@lists.openstack.org');> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Carlos A. Muñoz Software Engineering Supervisor Globalization Red Hat
On 2015-09-22 23:50, Carlos Munoz wrote:
Hi Daisy,
To add a bit more detail to what Alex said, we are planning in disabling copy trans *by default*. It will still be available to use by providing a command line option.
But to your point, I was certain that we had specified the option to disable copy trans when pushing. Maybe this was just on the migration scripts and not the Jenkins jobs perhaps?
It was on neither of these - but it's now on the push script. Still anybody manually uploading sources will trigger this but very few do - so the default override is great. Thanks, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
From: Carlos Munoz <camunoz@redhat.com> To: Alex Eng <aeng@redhat.com> Cc: Ying Chun Guo/China/IBM@IBMCN, Andreas Jaeger <aj@suse.com>, "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 09/23/2015 05:50 AM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
Hi Daisy,
To add a bit more detail to what Alex said, we are planning in disabling copy trans *by default*. It will still be available to use by providing a command line option.
But to your point, I was certain that we had specified the option to disable copy trans when pushing. Maybe this was just on the migration scripts and not the Jenkins jobs perhaps?
Carlos.
On Wednesday, 23 September 2015, Alex Eng <aeng@redhat.com> wrote: Daisy,
I suggest disable copy trans when pushing, `--copy-trans false`.
We are currently working on disable the copy trans: https://zanata.atlassian.net/browse/ZNTA-664
---------------------------------------------
Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com
On Wed, Sep 23, 2015 at 2:13 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote: I finally understand the cause. Those translations are copied from IBM branches to master branches.
The copy action is trigged by the update of pot files. There are Jenkins jobs automatically uploading pot files by CLI when there are changes. This caused the translations copied from IBM branches to master.
Refer to Zanata help document[1], it is said: Copy Trans usually runs automatically when a document is uploaded using the cli-client.
While I did test on the test server ( http://translate-dev.openstack.org ), there was no such auto jobs running for test server, so I didn't recognize uploading of pot files could cause the copy action. I apologize for missing this point.
What we should do now is to figure out how to handle the situation.
Best regards Ying Chun Guo (Daisy)
[1] http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/
Andreas Jaeger <aj@suse.com> wrote on 09/22/2015 10:41:00 PM:
From: Andreas Jaeger <aj@suse.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org
Date: 09/22/2015 10:41 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these:
https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/
That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as
Yes, Carlos. Infra team have add "--copy-trans false" to Jenkins jobs yesterday. Best regards Ying Chun Guo (Daisy) Carlos Munoz <camunoz@redhat.com> wrote on 09/23/2015 05:50:02 AM: translator,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica:
jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Carlos A. Muñoz Software Engineering Supervisor Globalization Red Hat
A feedback is provided to Zanata feature tacking website. https://zanata.atlassian.net/browse/ZNTA-698
From the perspective of Zanata admin, I hope Zanata could support one more rule: version mismatch in the "Copy Translations" setting page. I hope it could support "disable auto CopyTrans" at all in the "Copy Translations" setting page.
From: Carlos Munoz <camunoz@redhat.com> To: Alex Eng <aeng@redhat.com> Cc: Ying Chun Guo/China/IBM@IBMCN, Andreas Jaeger <aj@suse.com>, "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 09/23/2015 05:50 AM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
Hi Daisy,
To add a bit more detail to what Alex said, we are planning in disabling copy trans *by default*. It will still be available to use by providing a command line option.
But to your point, I was certain that we had specified the option to disable copy trans when pushing. Maybe this was just on the migration scripts and not the Jenkins jobs perhaps?
Carlos.
On Wednesday, 23 September 2015, Alex Eng <aeng@redhat.com> wrote: Daisy,
I suggest disable copy trans when pushing, `--copy-trans false`.
We are currently working on disable the copy trans: https://zanata.atlassian.net/browse/ZNTA-664
---------------------------------------------
Alex Eng Globalisation Tools Engineering DID: +61 3514 8262 Mobile: +614 2335 3457
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 Fax: +61 7 3514 8199 Website: www.redhat.com
On Wed, Sep 23, 2015 at 2:13 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote: I finally understand the cause. Those translations are copied from IBM branches to master branches.
The copy action is trigged by the update of pot files. There are Jenkins jobs automatically uploading pot files by CLI when there are changes. This caused the translations copied from IBM branches to master.
Refer to Zanata help document[1], it is said: Copy Trans usually runs automatically when a document is uploaded using the cli-client.
While I did test on the test server ( http://translate-dev.openstack.org ), there was no such auto jobs running for test server, so I didn't recognize uploading of pot files could cause the copy action. I apologize for missing this point.
What we should do now is to figure out how to handle the situation.
Best regards Ying Chun Guo (Daisy)
[1] http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/
Andreas Jaeger <aj@suse.com> wrote on 09/22/2015 10:41:00 PM:
From: Andreas Jaeger <aj@suse.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org
Date: 09/22/2015 10:41 PM Subject: Re: [Openstack-i18n] IBM translations to contribute: waiting for review
On 2015-09-22 15:40, Ying Chun Guo wrote:
I think they are not IBM translations. IBM translations are not merged into master branches yet. They are still in pre-review status. After coordinators review, these translations could be merged into master or liberty branches in Zanata. After that, the importing could happen.
Have a look at these:
https://review.openstack.org/#/c/225557/ https://review.openstack.org/#/c/226186/
That's such a large import, I would be surprised if those are not the IBM translations - and they have Tom Cocozzello mentioned as
Best regards Ying Chun Guo (Daisy) Carlos Munoz <camunoz@redhat.com> wrote on 09/23/2015 05:50:02 AM: translator,
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica:
jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
-- Carlos A. Muñoz Software Engineering Supervisor Globalization Red Hat
I finally understand the cause. Those translations are copied from IBM branches to master branches.
The copy action is trigged by the update of pot files. There are Jenkins jobs automatically uploading pot files by CLI when there are changes. This caused the translations copied from IBM branches to master.
Refer to Zanata help document[1], it is said: Copy Trans usually runs automatically when a document is uploaded using the cli-client.
While I did test on the test server ( http://translate-dev.openstack.org ), there was no such auto jobs running for test server, so I didn't recognize uploading of pot files could cause the copy action. I apologize for missing this point.
What we should do now is to figure out how to handle the situation.
Best regards Ying Chun Guo (Daisy)
[1] http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/
Hi Daisy, Thank you for detailed investigation. This is not a problem. No need apolpgize. Just need a little more action. Let's hurry coordinator's review. Regards, KATO Tomoyuki
Versions have been created for IBM to import their translations in the production server. These resources could be browsed through a "group" view. https://translate.openstack.org/version-group/view/ibm-translations-group
@ Doug, I think you could start uploading now.
Best regards Ying Chun Guo (Daisy)
At now, already merged master branch in prod server... I found IBM translation does not meet some Japanese translation conventions in our team. Therefore, these translations differ from horizon as of now. I will fix as possible. If IBM contributes translation next time, it is really welcome. However, I wloud like to share Japanese translation conventions and glossary before translation. Regards, KATO Tomoyuki
participants (6)
-
Akihiro Motoki
-
Alex Eng
-
Andreas Jaeger
-
Carlos Munoz
-
KATO Tomoyuki
-
Ying Chun Guo