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 hosted projects, Weblate open pull request. For other project, 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.
Repository for libdnf has been created: https://github.com/rpm-software-management/libdnf-l10n and weblate bot should have write access to it. For this repo we would need to set-up two branches - master and dnf-4-master (both of them with active development). Fedora packages will be created from dnf-4-master branch for a while.
configuration is done: https://translate.fedoraproject.org/projects/dnf/libdnf-master/ have a nice day