- OpenStack-I18n - lists.openstack.org

[i18n] Summary of 2026.2 Hibiscus PTG Discussions
by Ian Y. Choi 24 Apr '26

24 Apr '26

Hello all, I would like to share a summary of the recent discussions held during the 2026.2 Hibiscus virtual PTG regarding the i18n SIG. We focused on advancing the Weblate migration through Zuul job testing and language configuration challenges, alongside updates on AI-assisted translation pipelines from the KNU team. Special thanks to all attendees including the contributors, OpenDev infra team, and KNU students for their contributions. Please refer to the full details from our Etherpad: https://etherpad.opendev.org/p/apr2026-ptg-i18n 1. Zuul Job Development for Weblate Migration We reviewed progress on testing Zuul jobs for Weblate integration using scripts upstream_translation_update_weblate.sh and propose_translation_update_weblate.sh. - Current Status: Scripts verified locally and now under Zuul testing with Contributor Guide and Horizon projects; test environment built via [1]. - Next Steps: Virtual sprint proposed for Zuul implementation around June 3 (14-16 UTC), with infra team availability confirmed [2]. 2. Language Migration from Zanata to Weblate Discussions centered on applying Zanata language settings to Weblate and handling discrepancies. - Progress: Python script for settings application (Gerrit #961371) [3]; following OpenInfra Korea Forum process [4]. - Challenges: Need scripts for zanata.json and zanata-plural.json recreation; plural mismatches in languages like as, bn_IN, gu, kn, pt, ru, tr_TR. - Tasks: Develop JSON generation scripts and decide plural handling strategy. 3. KNU Team AI Translation Pipeline Wrap-up KNU students shared their PoC for AI-based draft translations on new POT entries. - Accomplishments: Ansible role (prepare-ai-translation) with 4-step CI pipeline using Ollama; supports 44 languages, preserves human translations, integrates OpenStack glossary. - Repo: [5]. - Remaining: Zuul feasibility for Ollama (consider llama.cpp); not yet tested in Zuul. 4. Additional Topics - Future of Zanata infra (Docker with JVM?); OpenStack-Helm translation support; 14 open reviews in openstack/i18n [6]. - Proposals: Testing infra guidelines, I18n contributor guidelines; learn from Kubernetes SIG Docs L10n [7]; LLM on Zuul feasibility. Thank you, /Ian [1] https://github.com/ppiyakk2/zuul-i18n-config [2] https://wiki.openstack.org/wiki/VirtualSprints [3] https://review.opendev.org/c/openstack/i18n/+/961371 [4] https://forum.openinfra-kr.org/t/openstack-weblate-migration-language-migra… [5] https://github.com/openstack-kr/knu_i18n_2025 [6] https://review.opendev.org/c/openstack/i18n/+/981694 [7] https://mentorship.lfx.linuxfoundation.org/project/c71fdb2a-8e77-447d-ae8b-…

1 0

[i18n][Weblate] Current Migration Status Wiki Page with Access Review
by Ian Y. Choi 28 Jan '26

28 Jan '26

Hello all, As many of you know, the i18n SIG has been working on the migration from Zanata to Weblate with contributions from Seongsoo and many community members, including tooling and process work as documented on our migration wiki page. - https://wiki.openstack.org/wiki/I18nTeam/Migration-to-weblate This has been an important and ongoing effort for our translation workflow with open communication. Following recent discussions regarding Weblate configuration [1], it has come to my attention that some administrative actions were taken privately, without visibility to other reviewers or co-admins. While the intent was operational alignment, this does not fully align with our open principles. To ensure proper management of administrative access and to re-establish transparency to move forward, I plan to take the following actions: 1. Revoke all existing Weblate administrator privileges so we can review and reassign them in a transparent and collaborative manner. 2. Conduct a full review of Weblate permissions considering roles such as translators, reviewers, language coordinators, core reviewers, infra team, supporters, and Weblate staffs to ensure balanced visibility, accountability, and continuity across ongoing i18n activities. Note that this is aligning with recent security-driven activities and infrastructure-related changes relevant to our environment [2]. I appreciate the community’s understanding and the continued efforts toward a successful and stable completion of the Weblate migration. I welcome feedback from the community and will share the updated access plan once the review is completed. /Ian [1] https://lists.openstack.org/archives/list/openstack-i18n@lists.openstack.or… [2] https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/…

