#1 please migrate to the new Fedora translation platform
Closed 2 months ago by jibecfed. Opened 10 months ago by jibecfed.

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


Sorry for not getting this back to you soon.

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?

master

  • [mandatory] have you merged latest translation from Zanata and locked the project?

Yes

  • [info] Weblate will handle updates when pot file changes, don't edit po files for this [2]

How does Weblate handle a trivial change in a source code? which causes fuzzy flag sometimes and we do run make -C po updates-po to avoid that situation? that enforces po modification here. do they do that if I simply upload the updated POT file?

Same as the source code. I mean GPLv2+

  • [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])

No idea. is it possible to change something later?

  • [optional] do you need us to automatically detect new translation files? (typical usecase: website translation with one translation file per page)

No.

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

How does Weblate handle a trivial change in a source code? which causes fuzzy flag sometimes and we do run make -C po updates-po to avoid that situation? that enforces po modification here. do they do that if I simply upload the updated POT file?

Weblate does mark as fuzzy changed string and does it well. I don't know what may be a trivial change in a pot file, as even a space can have to be translated differently.

As you are using Pagure, would you like to make @weblatebot part of your project with commit rights (this is my suggestion) or would you like to manually pull changes from Weblate git url?

How does Weblate handle a trivial change in a source code? which causes fuzzy flag sometimes and we do run make -C po updates-po to avoid that situation? that enforces po modification here. do they do that if I simply upload the updated POT file?

Weblate does mark as fuzzy changed string and does it well. I don't know what may be a trivial change in a pot file, as even a space can have to be translated differently.

For instance, all the translations should be marked as fuzzy if a line number is changed like inserting/removing a line around it. and the fuzzy translations won't be used in applications as you may know. anyway, if the translators are responsible to check and recover the state, that's fine.

As you are using Pagure, would you like to make @weblatebot part of your project with commit rights (this is my suggestion) or would you like to manually pull changes from Weblate git url?

Aha. let me add @weblatebot to my project then. thanks.

As you are using Pagure, would you like to make @weblatebot part of your project with commit rights (this is my suggestion) or would you like to manually pull changes from Weblate git url?

Aha. let me add @weblatebot to my project then. thanks.

Done.

Last step, in Pagure, go in Settings > Project Options, and set Web-hooks as https://translate.fedoraproject.org/hooks/pagure/ and click the update button

It will allow Weblate to be informed each time something happen in your repository.
If you wish to limit the number of commits, I can configure Weblate to rewrite his own commit with git squash. It means weblate will have to force-push.

Last step, in Pagure, go in Settings > Project Options, and set Web-hooks as https://translate.fedoraproject.org/hooks/pagure/ and click the update button

Added.

It will allow Weblate to be informed each time something happen in your repository.
If you wish to limit the number of commits, I can configure Weblate to rewrite his own commit with git squash. It means weblate will have to force-push.

No. I don't mind about the number of commits.

It looks like many of your translations files are empty, could you please remove all empty file?
to detect them, you may use pocount from translate toolkit or go into weblate.

I did the configuration and added you as admin.
https://translate.fedoraproject.org/projects/im-chooser/master/
Please remember not to update po files and let Weblate do it for you (benefit: it notifies translators new translations are available).

Have a nice day,

Metadata Update from @jibecfed:
- Issue status updated to: Closed (was: Open)

2 months ago

Okay, removed all the empty translations files from git. thanks for the help!

Login to comment on this ticket.

Metadata