- OpenStack-I18n - lists.openstack.org

Re: [OpenStack-I18n] [I18n] Zanata status + call for volunteers on Weblate migration
by Nikita Koselev 24 Oct '22

24 Oct '22

Hi, My name is Nikita Koselev: https://www.linkedin.com/in/nikitakoselev/ I was told by a friend that the OSS project you lead needs help: https://lists.openstack.org/pipermail/openstack-i18n/2022-October/003559.ht… I cannot commit that much to one project, but I can help you to find people. Would you like to give a talk to London Java Community about the project? 7 mins talk is easy to organize. If needed, we can organize 30 mins too. Also, we can have a call and find out how I could help the community of OpenStack. Have a really nice day, Kind regards, Nikita Koselev

1 0

[I18n] Zanata status + call for volunteers on Weblate migration
by Ian Y. Choi 04 Oct '22

04 Oct '22

Hi all, First, thank you all for contributing to OpenStack with globalization by contributing translations, coordinating translations with artifacts, and making sure that those translations are shipped with releases to all over the world (we are calling it I18n - Internationalization). While OpenStack I18n could be healthier with the tremendous help from translators as well as many OpenStack upstream contributors & teams such as infrastructure, release management, and documentation, the current translation platform we are using on https://translate.openstack.org relies on Zanata, an open-source translation platform which upstream activities were stopped [1]. Currently, there are several issues reported - most things have been resolved while it repeats / worses as time goes: - OpenID authentication issues for new registration users on translate.openstack.org [2] - Translation job failure issues since Zanata client did not work with a newer Java / job compatibility issues with Python versions [3] - Missing translation jobs for Xena/Yoga stable versions on Zanata [4] Considering the situation, to solve the root cause of the situation, I am calling for volunteers on Weblate migration. The detailed activities would continue from what the previous I18n PTL already investigated, identified, and documented to [5] [6]. There would be diverse work items with developer perspective as well as translators and operators. Hope that there are many volunteers to move forward. Meanwhile, I updated the "Translations & Priority" part on https://translate.openstack.org homepage. Note that stable versions are minimized to Horizon and dashboard projects, and ping me if there would be lots of translation work especially during R-3 to R-1. Looking forward to an enhanced open source translation platform landing soon with OpenInfra. With many thanks, /Ian [1] https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org… [2] https://lists.openstack.org/pipermail/openstack-i18n/2022-February/003550.h… [3] https://review.opendev.org/c/openstack/project-config/+/850962 [4] https://lists.openstack.org/pipermail/openstack-discuss/2021-December/02644… [5] https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation-pla… [6] https://etherpad.opendev.org/p/I18n-weblate-migration

2 1

[Bug 1975497] [NEW] openstacksdk 0.99.0 failure in compute.v2.server in Ansible
by Enrico Daglio 23 May '22

23 May '22

Public bug reported: When using Ansible with recent updates including openstacksdk 0.99.0 failures can be reproduced with Ansible, using the openstack.compute.v2.server.Server module in Playbooks. Issue appears when trying to launch new instances in an OpenStack environment. Detail message: n exception occurred during task execution. To see the full traceback, use -vvv. The error was: KeyError: 'volumes is not found. openstack.compute.v2.server.Server objects do not support setting arbitrary keys through the dict interface.' A role back to openstacksdk version 0.61 works as workaround. Some details: ansible [core 2.13.0] config file = /.../ansible.cfg configured module search path = ['/.../.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /.../.local/lib/python3.9/site-packages/ansible ansible collection location = /.../.ansible/collections:/usr/share/ansible/collections executable location = /usr/local/bin/ansible python version = 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] jinja version = 3.1.2 libyaml = True ** Affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1975497 Title: openstacksdk 0.99.0 failure in compute.v2.server in Ansible Status in openstack i18n: New Bug description: When using Ansible with recent updates including openstacksdk 0.99.0 failures can be reproduced with Ansible, using the openstack.compute.v2.server.Server module in Playbooks. Issue appears when trying to launch new instances in an OpenStack environment. Detail message: n exception occurred during task execution. To see the full traceback, use -vvv. The error was: KeyError: 'volumes is not found. openstack.compute.v2.server.Server objects do not support setting arbitrary keys through the dict interface.' A role back to openstacksdk version 0.61 works as workaround. Some details: ansible [core 2.13.0] config file = /.../ansible.cfg configured module search path = ['/.../.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /.../.local/lib/python3.9/site-packages/ansible ansible collection location = /.../.ansible/collections:/usr/share/ansible/collections executable location = /usr/local/bin/ansible python version = 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] jinja version = 3.1.2 libyaml = True To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1975497/+subscriptions

2 1

Re: [OpenStack-I18n] Updated OpenID provider for Zanata service
by Ian Y. Choi 04 Mar '22

04 Mar '22