1 0

Fwd: [OpenStack Weblate] Unexpected restoration of all language sets after manual cleanup and reconfiguration [Ticket#2012540]
by Seongsoo Cho 28 Jan '26

28 Jan '26

Hi i18n Team, During the October 2025 PTG, there was a discussion about synchronizing language settings between Weblate and Zanata, and a proposal was made to turn off Weblate’s automatic language synchronization in order to align with the languages configured in Zanata. [1] Following that discussion, on January 27, 2026, I sent a request to the Weblate team asking them to disable this automatic language update feature. To share this context, I am forwarding the full email content here. Please note that the initial inquiry was submitted through the Weblate website’s help desk, so that initial message does not appear in the forwarded email chain. Additionally, as Ian Y. Choi pointed out on the i18n IRC channel[2], the communication with the Weblate staff was handled privately. I would like to apologize to the entire community for not fully aligning with our open communication practices. Going forward, I will ensure that all related discussions follow the OpenStack Community’s “4 Opens” principles. Thank you. Seongsoo Cho [1] https://etherpad.opendev.org/p/oct2025-ptg-i18n [2] https://meetings.opendev.org/irclogs/%23openstack-i18n/%23openstack-i18n.20… ---------- Forwarded message --------- From: Michal Čihař via Weblate Care <care(a)weblate.org> Date: Tue, Jan 27, 2026 at 10:15 PM Subject: RE: [OpenStack Weblate] Unexpected restoration of all language sets after manual cleanup and reconfiguration [Ticket#2012540] To: <ppiyakk2(a)printf.kr> Hello Seongsoo, I've just disabled the language definitions updates for your Weblate server. Best regards, Michal -- Weblate -- You can follow us on Mastodon! https://fosstodon.org/@weblate

1 0

Re: Issue with Zanata confirmation emails for new Persian translators
by Ian Y. Choi 08 Jan '26

08 Jan '26

Hi Hamid, It would be helpful if you could provide that user’s Zanata ID, name, and e-mail address so that further checks can be performed. (Note that I am copying to openstack-i18n mailing list for visibility - no need to share privacy information via public mailing list) Please note that our translate.openstack.org is based on Zanata, a deprecated open source project that is no longer actively maintained, so a complete resolution unfortunately cannot be guaranteed. Thank you very much for your understanding and for bringing this issue to our attention. Thank you, /Ian On Mon, Dec 29, 2025 at 1:55 PM Hamid Lotfi <hamid.lotfi(a)gmail.com> wrote: > > Dear Ian, > > I hope this email finds you well. > > I am writing to report an issue regarding the Persian (Farsi) translation team. Recently, we have noticed that new contributors attempting to join the team are facing a problem: they are not receiving the account confirmation emails from Zanata. > > This is preventing them from verifying their accounts and starting their translation work. > > Could you please investigate this issue or guide us on the necessary steps to resolve it? > > Thank you for your time and assistance. > > Best regards, > > Hamid Lotfi > >

3 3

Request to join Vietnamese translation team
by Vũ Đặng 12 Dec '25

12 Dec '25

Hello OpenStack I18n SIG team, My name is Vu Dang. I would like to contribute to the OpenStack Vietnamese translation team. My Gerrit ID is: vudn ( https://review.opendev.org/q/owner:dangngocvu4@gmail.com ) My GitHub account: dangngocvu4(a)gmail.com I plan to help translate Horizon dashboard, as well as documentation if needed. Please let me know if any additional steps are required to join. Thank you for your consideration. Best regards, Vu Dang

2 2

[i18n] Summary of 2026.1 Gazpacho PTG Discussions
by Seongsoo Cho 08 Nov '25

08 Nov '25

Hello all, I would like to share with you a summary of the recent discussions held during the 2026.1 Gazpacho virtual PTG regarding the i18n SIG. We had several productive sessions focused on our two main goals for the upcoming cycles: the Weblate Migration, and a forward-looking discussion on AI Translation. Special thanks to the OpenDev Infra Team for the infrastructure support, the OpenSource Contribution Academy mentees in Korea who worked on the Weblate migration, and the KNU students who brought great energy and ideas to our AI discussion. Please refer to the full details from our Etherpad: https://etherpad.opendev.org/p/oct2025-ptg-i18n 1. Weblate Migration Status & Challenges A significant portion of our PTG was dedicated to the ongoing migration from Zanata to Weblate. - Migration Status: DaGyeong Kim presented the current status. 15 dashboard projects were initially migrated, but we identified issues that require a retry. A detailed status page is tracking all projects [1]. - Tooling Development: We are actively developing and refining automation scripts to manage the migration, including language creation/deletion and handling plural forms (patches [2], [3]). This work is being tracked in a blueprint [4]. - Key Challenge - Language Definitions: We are addressing mismatches between Zanata's language codes (e.g., ko_KR) and Weblate's CLDR standards (e.g., ko), especially concerning plural form definitions. - Verification of Migration Completion: It was discussed that a clear method needs to be defined to verify whether all translated PO files in Zanata have been successfully migrated to Weblate. In subsequent discussions, it was agreed to establish specific criteria for accurate verification and to proceed with the work based on those criteria. 2. Zuul Integration & Infrastructure The second major topic was integrating our new Weblate instance with the OpenDev (Zuul) CI/CD pipeline. - Core Patches: We reviewed the main patches for openstack-zuul-jobs [5] and project-config [6] that will enable Weblate to propose translation updates. - New Zuul Job Testing Strategy: It was discussed to create a completely new job to minimize the impact and to apply it to specific projects first, gradually expanding its scope over time. 3. AI Translation PoC We held an exciting session with students from Kyungpook National University (KNU) to discuss a Proof-of-Concept (PoC) for using AI in our translation workflow. - Goals: The discussion focused on two potential tools: - An automated, CPU-based LLM tool (e.g., using Ollama) to catch new strings from merged patches and provide initial translations. - A local AI-assisted tool for translators to help with the initial translation of large .po files. - Next Steps: We are exploring different instance flavors for performance and comparing the pros/cons of self-hosting a model versus using external APIs (similar to the Firefox translation model). 4. I18n Repository Packaging We are working to package the openstack i18n repository [7] and publish an updated package to PyPI. This initiative aims to enhance productivity by independently managing the tools related to i18n. Best Regards Seongsoo Cho [1] https://wiki.openstack.org/wiki/I18nTeam/Migration-to-weblate#List_of_proje… [2] https://review.opendev.org/c/openstack/i18n/+/961371 [3] https://review.opendev.org/c/openstack/i18n/+/963758 [4] https://blueprints.launchpad.net/openstack-i18n/+spec/weblate-migration [5] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/921878 [6] https://review.opendev.org/c/openstack/project-config/+/961499 [7] https://review.opendev.org/c/openstack/i18n/+/955037

3 2

[i18n] Current Weblate Migration Status
by Seongsoo Cho 30 Sep '25

30 Sep '25

Hello i18n team, OpenStack's current translation platform(translation.openstack.org) is based on Zanata, which is no longer maintained. To ensure a sustainable translation workflow, the i18n team has been migrating from Zanata to Weblate. This work officially started following the CMU Summer semester mentoring shared by Kendall Nelson in May (link), and has since been moving forward in collaboration with the Korea User Group and mentees participating in the government-sponsored Open Source Contribution Academy program. 1. Migration progress Migration scope: - Download translated .po files from Zanata and upload them to Weblate - The same language set configured in Zanata is also applied in Weblate. Branches: - Currently, only the master branch is being migrated. - We are exploring ways to support stable branches in the future. Migration Contents: - At this stage, the migration targets strings inside source code and release notes. - We are in the process of expanding this to include documentation as well. We started with Horizon and its plugins, and the following projects have already been successfully migrated to Weblate: • cloudkitty-dashboard • designate-dashboard • freezer-web-ui • heat-dashboard • horizon • ironic-ui • magnum-ui • manila-ui • networking-bgpvpn • neutron-fwaas-dashboard • neutron-vpnaas-dashboard • octavia-dashboard • trove-dashboard • zaqar-ui • zun-ui 2. New Zuul jobs for Weblate To replicate the existing Zanata-based Zuul workflow, we are adding new Weblate jobs. • Patch: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/921878 We plan to reuse the translation-jobs-master-only Zuul templates and update the following playbooks to run both Zanata and Weblate tasks: • https://opendev.org/openstack/project-config/src/branch/master/playbooks/tr… • https://opendev.org/openstack/project-config/src/branch/master/playbooks/tr… • Patch: https://review.opendev.org/c/openstack/project-config/+/961499 3. Migration scripts Although they are one-off scripts, we are adding them to the i18n repository to document how we migrated from Zanata to Weblate. • Language sync tool: https://review.opendev.org/c/openstack/i18n/+/961371 • Zanata-to-Weblate migration tool: https://review.opendev.org/c/openstack/i18n/+/961075 4. Next steps for migration We have implemented everything needed to replace the Zanata-based jobs with Weblate. Once the Zuul job patches are merged, we will verify the upstream pipeline. Our goal is to migrate all projects from Zanata to Weblate by October. After verifying the pipeline, we plan to shut down Zanata. 5. Future plans Beyond this migration, we plan to expand translation targets — including OpenStack governance documents and the docs/ directories of many projects — to provide broader translation opportunities. Anyone interested in contributing is warmly welcome to join us in the #openstack-i18n IRC channel and say hello! Thanks, Best Regards Seongsoo Cho -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

2 3

[i18n] Sharing CMU Students’ Contributions: Progress on Zanata-to-Weblate Migration
by Ian Y. Choi 28 Jul '25

28 Jul '25

Dear OpenStack Community, Over the past six weeks, Seongsoo and I had the privilege of mentoring a group of four students from Carnegie Mellon University (CMU) [1] as part of our ongoing effort to migrate the OpenStack Internationalization (I18n) platform from Zanata to Weblate. I would like to take this opportunity to highlight the significant and meaningful contributions made by three students, Furqan Saeed, Simon Yu, and Jana Hussien, who recently completed video demos showcasing their work [2] [3]. Project Context As many may know, the I18n SIG has been working to modernize our translation infrastructure by transitioning from Zanata (now unmaintained) to Weblate — an actively developed, open source platform. This project not only ensures the sustainability of our translations, but also offers a valuable learning path for new contributors. Below are the key outcomes achieved by Furqan, Simon and Jana: 1. i18n tools script test codes for Weblate (by Furqan Saeed & Simon Yu) Furqan and Simon focused on bringing robust, production-quality unit testing to the collection of Python scripts and tools responsible for Weblate integration. Furqan’s video [2] demonstrates these efforts. Together, they: Developed a comprehensive suite of ~34 unit tests covering the main Weblate tool files. Used Python’s unittest and mocking strategies to ensure functions behave as expected, even simulating server responses. Noted and addressed gaps in requirements, such as missing library dependencies. Provided clear documentation (README.rst) explaining test infrastructure and file structure. Gained and demonstrated familiarity with OpenStack’s development guidelines, Gerrit workflows, and CI requirements. Their efforts establish a much needed test baseline for future improvements and bring our I18n tooling closer to OpenStack’s best practices. This contribution not only enhances software reliability but also creates a safer, more efficient environment for future contributors. 2. Migration of Zuul infrastructure scripts to Weblate (by Jana Hussien) Jana concentrated on migrating and refactoring the automation scripts that enable daily translation updates in Zuul, shifting from Zanata to Weblate. Her work involved: Analyzing and translating the logic in current scripts to ensure seamless migration, including first-time migration routines for new projects. Developing new scripts to automate creation of Weblate components and upload of translation templates (POT) and PO files; handling language code transformations between platforms. Troubleshooting integration challenges between Weblate’s API/CLI and OpenStack workflows, identifying and overcoming tricky configuration issues related to version control structure. Successfully demonstrating the migration workflow for projects such as trove-dashboard and horizon, with detailed documentation of results. Improving operational resilience by implementing enhanced error handling and summary reporting in the scripts. Discovering and addressing several issues during live testing, and documenting workarounds and plans for future improvements. Jana has also outlined next steps, including integrating these scripts further into the Zuul pipeline, modularizing code, and enhancing public documentation. These contributions represent valuable progress toward a full, sustainable migration to Weblate - benefiting the entire OpenStack community by advancing our translation workflows and broadening global accessibility. On behalf of all mentors (myself, Seongsoo Cho, Goutham Pacha Ravi), I’d like to thank Furqan, Simon, and Jana for their hard work, dedication, and collaborative spirit, and encourage other students and new contributors to get involved. If anyone would like to review their code, documentation, or get involved in this effort, please feel free to reach out or interact directly with their contributions [6-9]! Best regards, Ian Y. Choi (ianychoi) & Seongsoo Cho (seongsoocho) OpenStack I18n SIG & Student Mentors [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] Video - OpenStack I18n Zanata-to-Weblate Migration: Weblate Tools Unit Test Development (CMU Project Demo) (Furqan), link: https://youtu.be/w966IpBCqeE [3] Video - OpenStack I18n Zanata-to-Weblate Migration: Translation Scripts working on Zuul (CMU Project Demo) (Jana), link: https://youtu.be/RcQweOe-vfo [4] Photo of our kick off meeting: https://photos.app.goo.gl/QhNwBusFZjwvTBzi7 [5] Photos of our final mentoring meeting: Final Mentoring Meeting - https://1drv.ms/f/c/6cc85a64cb418204/EljY3AfrnypGrF6EyDZq83MBDZpLTPt-8VPymj… [6] https://review.opendev.org/c/openstack/i18n/+/953745 (by Furqan, review is welcome) [7] https://review.opendev.org/c/openstack/i18n/+/955982 (by Simon, review is welcome) [8] https://review.opendev.org/c/openstack/i18n/+/955439 (by Jana, working in progress) [9] https://review.opendev.org/c/openstack/trove-dashboard/+/952787 (by Jana, merged)

1 0

Re: [i18n][infra][horizon] Zanata translation job failures after Python 3.8 deprecation
by Ian Y. Choi 09 Jul '25

09 Jul '25

(+openstack-i18n mailing list) Hi all, I’d like to provide a brief update regarding the translation sync issue on Horizon and its plugins. It appears that the problem has been resolved through the patch at https://review.opendev.org/c/openstack/project-config/+/954370. Fortunately, Java 8 seems to be supported on Ubuntu Noble, which helped address the compatibility concerns. Separately, the progress of the Weblate migration is currently being accelerated through the mentoring program. For more details, you can refer to the ongoing updates at https://etherpad.opendev.org/p/2025-July-I18n-Weblate-Migration-Progress . Thank you to everyone who continues to support I18n efforts. /Ian On Sun, Jan 19, 2025 at 11:33 PM Ian Y. Choi <ianyrchoi(a)gmail.com> wrote: > > Thank you for sharing the current situation accurately and providing > suggestions regarding the translation sync issues. > > Due to continuous requests for translation updates while Horizon > updates were pending, I took the initiative to execute the translation > infrastructure sync script locally. > > Following your suggestions, I successfully ran the sync in a local > container environment and uploaded the proposal patch [1]. Detail > commands are pasted as [2]. > > Given that the Weblate migration is still in progress [3], I believe > it would be beneficial to discuss how we can potentially incorporate > the approach into the current infrastructure sync process in future > discussions. > > I understand this is a temporary solution while we work towards > completing the Weblate migration. > > The container-based approach has proven effective for our immediate > needs, and I appreciate your guidance on this matter. > > Thank you, > > /Ian > > [1] https://review.opendev.org/c/openstack/horizon/+/939607 > [2] https://paste.opendev.org/show/b6v9BODjraT8Heie2xW4/ > [3] https://meetings.opendev.org/meetings/openstack_i18n_meeting/2025/ > > On Wed, Oct 30, 2024 at 8:36 AM Clark Boylan <cboylan(a)sapwetik.org> wrote: > > > > On Tue, Oct 29, 2024, at 2:48 PM, Ian Y. Choi wrote: > > > Hi all, > > > > > > During last week's PTG, the I18n SIG identified Zanata translation job > > > failures for Horizon (and likely related plugins). The root cause > > > appears to be Python 3.8 deprecation on Horizon [1]. > > > > > > Failed jobs have been observed on Zuul [2], and translation proposals > > > were made on Gerrit [3]. > > > > > > Since translation sync on Horizon stable branches is functioning > > > correctly, the error message seems to be related to Python 3.8 > > > deprecation: > > > ERROR: Cannot install -r doc/requirements.txt (line 3) due to > > > conflicting package version dependencies. > > > > > > To address this, I'd like to raise two points: > > > > > > 1/ To resolve the issue, would you support updating translation sync > > > jobs with Bionic-based Zuul jobs by either upgrading to Jammy or > > > modifying the Bionic image to support Python >3.8? > > > > The problem with updating the translation sync jobs to Jammy or newer is that the Zanata client requires Java 8 which isn't available on those newer platforms. We can either satisfy the Python requirements or the Java requirements but not both at the same time with extra work. As has been mentioned elsewhere, completing the migration to Weblate removes the need for Zanata client and we can move on from this old platform. > > > > Some ideas on how we might workaround this issue while continuing to use Zanata include: running Zanata client from a container image with the right version of Java installed, or as you suggest installing a newer version of Python on Bionic. We could potentially use the `ensure-python` zuul-jobs role with `python_use_pyenv` set to true and `python_version` set to 3.11 or similar. That would build the newer python version from source on the older platform. We did this with Python 3.12 to get early tests running and it seemed to work. > > > > The problem with these approaches are that they too require work when we could instead focus on completing the Weblate migration. > > > > > > > > 2/ At least me from I18n SIG acknowledges that recognizing these > > > translation job errors was delayed. Moving forward, would it be > > > beneficial to implement periodic (e.g., monthly) reporting on > > > translation job successes and failures? > > > > > > > > > Thank you, > > > > > > /Ian > > > > > > [1] > > > https://docs.openstack.org/releasenotes/horizon/2024.2.html#upgrade-notes > > > [2] > > > https://zuul.opendev.org/t/openstack/builds?job_name=propose-translation-up… > > > [3] > > > https://review.opendev.org/q/owner:proposal-bot+project:openstack/horizon+b…

1 0

Updates on I18n SIG: Translation Sync Issues and Launchpad Bug Notifications
by Ian Y. Choi 21 May '25

21 May '25

Hi all, I’d like to share updates on two key I18n SIG topics: 1. Horizon translation sync issues The sync mechanism between Git project repositories and translation data on Zanata, based on old infrastructure, is causing some challenges for Horizon project [1]. Currently, I am handling the sync manually, as shown here [2]. While progress on the Weblate migration is slow, I hope this temporary solution helps for now. 2. Launchpad bug alarms on mailing list I apologize for the excessive Launchpad bug notifications on the mailing list. I discovered that modifying the I18n mailing list settings could prevent these alarms, and I have temporarily applied the changes. [Next Steps] Looking ahead, here are some proposed actions to improve the situation: a. Recent translation bug reports have been overly granular. Moving forward, I recommend managing translation bugs with a more project-wide approach. b. Many bug reports lack clarity regarding which projects they pertain to. I plan to mark such unclear reports as “Invalid.” c. I hope contributors will gain a better understanding of the overall translation process soon. d. I am exploring whether it’s possible to introduce bug submission templates or improve the guidelines for reporting translation bugs [3]. I will revert the mailing list settings after these improvements are in place. Thank you for your patience and understanding. Thank you all, /Ian [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://review.opendev.org/c/openstack/horizon/+/939607 [3] https://docs.openstack.org/i18n/latest/bug_report.html

2 1