please migrate to the new Fedora translation platform

Create issue
Issue #4 new
Former user created an issue

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 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

Comments (3)

  1. Akira TAGOH repo owner

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

    [optional] what is the license of translation? (please use a code from https://spdx.org/licenses/))

    Same to the source code. LGPLv2+

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

    Not particularly so far.

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

    I guess not.

  2. j

    there is no pull request support for bitbucket.org see: https://github.com/WeblateOrg/weblate/issues/2344

    Two options:

    You’ll have to use this configuration: https://docs.weblate.org/en/latest/admin/continuous.html#automatically-receiving-changes-from-bitbucket

    but for now, nothing works, I can’t even clone your repository: “Could not fetch the repository: Warning: Permanently added the RSA host key for IP address '18.205.93.1' to the list of known hosts. git@bitbucket.org: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. (128)

    this page https://bitbucket.org/tagoh/imsettings/wiki/Home tells me “Please visit http://tagoh.bitbucket.org/imsettings/ for more details.” but the link doesn’t work.

    Why using bitbucket.org

  3. Log in to comment