#141 please migrate to the new Fedora translation platform
Opened 9 months ago by jibecfed. Modified a month ago

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@lists.fedoraproject.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


Metadata Update from @rcritten:
- Issue assigned to rcritten

9 months ago

So apparently there hasn't been a push to Zanata in almost three years (Feb 2017). A number of string changes have happened since then, I don't know if it would be better to pull the current updates or just drop them. Just glancing at the ~60k diff it looks like the vast majority of the changes are just line numbers so maybe it would be ok.

Similarly the pot file hasn't been updated since 2017 either.

@nalin you are the owner in Zanata, can you lock the project? I have a local copy of the current translations if I decide to go ahead and merge it.

optional:
license: GPLv3+
announcement/warning: none
specific checks: none for now, I assume I can enable in the future?
detect files?: No, this is already managed by POTFILES.in

Well, not a good news indeed=2E But that's life, this is an opportunity for us to improve

Anyway, you should delete every single po file with no translation Zanata had this bad habit to have empty translation files

It will lower a lot the size of the merge
You can use the 'pocount pofolder --csv'

Even if you don't update it now, Weblate will do a pot update of all po files, and you'll end up with a giant commit

Merged PR https://pagure.io/certmonger/pull-request/142 which dropped all empty translation files.

I'm not sure if answering the questions here is sufficient but here goes:

[mandatory] which branch is your development branch? master
[mandatory] have you merged latest translation from Zanata and locked the project? I'm abandoning Zanata so no merge. I'm not an admin of the project in Zanata and he is not responding so I can't lock it
[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/) GPL-3.0-or-later
[optional] do you have any announcement/warning you would like to display to the translators? (it will be displayed in Weblate) No
[optional] do you need us to activate any specific checks? (this is a setting per component [3]) None that I know of
[optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page) No

Login to comment on this ticket.

Metadata