While most Fedora project migrated to Weblate, the old translation platform still exists and needs to be removed (the community shouldn't have to go to multiple place to contribute, and nobody assume Zanata maintenance).
- Targeted release: Fedora 33
- Last updated: 2020-06-18
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
We created a migration page to follow projects migration from Zanata to Weblate: L10N Move to Weblate.
Remaining projects should either: migrate to Weblate or move to another translation platform.
Weblate configuration: unless your team knows Weblate, Jibecfed will do first configuration and make you admin of your project so you can add more components.
Pull request support for Pagure: it is unlikely this features lands in Weblate before Zanata removal. Suggestion is to allow https://pagure.io/user/weblatebot for commits.
Some project requiring Sign-off: https://docs.weblate.org/en/latest/admin/licensing.html#signed-off-by
Reducing translation impact in your repository:
- you can configure weblate's components to save po files without any line number, saving many useless commits if you do frequent pot updates
- you can configure weblate's components to squash commits per author to limit the number of commits
Benefit to Fedora
This makes the distribution more efficient:
- translators have one single place for translating, and get many interesting features (alerts, comments, etc.)
- newcomers can directly translate without approval
- maintainer have less automation to do (po updates, etc.)
- reduce complexity (all in one place) & infrastructure costs
- Proposal owners: continue to answer questions from upstream projects and translators
- Other developers:
- if we created a ticket for you, answer it. It may require you to change your l10n/i18n automation (likely) and git repositories (unlikely).
- if not, open a ticket to l10n team: https://pagure.io/fedora-l10n/tickets
- Release engineering: #9537
- Policies and guidelines: No
- Trademark approval: No
This impact upstream projects, not the delivered operating system. Worse case scenario: less translations reach upstream.
How To Test
This improve the experience of users that don't speak English correctly (90% of the world, source CLDR + Wikipedia) or not at all (80% of the world, source CLDR + Wikipedia)
None (this doesn't impact packaging)
- Contingency mechanism: (What to do? Who will do it?) No contingency, Zanata won't be kept any longer, we already gave 6 more month to let project migrate at their own pace to the new system
- Contingency deadline: none
- Blocks release? No
- Blocks product? No
- How to translate on Weblate?
- List of Weblate file formats support: https://docs.weblate.org/en/latest/formats.html
- Weblate's FAQ: https://docs.weblate.org/en/latest/faq.html
- Weblate evolves fast, reading changes is interesting: https://docs.weblate.org/en/latest/changes.html