- openSUSE Translation

phasing out desktop-file-translations
by Stanislav Brabec 05 Nov '24

05 Nov '24

Hi. I am working on a project of phasing out of desktop-file-translations: https://en.opensuse.org/openSUSE:Update-desktop-files_deprecation This project was started in 2003 to fulfill a goal of 100% translation of the desktop menu. Initially, Novell paid a substantial amount of money to complete this translation to supported languages. Later, the project was driven by the community. Increasing number of packages in the distribution made the project larger and larger. The project was extended to translate all desktop files in the product. Not only the desktop menu. So now we have a set of custom translations for all screensaver hacks, Amarok modules, stencils and templates for Calligra, names of KDE 4 and KDE 5 services, layout names for Umbrello 5 and much more. The implementation ignores the fact that many of included projects have their own translation projects, and duplicates the translation work. Or even worse, it forces the > 20 years old SUSE customizations over the recent upstream development. Nobody realized how big the project is in recent days. Now it includes about 20000 strings to translate. And translators have already translated about 380000 strings, which corresponds to about 20 human years of work. An unfortunate implementation following the "downstream only" way causes that we were not able to upstream these translations, return to the upstream nor drop this project any time later, as it would cause an unknown level of translation regression. In the later years, the "downstream only" was changed to "downstream first", but still, there was no way to return translations back to the upstream to save maintenance, translators' work, and as it is required by the recent "upstream first" policy. This starts to change in Factory. I made an improvement that changes the way it works, and suggests to upstream changes that it does. It would be a huge amount of work. Thousands of packages, thousands of upstreams. But as a result, we can start to use pure upstream packages, not only using the upstream code but also the upstream translations. There are first steps that will be done: 1. Projects are going to be locked in Weblate, and possibly also in GitHub. 2. Last translation updates will be sent to Factory. 3. New products will not get any new branch of update-desktop-files, and the desktop collection scripts will be never more called. Notes: - subprojects that are not phased out: - update-desktop-files-yast: We are the upstream here. And as YaST is slowly dying now, it does not make sense to spend a time on a more straightforward translation tool. - update-desktop-files-directories: Strings from the former Novell Linux Desktop 9 menu structure. Questionable. Is there any reasonable upstream for that? There is another large volume project: packages-i18n. It contains translations for all RPM packages in our products. There are more than 80000 strings to translate and I cannot imagine that it would be even 10% finished at any time in the future. Anyway, translators already spent more than 10 human years there. It makes sense to deprecate it as well, or at least use automated translation for it. Best regards -- Stanislav Brabec

2 1

Granting permissions to user opensuse-i18n on Github
by Ancor Gonzalez Sosa 17 Oct '24

17 Oct '24

Weblate submissions to the Agama Github project[1] are blocked because the user opensuse-i18n does not have permissions to commit there. We tried several times to grant those permissions but the process sticks at "Pending invite: awaiting opensuse-i18n’s response". Who can accept that invitation? Cheers. [1] https://github.com/agama-project/agama -- Ancor González Sosa YaST Team at SUSE Software Solutions

2 2

Leap 15.6 release notes / weblate is now fixed
by Lubos Kocman 12 Jun '24

12 Jun '24

Hello translation team! the .pot/.po files for 15.6 release notes were still referencing old versions.I've resolved any merge conflicts and then locally rebuilt .po/.pot files so they refer to 15.6 Would any of you be interested in co-ordinating/driving translations for new Leap releases? Including all the git/weblate-admin fun? Leap 16.0 is just behind the corner. :-) -- Best regards Luboš Kocman openSUSE Leap Release Manager

2 1

Exciting News - We've Upgraded and Migrated Weblate!
by Padraig Dillon 15 May '24

15 May '24

