Hello, the Fedora project migrates its translation platform to Weblate [1]. This tool directly interact with your git repository, and requires us to know: * [mandatory] which branch is your development branch? * [mandatory] have you merged latest translation from Zanata and locked the project? * [info] Weblate will handle updates when pot file changes, don't edit po files for this [2] * [optional] what is the license of translation? (please use a code from https://spdx.org/licenses/) * [optional] do you have any announcement/warning you would like to display to the translators? (it will be displayed in Weblate) * [optional] do you need us to activate any specific checks? (this is a setting per component [3]) * [optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page) Please note: * For github and gitlab hosted projects, Weblate open pull request. For other git hosting, you'll have to add a key to allow commits. * In Weblate's vocable, one project is a group of component. Each component is a translation file. You can have many projects or many components or both. * You can change your mind over time, just reach trans.org [1] https://communityblog.fedoraproject.org/fedora-localization-platform-migrates-to-weblate/ [2] https://docs.weblate.org/en/latest/admin/continuous.html#avoiding-merge-conflicts [3] https://docs.weblate.org/en/latest/user/checks.html#translation-checks
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Be carefull, Zanata will be removed in a few weeks now: https://bugzilla.redhat.com/show_bug.cgi?id=1854445
I don't recall why gfs2-utils was included in the Fedora group of translation projects, but there are some fundamental issues that need to be addressed with the upstream project before it can be properly translated. In fact it was premature for a translation project to be created for it at all, so I intend to let the translation project get removed with Zanata, and we'll figure out the best solution for the upstream project once it is in a better shape. We've never actually shipped translations (due to the aforementioned issues) so this will not carry any impact.
I understand, thanks for your feedback Andrew. please open a request here if upstream wants to join: https://pagure.io/fedora-l10n/tickets