Zanata trial starts ! Please register and try.
Hello, team Infra team have set up the Zanata test instance on top of openstack infrastructure. OpenStack projects, together with the translations, in Transifex have been moved to Zanata test instance now. So we could start the Zanata trial now. https://translate-dev.openstack.org/ (it's a self-signed certificate, so you will be presented with a warning, it's ok) 1. Log in You can use your OpenStack ID to log in. If you don't have, register here: https://www.openstack.org/join/register I will suggest to register with your company email, which will help your company to get the credit. If you don't want to, that's OK. :)) When you log in, you will be required to fill in your profile. Then you can start the trial. 2. Join a translation team List all languages by clicking "Languages" on the top. Click your language, you will go to that language page. On the right of the language name, there is a button "^..." which means "more actions". Click on the button and select "Request to Join Team". Then wait for your request to be approved. When it is approved, you will get the email notification. 3. Manage your team member if you are a coordinator If you are assigned a coordinator role, you will be able to see "Add Team Members" in the language page after clicking "^..." (more actions). You can only search users by user id. You can assign a member different roles (translator, reviewer, coordinator) 4. Translate After you have a language team, list the projects by clicking "Projects" on the top. Select a project, select a version, then you can translate. 5. Feedback We hope to get your feedback to the Zanata trial. If you find any resources/translations missed, which is in Transifex but not in Zanata, please let us know. If you find any bugs, please let us know. If you don't know how to operate, please let us know. We use https://etherpad.openstack.org/p/zanata-feedback to track the feedback. Reference link: Documentation for Zanata can be found here: http://docs.zanata.org/en/release/ Specifically for translators: http://docs.zanata.org/en/release/user-guide/translator-guide/ Note: 1. This is only a trial. All the projects, teams, and translations will not be preserved. This test instance will be wrapped off when the trail is done. Then infra team will create a formal website. You will be notified when we officially move to Zanata. Now if you want to translate, please still use Transifex for your primary translations work. Your registration to OpenStack ID will be preserved for ever. When we officially move to Zanata, you don't need to register again. But we need to create the language team once more. 2. Anyone can create projects, for the sake of this demonstration please don't create your own Thanks! Best regards Ying Chun Guo (Daisy)
Daisy, Thanks for your all efforts. I have some questions. * When do we start translations on Zanata? Liberty cycle? * There is no translation memories. Are some translation memories migrated from Transifex? * Do we collect translation stats for Liberty? Some translators already translated on Transifex and if they don't take into account it is unfair. I know you said it is a trial, so I just wonders when we switch the translation infra. Akihiro 2015-07-14 18:57 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Hello, team
Infra team have set up the Zanata test instance on top of openstack infrastructure. OpenStack projects, together with the translations, in Transifex have been moved to Zanata test instance now. So we could start the Zanata trial now.
https://translate-dev.openstack.org/ (it's a self-signed certificate, so you will be presented with a warning, it's ok)
1. Log in You can use your OpenStack ID to log in. If you don't have, register here: https://www.openstack.org/join/register I will suggest to register with your company email, which will help your company to get the credit. If you don't want to, that's OK. :)) When you log in, you will be required to fill in your profile. Then you can start the trial.
2. Join a translation team List all languages by clicking "Languages" on the top. Click your language, you will go to that language page. On the right of the language name, there is a button "^..." which means "more actions". Click on the button and select "Request to Join Team". Then wait for your request to be approved. When it is approved, you will get the email notification.
3. Manage your team member if you are a coordinator If you are assigned a coordinator role, you will be able to see "Add Team Members" in the language page after clicking "^..." (more actions). You can only search users by user id. You can assign a member different roles (translator, reviewer, coordinator)
4. Translate After you have a language team, list the projects by clicking "Projects" on the top. Select a project, select a version, then you can translate.
5. Feedback We hope to get your feedback to the Zanata trial. If you find any resources/translations missed, which is in Transifex but not in Zanata, please let us know. If you find any bugs, please let us know. If you don't know how to operate, please let us know. We use https://etherpad.openstack.org/p/zanata-feedback to track the feedback.
Reference link: Documentation for Zanata can be found here: http://docs.zanata.org/en/release/ Specifically for translators: http://docs.zanata.org/en/release/user-guide/translator-guide/
Note: 1. This is only a trial. All the projects, teams, and translations will not be preserved. This test instance will be wrapped off when the trail is done. Then infra team will create a formal website. You will be notified when we officially move to Zanata. Now if you want to translate, please still use Transifex for your primary translations work. Your registration to OpenStack ID will be preserved for ever. When we officially move to Zanata, you don't need to register again. But we need to create the language team once more.
2. Anyone can create projects, for the sake of this demonstration please don't create your own
Thanks!
Best regards Ying Chun Guo (Daisy)
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 07/15/2015 06:19 AM, Akihiro Motoki wrote:
Daisy,
Thanks for your all efforts. I have some questions.
* When do we start translations on Zanata? Liberty cycle?
This cycle - as soon as everything is working ;)
* There is no translation memories. Are some translation memories migrated from Transifex?
What do you mean exactly? Did Steve not migrate all translated strings or do you miss the separate translation memory?
* Do we collect translation stats for Liberty? Some translators already translated on Transifex and if they don't take into account it is unfair.
They were not counted in Transifex, we cannot fix that.
I know you said it is a trial, so I just wonders when we switch the translation infra.
I hope soon ;) Andreas
Akihiro
2015-07-14 18:57 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com <mailto:guoyingc@cn.ibm.com>>:
Hello, team
Infra team have set up the Zanata test instance on top of openstack infrastructure. OpenStack projects, together with the translations, in Transifex have been moved to Zanata test instance now. So we could start the Zanata trial now.
https://translate-dev.openstack.org/ (it's a self-signed certificate, so you will be presented with a warning, it's ok)
1. Log in You can use your OpenStack ID to log in. If you don't have, register here: https://www.openstack.org/join/register I will suggest to register with your company email, which will help your company to get the credit. If you don't want to, that's OK. :)) When you log in, you will be required to fill in your profile. Then you can start the trial.
2. Join a translation team List all languages by clicking "Languages" on the top. Click your language, you will go to that language page. On the right of the language name, there is a button "^..." which means "more actions". Click on the button and select "Request to Join Team". Then wait for your request to be approved. When it is approved, you will get the email notification.
3. Manage your team member if you are a coordinator If you are assigned a coordinator role, you will be able to see "Add Team Members" in the language page after clicking "^..." (more actions). You can only search users by user id. You can assign a member different roles (translator, reviewer, coordinator)
4. Translate After you have a language team, list the projects by clicking "Projects" on the top. Select a project, select a version, then you can translate.
5. Feedback We hope to get your feedback to the Zanata trial. If you find any resources/translations missed, which is in Transifex but not in Zanata, please let us know. If you find any bugs, please let us know. If you don't know how to operate, please let us know. We use https://etherpad.openstack.org/p/zanata-feedback to track the feedback.
Reference link: Documentation for Zanata can be found here: http://docs.zanata.org/en/release/ Specifically for translators: http://docs.zanata.org/en/release/user-guide/translator-guide/
Note: 1. This is only a trial. All the projects, teams, and translations will not be preserved. This test instance will be wrapped off when the trail is done. Then infra team will create a formal website. You will be notified when we officially move to Zanata. Now if you want to translate, please still use Transifex for your primary translations work. Your registration to OpenStack ID will be preserved for ever. When we officially move to Zanata, you don't need to register again. But we need to create the language team once more.
2. Anyone can create projects, for the sake of this demonstration please don't create your own
Thanks!
Best regards Ying Chun Guo (Daisy)
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto: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
-- 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
2015-07-15 15:27 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 07/15/2015 06:19 AM, Akihiro Motoki wrote:
Daisy,
Thanks for your all efforts. I have some questions.
* When do we start translations on Zanata? Liberty cycle?
This cycle - as soon as everything is working ;)
* There is no translation memories. Are some translation memories
migrated from Transifex?
What do you mean exactly? Did Steve not migrate all translated strings or do you miss the separate translation memory?
When I visit horizon translations in Japanese, I seem 0.0% translated for all languages. I just created an account on Zanata and have not joined any lang team, so it may affect what I see.
* Do we collect translation stats for Liberty? Some translators already
translated on Transifex and if they don't take into account it is unfair.
They were not counted in Transifex, we cannot fix that.
I recently translated around 200 strings in Transifex. That seems a mistake and I should have wait. If I18N project use the stats in Liberty for some official use (like ATC), it should be announced as soon as possible how it affects. Akihiro
I know you said it is a trial, so I just wonders when we switch the
translation infra.
I hope soon ;)
Andreas
Akihiro
2015-07-14 18:57 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com <mailto:guoyingc@cn.ibm.com>>:
Hello, team
Infra team have set up the Zanata test instance on top of openstack infrastructure. OpenStack projects, together with the translations, in Transifex have been moved to Zanata test instance now. So we could start the Zanata trial now.
https://translate-dev.openstack.org/ (it's a self-signed certificate, so you will be presented with a warning, it's ok)
1. Log in You can use your OpenStack ID to log in. If you don't have, register here: https://www.openstack.org/join/register I will suggest to register with your company email, which will help your company to get the credit. If you don't want to, that's OK. :)) When you log in, you will be required to fill in your profile. Then you can start the trial.
2. Join a translation team List all languages by clicking "Languages" on the top. Click your language, you will go to that language page. On the right of the language name, there is a button "^..." which means "more actions". Click on the button and select "Request to Join Team". Then wait for your request to be approved. When it is approved, you will get the email notification.
3. Manage your team member if you are a coordinator If you are assigned a coordinator role, you will be able to see "Add Team Members" in the language page after clicking "^..." (more actions). You can only search users by user id. You can assign a member different roles (translator, reviewer, coordinator)
4. Translate After you have a language team, list the projects by clicking "Projects" on the top. Select a project, select a version, then you can translate.
5. Feedback We hope to get your feedback to the Zanata trial. If you find any resources/translations missed, which is in Transifex but not in Zanata, please let us know. If you find any bugs, please let us know. If you don't know how to operate, please let us know. We use https://etherpad.openstack.org/p/zanata-feedback to track the feedback.
Reference link: Documentation for Zanata can be found here: http://docs.zanata.org/en/release/ Specifically for translators: http://docs.zanata.org/en/release/user-guide/translator-guide/
Note: 1. This is only a trial. All the projects, teams, and translations will not be preserved. This test instance will be wrapped off when the trail is done. Then infra team will create a formal website. You will be notified when we officially move to Zanata. Now if you want to translate, please still use Transifex for your primary translations work. Your registration to OpenStack ID will be preserved for ever. When we officially move to Zanata, you don't need to register again. But we need to create the language team once more.
2. Anyone can create projects, for the sake of this demonstration please don't create your own
Thanks!
Best regards Ying Chun Guo (Daisy)
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto: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
-- 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Some update. Kato-san added me to the lang team and I tried some on Zanata. Generally looks good. One question I have is how I can know a specific string comes from which part of codes. I often check the source code to check its context, but I don't see any information from Zanata interface. Some message is too short to grep codes, so location information is nice. For example, I see one word message "of" and it is not easy to find out it in the code. Is there any convenient way to know this kind of information? (Transifex provides this information and I usually use the information.) Regarding translation memory, it was my mistake and confusion. Sorry, I see some suggestions which seems from translation memory. It is no so attractive at first, but after importing Japanese translation from Transifex, the translation memory became nice and it now looks similar level as Transifex. Akihiro 2015-07-15 16:00 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:
2015-07-15 15:27 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 07/15/2015 06:19 AM, Akihiro Motoki wrote:
Daisy,
Thanks for your all efforts. I have some questions.
* When do we start translations on Zanata? Liberty cycle?
This cycle - as soon as everything is working ;)
* There is no translation memories. Are some translation memories
migrated from Transifex?
What do you mean exactly? Did Steve not migrate all translated strings or do you miss the separate translation memory?
When I visit horizon translations in Japanese, I seem 0.0% translated for all languages. I just created an account on Zanata and have not joined any lang team, so it may affect what I see.
* Do we collect translation stats for Liberty? Some translators already
translated on Transifex and if they don't take into account it is unfair.
They were not counted in Transifex, we cannot fix that.
I recently translated around 200 strings in Transifex. That seems a mistake and I should have wait.
If I18N project use the stats in Liberty for some official use (like ATC), it should be announced as soon as possible how it affects.
Akihiro
I know you said it is a trial, so I just wonders when we switch the
translation infra.
I hope soon ;)
Andreas
Akihiro
2015-07-14 18:57 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com <mailto:guoyingc@cn.ibm.com>>:
Hello, team
Infra team have set up the Zanata test instance on top of openstack infrastructure. OpenStack projects, together with the translations, in Transifex have been moved to Zanata test instance now. So we could start the Zanata trial now.
https://translate-dev.openstack.org/ (it's a self-signed certificate, so you will be presented with a warning, it's ok)
1. Log in You can use your OpenStack ID to log in. If you don't have, register here: https://www.openstack.org/join/register I will suggest to register with your company email, which will help your company to get the credit. If you don't want to, that's OK. :)) When you log in, you will be required to fill in your profile. Then you can start the trial.
2. Join a translation team List all languages by clicking "Languages" on the top. Click your language, you will go to that language page. On the right of the language name, there is a button "^..." which means "more actions". Click on the button and select "Request to Join Team". Then wait for your request to be approved. When it is approved, you will get the email notification.
3. Manage your team member if you are a coordinator If you are assigned a coordinator role, you will be able to see "Add Team Members" in the language page after clicking "^..." (more actions). You can only search users by user id. You can assign a member different roles (translator, reviewer, coordinator)
4. Translate After you have a language team, list the projects by clicking "Projects" on the top. Select a project, select a version, then you can translate.
5. Feedback We hope to get your feedback to the Zanata trial. If you find any resources/translations missed, which is in Transifex but not in Zanata, please let us know. If you find any bugs, please let us know. If you don't know how to operate, please let us know. We use https://etherpad.openstack.org/p/zanata-feedback to track the feedback.
Reference link: Documentation for Zanata can be found here: http://docs.zanata.org/en/release/ Specifically for translators: http://docs.zanata.org/en/release/user-guide/translator-guide/
Note: 1. This is only a trial. All the projects, teams, and translations will not be preserved. This test instance will be wrapped off when the trail is done. Then infra team will create a formal website. You will be notified when we officially move to Zanata. Now if you want to translate, please still use Transifex for your primary translations work. Your registration to OpenStack ID will be preserved for ever. When we officially move to Zanata, you don't need to register again. But we need to create the language team once more.
2. Anyone can create projects, for the sake of this demonstration please don't create your own
Thanks!
Best regards Ying Chun Guo (Daisy)
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto: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
-- 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
One question I have is how I can know a specific string comes from which part of codes. I often check the source code to check its context, but I don't see any information from Zanata interface. Some message is too short to grep codes, so location information is nice. For example, I see one word message "of" and it is not easy to find out it in the code. Is there any convenient way to know this kind of information? (Transifex provides this information and I usually use the information.)
I think this is derived from our language "po" files don't contain filenames and line numbers any more. In my guess, Transifex display this information from the same msgid as the corresponding "pot" file. So, I think we need to consult Zanata team. KATO Tomoyuki
Kato, Zanata stores source string information if there comments in the source file. I've attached a screenshot. You will need to expend the information section of the source string by clicking on the highlighted square below the source string. Regards, Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email: aeng@redhat.com 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 16/07/15 14:09, KATO Tomoyuki wrote:
One question I have is how I can know a specific string comes from which part of codes. I often check the source code to check its context, but I don't see any information from Zanata interface. Some message is too short to grep codes, so location information is nice. For example, I see one word message "of" and it is not easy to find out it in the code. Is there any convenient way to know this kind of information? (Transifex provides this information and I usually use the information.) I think this is derived from our language "po" files don't contain filenames and line numbers any more. In my guess, Transifex display this information from the same msgid as the corresponding "pot" file. So, I think we need to consult Zanata team.
KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Kato, Zanata stores source string information if there comments in the source file. I've attached a screenshot. You will need to expend the information section of the source string by clicking on the highlighted square below the source string. Regards, Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email: aeng@redhat.com 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 16/07/15 14:09, KATO Tomoyuki wrote:
One question I have is how I can know a specific string comes from which part of codes. I often check the source code to check its context, but I don't see any information from Zanata interface. Some message is too short to grep codes, so location information is nice. For example, I see one word message "of" and it is not easy to find out it in the code. Is there any convenient way to know this kind of information? (Transifex provides this information and I usually use the information.) I think this is derived from our language "po" files don't contain filenames and line numbers any more. In my guess, Transifex display this information from the same msgid as the corresponding "pot" file. So, I think we need to consult Zanata team.
KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Alex, I see the same information but the information is not enough to me. Transifex provides information like the location in the source code as you see in my attached image. In POT file (e.g. horizon/openstack_dashboard/locale/django.pot), I see the location of the source code: ---- #: api/ceilometer.py:1140 msgid "Image existence check" msgstr "" but I don't see any information like api/ceilometer.py 1140 in Zanata UI. I believe this information is important to give feedback to the upstream. I am not sure POT file which is used for uploading has this kind information. Akihiro 2015-07-16 13:31 GMT+09:00 Alex Eng <aeng@redhat.com>:
Hi Kato,
Zanata stores source string information if there comments in the source file.
I've attached a screenshot. You will need to expend the information section of the source string by clicking on the highlighted square below the source string.
Regards,
Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email: aeng@redhat.com
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 16/07/15 14:09, KATO Tomoyuki wrote:
One question I have is how I can know a specific string comes from which part of codes. I often check the source code to check its context, but I don't see any information from Zanata interface. Some message is too short to grep codes, so location information is nice. For example, I see one word message "of" and it is not easy to find out it in the code. Is there any convenient way to know this kind of information? (Transifex provides this information and I usually use the information.)
I think this is derived from our language "po" files don't contain filenames and line numbers any more. In my guess, Transifex display this information from the same msgid as the corresponding "pot" file. So, I think we need to consult Zanata team.
KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing listOpenstack-i18n@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Kato, I've confirmed that the source reference is being stored in Zanata, but it's not visible in the editor. I've filed a bug for it: https://bugzilla.redhat.com/show_bug.cgi?id=1243672 Regards, Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email: aeng@redhat.com 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 16/07/15 14:52, Akihiro Motoki wrote:
Alex,
I see the same information but the information is not enough to me. Transifex provides information like the location in the source code as you see in my attached image.
In POT file (e.g. horizon/openstack_dashboard/locale/django.pot), I see the location of the source code: ---- #: api/ceilometer.py:1140 msgid "Image existence check" msgstr ""
but I don't see any information like api/ceilometer.py 1140 in Zanata UI. I believe this information is important to give feedback to the upstream.
I am not sure POT file which is used for uploading has this kind information.
Akihiro
2015-07-16 13:31 GMT+09:00 Alex Eng <aeng@redhat.com <mailto:aeng@redhat.com>>:
Hi Kato,
Zanata stores source string information if there comments in the source file.
I've attached a screenshot. You will need to expend the information section of the source string by clicking on the highlighted square below the source string.
Regards,
Alex Eng Senior Software Engineer DID: +61 3514 8262 Mobile: +614 2335 3457 Email:aeng@redhat.com <mailto:aeng@redhat.com>
Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office:+61 7 3514 8100 <tel:%2B61%207%203514%208100> Fax:+61 7 3514 8199 <tel:%2B61%207%203514%208199> Website:www.redhat.com <http://www.redhat.com>
On 16/07/15 14:09, KATO Tomoyuki wrote:
One question I have is how I can know a specific string comes from which part of codes. I often check the source code to check its context, but I don't see any information from Zanata interface. Some message is too short to grep codes, so location information is nice. For example, I see one word message "of" and it is not easy to find out it in the code. Is there any convenient way to know this kind of information? (Transifex provides this information and I usually use the information.)
I think this is derived from our language "po" files don't contain filenames and line numbers any more. In my guess, Transifex display this information from the same msgid as the corresponding "pot" file. So, I think we need to consult Zanata team.
KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto:Openstack-i18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Alex, Akihiro Thanks! I think this feature is very important to the translators(include me). KATO Tomoyuki
Hi Kato,
I've confirmed that the source reference is being stored in Zanata, but it's not visible in the editor. I've filed a bug for it: https://bugzilla.redhat.com/show_bug.cgi?id=1243672
Regards,
From: KATO Tomoyuki <tomo@dream.daynight.jp> To: Alex Eng <aeng@redhat.com> Cc: Openstack-i18n Openstack-i18n <openstack- i18n@lists.openstack.org>, Steve Kowalik <steven@wedontsleep.org> Date: 2015/07/16 14:57 Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register and
Thank you all for the feedback. I have summarize feedback here: https://etherpad.openstack.org/p/zanata-feedback If I miss yours by mistake, feel free to add. Best regards Ying Chun Guo (Daisy) KATO Tomoyuki <tomo@dream.daynight.jp> wrote on 2015/07/16 14:55:54: try.
Hi Alex, Akihiro
Thanks! I think this feature is very important to the translators(include me).
KATO Tomoyuki
Hi Kato,
I've confirmed that the source reference is being stored in Zanata, but
it's not visible in the editor. I've filed a bug for it: https://bugzilla.redhat.com/show_bug.cgi?id=1243672
Regards,
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On Thu, Jul 16, 2015 at 2:19 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Thank you all for the feedback. I have summarize feedback here: https://etherpad.openstack.org/p/zanata-feedback If I miss yours by mistake, feel free to add.
Thanks for putting all of this in one place! I let it sit for several days and there were a additions made to the document. This morning I went through the notes and left several comments that I signed with "(pleia2, July 28)". If some of you could look through my notes and answer the questions I asked, it would be nice to get these all to a point where we can properly handle each them and see what exactly is required before we go into production. My vision is to have a list of things that are absolutely required before we go into production, and then a wishlist of things that may be important, but we could go into production without them. I still have a few tasks on the infra side to improve how we deploy Zanata itself, I'll let you know when to expect service disruption on translate-dev. Finally, I'll be traveling for a couple weeks from August 5-19th for a couple conferences and some vacation time. I'll still be reachable via email, except Aug 11-16 when I'll be hiking through the Andes with limited internet access. -- Elizabeth Krumbach Joseph || Lyz || pleia2
Hi, Elizabeth I reviewed the feedback in Etherpad together with the team last week, and got two requirements before going into production. 1. Language codes In Transifex, there are 44 languages which have progress. Some of the language codes only contain language codes, the others contain language codes plus locale codes. The language code format in Transifex is language codes ( in small case ) + underline ("_") + locale codes ( in big case ), for example, ko_KR. The language code format in Zanata is language codes ( in small case ) + hyphen ("-") + locale codes ( in small case ), for example, ko-kr. I don't know if the different format will cause issues because language codes are the folder names in OpenStack git repo. Refer to Horizon repo [1]. Please help to verify that. Besides the format differences, I also notice some languages are missed in Zanata. They are: bg_BG, gu, ks, kok, mai, mni, mr, pa_IN, ta, ur. These languages should be added. And in Zanata, there are some languages which should be removed from Zanata. They are: bn, nl, en-au, en-Au, en-aU, en-gb, fi, ko, pl-P, pl-p, pt-B, sl-, te. Considering the format differences and the language lists differences, I suggest that we update the database to configure the language codes just same as Transifex. And then export all the translations of these languages into Zanata. I have written down the list of language codes in Transfiex which have any progress in the trail feedback page. [2] 2. Session time It looks like the session time of Zanata is much shorter than in Transfiex. Carlos said there was a way to config a longer session time. Is it possible to make it happen before we go to production? Please let me know your thoughts if these requirements look reasonable. Thank you. Best regards Ying Chun Guo (Daisy) [1] http://git.openstack.org/cgit/openstack/horizon/tree/horizon/locale [2] https://etherpad.openstack.org/p/zanata-feedback "Elizabeth K. Joseph" <lyz@princessleia.com> wrote on 07/29/2015 08:16:37 AM:
From: "Elizabeth K. Joseph" <lyz@princessleia.com> To: Openstack-i18n Openstack-i18n <openstack-i18n@lists.openstack.org> Cc: Steve Kowalik <steven@wedontsleep.org> Date: 07/29/2015 08:17 AM Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register and try - Feedback summrized in etherpad.
On Thu, Jul 16, 2015 at 2:19 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Thank you all for the feedback. I have summarize feedback here: https://etherpad.openstack.org/p/zanata-feedback If I miss yours by mistake, feel free to add.
Thanks for putting all of this in one place! I let it sit for several days and there were a additions made to the document.
This morning I went through the notes and left several comments that I signed with "(pleia2, July 28)". If some of you could look through my notes and answer the questions I asked, it would be nice to get these all to a point where we can properly handle each them and see what exactly is required before we go into production. My vision is to have a list of things that are absolutely required before we go into production, and then a wishlist of things that may be important, but we could go into production without them.
I still have a few tasks on the infra side to improve how we deploy Zanata itself, I'll let you know when to expect service disruption on translate-dev.
Finally, I'll be traveling for a couple weeks from August 5-19th for a couple conferences and some vacation time. I'll still be reachable via email, except Aug 11-16 when I'll be hiking through the Andes with limited internet access.
-- Elizabeth Krumbach Joseph || Lyz || pleia2
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On Mon, Aug 10, 2015 at 2:43 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Hi, Elizabeth
I reviewed the feedback in Etherpad together with the team last week, and got two requirements before going into production.
I'm back from my travels! Thanks for putting this together, I also reviewed meeting logs. While I was gone, Clark was able to upgrade Zanata to the latest version (thanks Clark!). It introduced a language code change that Steve has been able to address (change merged today). Aside from what is mentioned in this email, currently on our plate before we go into production, since it's easier to fix now rather than after we go into production: 1. Upgrade to the newer Java Application Server, Wildfly 9 (we're on 8.1) 2. Make the Puppet-based installation less brittle Once this is done, we'll deploy a new translate-dev.openstack.org in anticipation for launching the actual translate.openstack.org, to make sure it all looks good. I'll be spending most of my time tomorrow and over the next week making sure this all gets done. I have a bit more travel coming up, but I'll be available between planes/cars and my aim is to have a production ready translate.openstack.org ready at the latest for the week of September 7th.
1. Language codes <snip> I have written down the list of language codes in Transfiex which have any progress in the trail feedback page. [2]
Thanks for this list, Steve is now the most familiar with all of this and is currently looking into it. We'll give you a link to the updated translate-dev server once it's ready so you can review the list once we're finished with this work.
2. Session time
It looks like the session time of Zanata is much shorter than in Transfiex. Carlos said there was a way to config a longer session time. Is it possible to make it happen before we go to production?
I spoke with Carlos about this today. He's looking into the options and we'll do our best to make this happen before we go into production, I know how annoying the short timeout is. Please let me know if there is anything else that needs to be looked at.
-- Elizabeth Krumbach Joseph || Lyz || pleia2
Thank you for the update, Elizabeth. While you are working to set up Zanata ready for production, I will encourage the whole team to register ID in Zanata, and create the team structures ( the coordinators, the reviewers and the translators ) Hope the team could start Liberty translation just after the production env is ready. I don't want to spend several days on team creation even after the production env is ready. Now we have to use the test env to register ID and to create teams, I wonder if there is a way to move all the team from test env to production env. @ Carlos, need your suggestions too. Thank you. Best regards Ying Chun Guo (Daisy) "Elizabeth K. Joseph" <lyz@princessleia.com> wrote on 08/21/2015 09:41:50 AM:
From: "Elizabeth K. Joseph" <lyz@princessleia.com> To: Openstack-i18n Openstack-i18n <openstack-i18n@lists.openstack.org> Date: 08/21/2015 09:44 AM Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register and try - requirements before production
On Mon, Aug 10, 2015 at 2:43 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Hi, Elizabeth
I reviewed the feedback in Etherpad together with the team last week, and got two requirements before going into production.
I'm back from my travels! Thanks for putting this together, I also reviewed meeting logs.
While I was gone, Clark was able to upgrade Zanata to the latest version (thanks Clark!). It introduced a language code change that Steve has been able to address (change merged today).
Aside from what is mentioned in this email, currently on our plate before we go into production, since it's easier to fix now rather than after we go into production:
1. Upgrade to the newer Java Application Server, Wildfly 9 (we're on 8.1) 2. Make the Puppet-based installation less brittle
Once this is done, we'll deploy a new translate-dev.openstack.org in anticipation for launching the actual translate.openstack.org, to make sure it all looks good.
I'll be spending most of my time tomorrow and over the next week making sure this all gets done. I have a bit more travel coming up, but I'll be available between planes/cars and my aim is to have a production ready translate.openstack.org ready at the latest for the week of September 7th.
1. Language codes <snip> I have written down the list of language codes in Transfiex which have any progress in the trail feedback page. [2]
Thanks for this list, Steve is now the most familiar with all of this and is currently looking into it.
We'll give you a link to the updated translate-dev server once it's ready so you can review the list once we're finished with this work.
2. Session time
It looks like the session time of Zanata is much shorter than in Transfiex. Carlos said there was a way to config a longer session time. Is it possible to make it happen before we go to production?
I spoke with Carlos about this today. He's looking into the options and we'll do our best to make this happen before we go into production, I know how annoying the short timeout is.
Please let me know if there is anything else that needs to be looked at.
-- Elizabeth Krumbach Joseph || Lyz || pleia2
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Daisy, On 10/08/15 19:43, Ying Chun Guo wrote:
1. Language codes
In Transifex, there are 44 languages which have progress. Some of the language codes only contain language codes, the others contain language codes plus locale codes. The language code format in Transifex is language codes ( in small case ) + underline ("_") + locale codes ( in big case ), for example, ko_KR. The language code format in Zanata is language codes ( in small case ) + hyphen ("-") + locale codes ( in small case ), for example, ko-kr. I don't know if the different format will cause issues because language codes are the folder names in OpenStack git repo.
It did not with Zanata 3.6.2, since we were telling the Zanata client to map from ko-kr to ko_KR. Since the move to 3.7.1, we can not perform the mapping, so moving forward we will use ko-KR.
Refer to Horizon repo [1]. Please help to verify that.
Besides the format differences, I also notice some languages are missed in Zanata. They are: bg_BG, gu, ks, kok, mai, mni, mr, pa_IN, ta, ur. These languages should be added. And in Zanata, there are some languages which should be removed from Zanata. They are: bn, nl, en-au, en-Au, en-aU, en-gb, fi, ko, pl-P, pl-p, pt-B, sl-, te.
Considering the format differences and the language lists differences, I suggest that we update the database to configure the language codes just same as Transifex. And then export all the translations of these languages into Zanata.
I have written down the list of language codes in Transfiex which have any progress in the trail feedback page. [2]
I have gone through your list, and converted them into the locale code that Zanata expects (a dash, rather than an underscore). When Elizabeth and I set up the new translate-dev, I will be creating the following locales on it: http://paste.openstack.org/show/423139/ Can you look over that list and let me know if there are any you wish to add or remove? Cheers, -- Steve <bob2> joy hasn't spoken on IRC in 45 seconds, he must be MIA!
From: Steve Kowalik <steven@wedontsleep.org> To: Ying Chun Guo/China/IBM@IBMCN, "Elizabeth K. Joseph" <lyz@princessleia.com> Cc: Openstack-i18n Openstack-i18n <openstack-i18n@lists.openstack.org> Date: 08/21/2015 01:50 PM Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register and try - requirements before production
Hi Daisy,
On 10/08/15 19:43, Ying Chun Guo wrote:
1. Language codes
In Transifex, there are 44 languages which have progress. Some of the language codes only contain language codes, the others contain language codes plus locale codes. The language code format in Transifex is language codes ( in small case ) + underline ("_") + locale codes ( in big case ), for example, ko_KR. The language code format in Zanata is language codes ( in small case )
Thank you, Steve. Could you add three more languages? These languages have good progress in Horizon (only) but bad progress in the overall view. So I missed these languages in the previous list. Please add them. Filipino ( fil ) Georgian ( ka_GE) Telugu (India) (te_IN) BTW, I don't know if changing underscore to dash will cause any unexpected issues. Have you ever tried to pull translations from Zanata and then store in git repo ? I don't know if the folder names ( same as language codes ) would be changed. Or you use some special codes to change dash back to underscore while pulling translations and before storing in git repo ? Regards Daisy Steve Kowalik <steven@wedontsleep.org> wrote on 08/21/2015 01:50:24 PM: +
hyphen ("-") + locale codes ( in small case ), for example, ko-kr. I don't know if the different format will cause issues because language codes are the folder names in OpenStack git repo.
It did not with Zanata 3.6.2, since we were telling the Zanata client to
map from ko-kr to ko_KR. Since the move to 3.7.1, we can not perform the
mapping, so moving forward we will use ko-KR.
Refer to Horizon repo [1]. Please help to verify that.
Besides the format differences, I also notice some languages are missed in Zanata. They are: bg_BG, gu, ks, kok, mai, mni, mr, pa_IN, ta, ur. These languages should be added. And in Zanata, there are some languages which should be removed from Zanata. They are: bn, nl, en-au, en-Au, en-aU, en-gb, fi, ko, pl-P, pl-p, pt-B, sl-, te.
Considering the format differences and the language lists differences, I suggest that we update the database to configure the language codes just same as Transifex. And then export all the translations of these languages into Zanata.
I have written down the list of language codes in Transfiex which have any progress in the trail feedback page. [2]
I have gone through your list, and converted them into the locale code that Zanata expects (a dash, rather than an underscore).
When Elizabeth and I set up the new translate-dev, I will be creating the following locales on it:
http://paste.openstack.org/show/423139/
Can you look over that list and let me know if there are any you wish to
add or remove?
Cheers, -- Steve <bob2> joy hasn't spoken on IRC in 45 seconds, he must be MIA!
Hi Daisy, On 21/08/15 16:35, Ying Chun Guo wrote:
Could you add three more languages? These languages have good progress in Horizon (only) but bad progress in the overall view. So I missed these languages in the previous list. Please add them.
Filipino ( fil ) Telugu (India) (te_IN)
I've added these two, thanks.
Georgian ( ka_GE)
This was already in my list.
BTW, I don't know if changing underscore to dash will cause any unexpected issues. Have you ever tried to pull translations from Zanata and then store in git repo ? I don't know if the folder names ( same as language codes ) would be changed. Or you use some special codes to change dash back to underscore while pulling translations and before storing in git repo ?
I have tested it, and it works fine, the Zanata client transforms the dash back into an underscore, and writes to the correct locations in the git repo thanks to the rules we have written in the zanata.xml file. The plan is that the language codes in Zanata will be identical to the ones we use in the git repos. (Ignoring the difference between _ and -, obviously.) Thanks, -- Steve In the beginning was the word, and the word was content-type: text/plain
From: Akihiro Motoki <amotoki@gmail.com> To: Andreas Jaeger <aj@suse.com> Cc: Ying Chun Guo/China/IBM@IBMCN, Openstack-i18n Openstack-i18n <openstack-i18n@lists.openstack.org>, Steve Kowalik <steven@wedontsleep.org> Date: 2015/07/15 15:01 Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register and
Akihiro Motoki <amotoki@gmail.com> wrote on 2015/07/15 15:00:00: try.
2015-07-15 15:27 GMT+09:00 Andreas Jaeger <aj@suse.com>: On 07/15/2015 06:19 AM, Akihiro Motoki wrote: Daisy,
Thanks for your all efforts. I have some questions.
* When do we start translations on Zanata? Liberty cycle?
This cycle - as soon as everything is working ;)
* There is no translation memories. Are some translation memories migrated from Transifex?
What do you mean exactly? Did Steve not migrate all translated strings or do you miss the separate translation memory?
When I visit horizon translations in Japanese, I seem 0.0% translated for all languages. I just created an account on Zanata and have not joined any lang team, so it may affect what I see.
* Do we collect translation stats for Liberty? Some translators already translated on Transifex and if they don't take into account it is unfair.
They were not counted in Transifex, we cannot fix that.
I recently translated around 200 strings in Transifex. That seems a mistake and I should have wait.
If I18N project use the stats in Liberty for some official use (like ATC), it should be announced as soon as possible how it affects.
Akihiro
In Zanta, tt looks like we have to build stats from scratch. While we use stats for official use, if I can manually make some "make up", I will do. Like manually exporting stats from Transifex and considering them in official use. If I cannot manually change, like "translation metric" in stackalytics, we have to tolerate that. Sorry for that.
I know you said it is a trial, so I just wonders when we switch the translation infra.
I hope soon ;)
Andreas
Akihiro
2015-07-14 18:57 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com <mailto:guoyingc@cn.ibm.com>>:
Hello, team
Infra team have set up the Zanata test instance on top of openstack infrastructure. OpenStack projects, together with the translations, in Transifex have been moved to Zanata test instance now. So we could start the Zanata trial now.
https://translate-dev.openstack.org/ (it's a self-signed certificate, so you will be presented with a warning, it's ok)
1. Log in You can use your OpenStack ID to log in. If you don't have, register here: https://www.openstack.org/join/register I will suggest to register with your company email, which will help your company to get the credit. If you don't want to, that's OK. :)) When you log in, you will be required to fill in your profile. Then you can start the trial.
2. Join a translation team List all languages by clicking "Languages" on the top. Click your language, you will go to that language page. On the right of the language name, there is a button "^..." which means "more actions". Click on the button and select "Request to Join Team". Then wait for your request to be approved. When it is approved, you will get the email notification.
3. Manage your team member if you are a coordinator If you are assigned a coordinator role, you will be able to see "Add Team Members" in the language page after clicking "^..." (more actions). You can only search users by user id. You can assign a member different roles (translator, reviewer, coordinator)
4. Translate After you have a language team, list the projects by clicking "Projects" on the top. Select a project, select a version, then you can translate.
5. Feedback We hope to get your feedback to the Zanata trial. If you find any resources/translations missed, which is in Transifex but not in Zanata, please let us know. If you find any bugs, please let us know. If you don't know how to operate, please let us know. We use https://etherpad.openstack.org/p/zanata-feedback to track the feedback.
Reference link: Documentation for Zanata can be found here: http://docs.zanata.org/en/release/ Specifically for translators: http://docs.zanata.org/en/release/user-guide/translator-guide/
Note: 1. This is only a trial. All the projects, teams, and translations will not be preserved. This test instance will be wrapped off when the trail is done. Then infra team will create a formal website. You will be notified when we officially move to Zanata. Now if you want to translate, please still use Transifex for your primary translations work. Your registration to OpenStack ID will be preserved for ever. When we officially move to Zanata, you don't need to register again. But we need to create the language team once more.
2. Anyone can create projects, for the sake of this demonstration please don't create your own
Thanks!
Best regards Ying Chun Guo (Daisy)
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <mailto: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
-- 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wednesday 15 July 2015, 08:27:29 Andreas Jaeger <aj@suse.com> wrote (shortened):
On 07/15/2015 06:19 AM, Akihiro Motoki wrote:
* There is no translation memories. Are some translation memories migrated from Transifex?
What do you mean exactly? Did Steve not migrate all translated strings or do you miss the separate translation memory?
It doesn't look to me as if anything was imported, I actually don't find any translated strings besides the one you and me have done so far for the German language. Is that on purpose? -- Regards, Robert
From: Robert Simai <robert.simai@suse.com> To: openstack-i18n@lists.openstack.org Date: 2015/07/15 18:12 Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register and
I have the same observation. In openstack-manuals, I can only see the progress of a few language teams. The number of language teams which has progress in translation is obviously less than the number in Transifex. I want to understand if all the translations are moved into Zanata. Best regards Ying Chun Guo (Daisy) Robert Simai <robert.simai@suse.com> wrote on 2015/07/15 18:11:16: try.
On Wednesday 15 July 2015, 08:27:29 Andreas Jaeger <aj@suse.com> wrote (shortened):
On 07/15/2015 06:19 AM, Akihiro Motoki wrote:
* There is no translation memories. Are some translation memories migrated from Transifex?
What do you mean exactly? Did Steve not migrate all translated strings or do you miss the separate translation memory?
It doesn't look to me as if anything was imported, I actually don't find
any
translated strings besides the one you and me have done so far for the German language. Is that on purpose?
-- Regards, Robert
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 07/16/2015 10:47 AM, Ying Chun Guo wrote:
I have the same observation. In openstack-manuals, I can only see the progress of a few language teams. The number of language teams which has progress in translation is obviously less than the number in Transifex. I want to understand if all the translations are moved into Zanata.
Indeed, not all translated files have been imported. This was not the point of the current evaluation, Andreas
Best regards Ying Chun Guo (Daisy)
Robert Simai <robert.simai@suse.com> wrote on 2015/07/15 18:11:16:
From: Robert Simai <robert.simai@suse.com> To: openstack-i18n@lists.openstack.org Date: 2015/07/15 18:12 Subject: Re: [Openstack-i18n] Zanata trial starts ! Please register and try.
On Wednesday 15 July 2015, 08:27:29 Andreas Jaeger <aj@suse.com> wrote (shortened):
On 07/15/2015 06:19 AM, Akihiro Motoki wrote:
* There is no translation memories. Are some translation memories migrated from Transifex?
What do you mean exactly? Did Steve not migrate all translated strings or do you miss the separate translation memory?
It doesn't look to me as if anything was imported, I actually don't find any translated strings besides the one you and me have done so far for the German language. Is that on purpose?
-- Regards, Robert
_______________________________________________ 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
-- 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, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (8)
-
Akihiro Motoki
-
Alex Eng
-
Andreas Jaeger
-
Elizabeth K. Joseph
-
KATO Tomoyuki
-
Robert Simai
-
Steve Kowalik
-
Ying Chun Guo