Dear Team, We are thrilled to announce that we have successfully migrated and upgraded our Weblate platform! This significant update brings a host of new features, improved performance, and enhanced security measures. Our team has worked hard to ensure a smooth transition and we're confident that this upgrade will provide an even better user experience for all of us. The new version of Weblate promises to deliver faster response times, a more intuitive user interface, and a more robust set of tools for our translation needs. We understand that change can sometimes be challenging, but we believe that this upgrade will greatly benefit our work and the services we provide to our users. We encourage everyone to explore the new platform and discover its enhanced capabilities. Should you have any questions or encounter any issues, please don't hesitate to reach out to our support team. We're here to help! Thank you for your continued support and cooperation during this transition. We're excited about this new chapter and look forward to seeing all the amazing work we'll accomplish with this upgraded Weblate platform! Best Regards, Padraig. Padraig Dillon SUSE Head of Localization LinkedIn <https://www.linkedin.com/company/suse/mycompany/> | Instagram <https://www.instagram.com/suseinc/?hl=en> | <https://twitter.com/SUSE>X <https://twitter.com/SUSE> | <https://twitter.com/SUSE> YouTube <https://www.youtube.com/channel/UCHTfqIzPKz4f_dri36lAQGA>

1 0

Weblate Outage
by Padraig Dillon 10 May '24

10 May '24