What is your error message? Thanks, /Ian On Sat, Mar 5, 2022 at 3:39 PM Cloud Suhartono <cloudsuhartono(a)gmail.com> wrote: > Sorry, it doesn’t work for me > > On Sun, 27 Feb 2022 at 19.31 Ian Y. Choi <ianyrchoi(a)gmail.com> wrote: > >> Thank you @fungi! It works perfectly with me. >> >> >> Please don't hesitate to share via openstack-i18n(a)lists.openstack.org if >> new openinfraid does not work with your account. Thank you all, /Ian >> >> On 2/15/2022 1:07 AM, Jeremy Stanley wrote: >> > As part of the Open Infrastructure Foundation's move to replace >> > openstackid.org with a new id.openinfra.dev provider, I've switched >> > the configuration for the Zanata deployments on >> > translate.openstack.org and translate-dev.openstack.org, as well as >> > updating everyone's accounts in the database to expect the new >> > provider URL. I've tested my logins and they're still working, but >> > please don't hesitate to let me know if you see any account-related >> > problems you think may be a result of the change. Feel free to reply >> > here on the mailing list, or in private if you prefer. >> > >> > _______________________________________________ >> > OpenStack-I18n mailing list >> > OpenStack-I18n(a)lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

1 0

Updated OpenID provider for Zanata service
by Jeremy Stanley 27 Feb '22

27 Feb '22

As part of the Open Infrastructure Foundation's move to replace openstackid.org with a new id.openinfra.dev provider, I've switched the configuration for the Zanata deployments on translate.openstack.org and translate-dev.openstack.org, as well as updating everyone's accounts in the database to expect the new provider URL. I've tested my logins and they're still working, but please don't hesitate to let me know if you see any account-related problems you think may be a result of the change. Feel free to reply here on the mailing list, or in private if you prefer. -- Jeremy Stanley

2 1

[tc][sig][i18n] What's the status for Xena translation?
by Akihiro Motoki 23 Dec '21

23 Dec '21

Hi, # I include TC and SIG tags to get broader attractions to this topic. # Also Cc'ed to Ian (i18n SIG char) and Andreas. I would like to ask the status of Xena translation in translate.openstack.org (Zanata). In past releases, stable-XXX branches were created on Zanata, but a branch for Xena translation has not been created yet. Ajaeger usually prepared these branches as a volunteer (I am really appreciated) but AFAIK he no longer works on OpenStack actively. Who takes care of the translatio preparation around the release now? I hope the i18n SIG is not dead. Thanks, Akihiro Motoki (amotoki)

3 2

Different meanings of 'retrieve' in django from horizon-stable-wallaby?
by Juliette Tux 06 Sep '21

06 Sep '21

Hello, my name is Julie Dronova, I do Russian translations. I have a question regarding possible different meanings of the verb 'retrieve' in horizon's django. Firstly, we have these types of phrases: "Unable to retrieve image format list." "Unable to retrieve volume backup details." "Unable to retrieve hypervisor information." etc in which we have a clear indication of retrieving an information, data. And then we have these types of messages: Unable to retrieve volume backups. Unable to retrieve floating IP pools. Unable to retrieve availability zones. My question is: do these 2nd types of messages also mean 'retrieving of data, info' or do they mean something different? Since in Russian we would need to use two different verbs here. If this is a wrong type of mailing list to ask such questions, kindly direct me to more appropriate one (devs mailing list?). Thanks in advance. -- С уважением, Дронова Юлия

2 2

Hope to get response of request of joining zh-CN languages team
by 韩光宇 02 Sep '21

02 Sep '21

Hi, I'm a employee of Uniontech Software Technology Co., Ltd which has been signed CCLA. My department has been working on OpenStack, and we also want to contribute to OpenStack community now. We applied to join the zh-CN languages team a few weeks ago. I heard that I can remind the admin to process the application here, so I send this email, sorry to bother you. Two zanata account which applied join zh-CN language team in https://translate.openstack.org/ are: "hanguangyu(a)uniontech.com" and "wangleic(a)uniontch.com". Thank you very much. Han Guangyu.

2 1

[Bug 1935742] [NEW] The openstack-tox-docs job fails because of "LaTeX Error: File `tgtermes.sty' not found."
by Takashi Kajinami 21 Jul '21

21 Jul '21

Public bug reported: Currently the openstack-tox-docs job continuously fails because of the following error in sphinx build. ! LaTeX Error: File `tgtermes.sty' not found. An example can be found here. https://zuul.opendev.org/t/openstack/build/919c3ac7b0be438db69fe8d98340a960… ** Affects: openstack-i18n Importance: Undecided Assignee: Takashi Kajinami (kajinamit) Status: In Progress ** Changed in: openstack-i18n Assignee: (unassigned) => Takashi Kajinami (kajinamit) -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1935742 Title: The openstack-tox-docs job fails because of "LaTeX Error: File `tgtermes.sty' not found." Status in openstack i18n: In Progress Bug description: Currently the openstack-tox-docs job continuously fails because of the following error in sphinx build. ! LaTeX Error: File `tgtermes.sty' not found. An example can be found here. https://zuul.opendev.org/t/openstack/build/919c3ac7b0be438db69fe8d98340a960… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1935742/+subscriptions

2 1

[Bug 1929360] Re: Fix typo of "Instance ID" in Chinese
by Akihiro Motoki 24 May '21

24 May '21

A translation bug should be fixed in https://translate.openstack.org/. All translations are automatically imported, so there is nothing that the horizon team can do. ** Project changed: horizon => openstack-i18n -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1929360 Title: Fix typo of "Instance ID" in Chinese Status in openstack i18n: New Bug description: In Chinese, the 'Instance ID' should be "实例 ID", not '示例 ID'. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1929360/+subscriptions

1 0