- OpenStack-I18n - lists.openstack.org

[Bug 2008023] [NEW] Vue d'ensemble in Installation Guide
by Quentin 22 Feb '23

22 Feb '23

Public bug reported: Line "network" in tables. Link of network is write and not clickable in french version La ligne "réseaux" du tableau. Le lien est écris en plus d'être non cliquable dans la version française. ----------------------------------- Release: 0.1 on 2016-11-24 07:55 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/liberty/fr/install-guide-ubuntu/overview.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/2008023 Title: Vue d'ensemble in Installation Guide Status in openstack i18n: New Bug description: Line "network" in tables. Link of network is write and not clickable in french version La ligne "réseaux" du tableau. Le lien est écris en plus d'être non cliquable dans la version française. ----------------------------------- Release: 0.1 on 2016-11-24 07:55 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/liberty/fr/install-guide-ubuntu/overview.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/2008023/+subscriptions

1 0

Need help in making sense of a message in Heat
by Juliette Tux 16 Jan '23

16 Jan '23

Hello, Could anybody kindly elaborate on the meaning of a condition in a message: "The flag which represents condition of reserved resources of the lease. If it is true, the amount of reserved resources is less than the request or reserved resources were changed." The obscure part for me is "less than the request or reserved resources were changed." Context: heat/engine/resources/openstack/blazar/lease.py:233 TY! -- С уважением, Дронова Юлия

3 3

[skyline][i18n] Questions on more language translation support
by Ian Y. Choi 16 Jan '23

16 Jan '23

Hi Skyline team and I18n contributors, First, Skyline team, thank you for considering skyline with i18n! As Seongsoo started to talk via skyline IRC channel [1], I see that there are some needs for more language support for the Skyline project. Let me elaborate through the following questions as current I18n SIG lead: 1. Skyline team: While I believe you are welcome to contribute to other languages by adding per-language json files like [2], is it okay to contribute Korean language through Korea User Group members? Me and/or Seongsoo would like to happily step up as reviewers to guarantee sufficient language quality. 2. Any translation interests from other I18n language teams? Feel free to tell me or reply to this thread. 3. While number 1 would be a short-term approach to add Korean language support, to support more international languages, I want to suggest integrating with react-intl if skyline is using react (from my brief investigation, it is yes through [3]), since react-intl support to convert json <-> pot which functionality was previously used by tripleo-ui for i18n support [4]. Although I18n SIG is trying to migrate from Zanata to Weblate, a new translation platform [5], pot support would be essential for standardizing i18n and the translation process. With many thanks, /Ian [1] https://meetings.opendev.org/irclogs/%23openstack-skyline/%23openstack-skyl… [2] https://github.com/openstack/skyline-console/tree/master/src/locales [3] https://opendev.org/openstack/skyline-console/src/branch/master/package.jso… [4] https://opendev.org/openstack/tripleo-ui/src/commit/d1baef537f0746efceacfdd… [5] https://lists.openstack.org/pipermail/openstack-i18n/2022-October/003559.ht…

2 1

[Bug 1999519] Re: Typo in French translation concerning admin state
by Vishal Manchanda 14 Dec '22

14 Dec '22

This issue needs to be fixed in https://translate.openstack.org/ That's why marked it as invalid for the horizon. If you like to know more about the process of how translation happens, please refer https://docs.openstack.org/i18n/latest/ ** Project changed: horizon => openstack-i18n ** Also affects: horizon Importance: Undecided Status: New ** Changed in: horizon Status: New => Invalid -- 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/1999519 Title: Typo in French translation concerning admin state Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: New Bug description: In horizon we can read in the French translation: Etat administateur instead of Etat administrateur (a 'r' is missing). cf https://opendev.org/openstack/horizon/src/branch/master/openstack_dashboard… --- openstack_dashboard/locale/fr/LC_MESSAGES/django.po.ori 2022-12-13 14:02:08.865183595 +0100 +++ openstack_dashboard/locale/fr/LC_MESSAGES/django.po 2022-12-13 14:00:29.410016035 +0100 @@ -495,7 +495,7 @@ msgstr "Mot de Passe Administrateur" msgid "Admin State" -msgstr "État Administateur" +msgstr "État Administrateur" msgid "Admin State =" msgstr "État Admin =" To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1999519/+subscriptions

1 0

[Bug 1999519] [NEW] Typo in French translation concerning admin state
by Launchpad Bug Tracker 14 Dec '22

14 Dec '22

You have been subscribed to a public bug: In horizon we can read in the French translation: Etat administateur instead of Etat administrateur (a 'r' is missing). cf https://opendev.org/openstack/horizon/src/branch/master/openstack_dashboard… --- openstack_dashboard/locale/fr/LC_MESSAGES/django.po.ori 2022-12-13 14:02:08.865183595 +0100 +++ openstack_dashboard/locale/fr/LC_MESSAGES/django.po 2022-12-13 14:00:29.410016035 +0100 @@ -495,7 +495,7 @@ msgstr "Mot de Passe Administrateur" msgid "Admin State" -msgstr "État Administateur" +msgstr "État Administrateur" msgid "Admin State =" msgstr "État Admin =" ** Affects: openstack-i18n Importance: Undecided Status: New -- Typo in French translation concerning admin state https://bugs.launchpad.net/bugs/1999519 You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n.

1 0

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 05 Oct '22

05 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 05 Mar '22

05 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