Planning Disruption for Weblate Migration The [openSUSE](https://www.opensuse.org/) will undergo a critical update with the migration of [Weblate](https://l10n.opensuse.org/) to a hosted solution. Shifting to a hosted solution for the web-based localization tool in order to keep up with the increasing demands of projects’ development. The migration is slated for May 14 and it is anticipated that the service will be down for approximately one day. This is a planned short-term inconvenience for a long-term benefit and will allow for our translation contributors to pick up right where they left off. People wanting to contribute to the openSUSE Project by helping to translate using [Weblate](https://weblate.org/en/) can register on https://l10n.opensuse.org and connect with other translators through translation(a)lists.opensuse.org and project(a)lists.opensuse.org mailing lists. Any attempt to connect to Weblate during the migration will trigger a notification informing the user of the ongoing maintenance. Others will be informed of the outage through https://status.opensuse.org.

1 0

Translations for openSUSE Leap 15.6 Release Announcement / Screenshots
by Douglas DeMaio 07 May '24

07 May '24

Hi everyone, I have placed the release announcement for openSUSE Leap 15.6 on the wiki at https://en.opensuse.org/Release_announcement_15.6 It would be highly appreciated if you could help to translate the release announcement to your native language to help propagate the news of our next release. Currently it is only in English. Feel free to link your translated version to the top and include your ISO 639-1 Code language code. If you have any questions, please let me know. It would be ideal to have this complete by June 4. Screenshots If you wold like to do screenshots, you can start the page at https://en.opensuse.org/Portal:15.6/Screenshots and add new screenshots. v/r Doug

1 0

Translations for openSUSE Leap 15.6 Release Announcement / Screenshots
by Douglas DeMaio 07 May '24

07 May '24

Hi everyone, I have placed the release announcement for openSUSE Leap 15.6 on the wiki at https://en.opensuse.org/Release_announcement_15.6 It would be highly appreciated if you could help to translate the release announcement to your native language to help propagate the news of our next release. Currently it is only in English. Feel free to link your translated version to the top and include your ISO 639-1 Code language code. If you have any questions, please let me know. It would be ideal to have this complete by June 4. Screenshots If you wold like to do screenshots, you can start the page at https://en.opensuse.org/Portal:15.6/Screenshots and add new screenshots. v/r Doug

1 0

FOSDEM 2024: Call for Participation - Translations Devroom 2024
by Paulo Henrique de Lima Santana 15 Nov '23

15 Nov '23

Hi all, Web version available here: https://gitlab.com/translations-devroom/cfp # FOSDEM 2024 In Person -- Translations DevRoom Call for Participation! FOSDEM 2024 [1] will take place on Saturday 3rd and Sunday 4th February 2024 in Brussels, Belgium. ## Key dates / New updates * Conference dates: 3-4 February, 2024 In person. * Translations DevRoom [2] date: Sunday 4th February (half a day in the morning). * Submission deadline: Sunday 10th December. * Announcement of selected talks: Friday 15th December. * You must be available in person to present your talk. * Talk submissions should be 30 mins and this should include Q&A time. ## TALK TOPICS For the second year in a row, FOSDEM will hold a devroom on all things related to translating FLOSS projects. * Recruiting new people to translate your project. * How it works in your project to translate softwares, websites, packages, manuals, tools, and so on. * Which tools are used by translators. * Exchange experiences between FLOSS projects. * Rewarding volunteer contributors and keeping volunteers motivated. * Showing which languages your project has been translated to. Again, these are just suggestions. We welcome proposals on any aspect of translations! ## HOW TO SUBMIT A TALK * Visit the FOSDEM 2024 pretalx [3] website. This has replaced Pentabarf! * Follow the instructions to create an account. * Once logged in, select “submit a CFP”. * Your submission must include the following information: - Proposal title - Track - Select **Translations** from the drop down list - Abstract - Description - Add any other details as needed to the Submission notes. - Additional speaker - _Click Continue or you can save and come back to it_ - About your proposal: Which open source license do you use? - FOSDEM is an open-source software conference, please specify which OSI approved license [4] your proposal uses. - Extra review material, only shown to reviewers (not published when scheduled) - Extra Contact details (optional) - _Click Continue or you can save and come back to it_ - Finally tell us your name - Biography - Availability If you need to get in touch with the organiser of the Translations DevRoom, email us at <translations-devroom-manager(a)fosdem.org> FOSDEM code of conduct [5]. Paulo Henrique de Lima Santana - Translations DevRoom Organiser [1] https://fosdem.org/2024 [2] https://fosdem.org/2024/schedule/track/translations [3] https://pretalx.fosdem.org/fosdem-2024/cfp [4] https://opensource.org/licenses [5] https://fosdem.org/2024/practical/conduct -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com.br GPG ID: 0443C450

1 0

A Heartfelt Thank You for the Resilience and Commitment of openSUSE Contributors
by Douglas DeMaio 18 Oct '23

18 Oct '23

Dear openSUSE Contributors, A few of us within the community want to extend our heartfelt thank you and appreciation for your dedicated community in ensuring the security and integrity of openSUSE's distributions, tools and communications channels. We want to acknowledge that swift and decisive measures to prevent malicious content from infiltrating the openSUSE ecosystem is of the upmost importance. As we unfortunately witnessed with Ubuntu recent release, some people will act with malicious intent and use hate speech. Our hearts go out to the Ubuntu community for the challenges they've faced. Stay strong, friends. Your commitment to maintaining a high standard is highly appreciated. openSUSE members have been actively guarding and protecting our community's image from threats, which is commendable. We realize that what happend to Ubuntu can happen to other distributions, and we should remain vigilant and dedication to safeguarding the user community. We encourage discussion about this topic and have a few key points we would like to emphisize below. Weblate open source: The open-source community relies on collaborative tools like Weblate to ensure translations and contributions are secure. We encourage contributions to this tool as it could help identify harmful content. Awareness: It's essential to spread awareness about the need for a content review and security checks in open-source projects. By doing so, we can make a proactive stance against any potential threats. Resilience: Building resilience in our open-source ecosystems is crucial. This resilience not only shields us from threats but also guarantees a safe and harassment-free environment. In a world where cybersecurity is of paramount importance, your actions not only prevent harm but also set an example for others in the open-source community. Thank you for keeping openSUSE a safe and reliable choice for all of us who depend on it. Sincerely, openSUSE Community Meeting - weeklymeeting20231017

2 1

Leap 15.5 retrospective feedback is now seeking action items
by Lubos Kocman 27 Jun '23

27 Jun '23

Hello openSUSE! I would like to share categorized openSUSE Leap 15.5 retrospective results with all contributors, team leads, and individuals who directly or indirectly contribute to openSUSE Leap! https://en.opensuse.org/Portal:15.5/Retrospective Feel free to review relevant sections for you or your team and see if you could help to address some of the issues. I already started making action items for the obvious ones, however, It would really help me if you'd share any suggestion or ideas. Feel free to link action items to the wiki, such as links to github issues, bugs, progress-o-o, trello, jira, code-o-o feature links. I promise that I'll try to help driving "reasonable ones" to the completion. I already agreed with the review round that Leap 15.6 retrospective will have explicit "written" suggestion in the "what didn't go too well" section to open a bug and reference it in the next. I'm aware that might take away the anonymity aspect of the survey, however, as it is now it's impossible to react to some of the feedback without an effective feedback loop such as discussion in bugzilla. Let's make Leap 15.6 even a better release than 15.5 Please be aware that I'll be on vacation for next two weeks starting by Thursday. Best regards Lubos Kocman openSUSE Leap Release Manager

1 0