Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

please migrate to the new Fedora translation platform #31

Closed
Jibec opened this issue Jan 1, 2020 · 5 comments
Closed

please migrate to the new Fedora translation platform #31

Jibec opened this issue Jan 1, 2020 · 5 comments

Comments

@Jibec
Copy link
Contributor

Jibec commented Jan 1, 2020

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

@Jibec
Copy link
Contributor Author

Jibec commented Feb 2, 2020

hi, to make this happen:

  • pull latest translation from Zanata (zanata pull) and lock the project
  • make sure all po files have at least one string translated (some project did create empty translations fles with zanata cli)
  • commit your pot file in you repo (you'll have to change your makefile)
  • connect once to https://translate.fedoraproject.org/ and give me your username

then, I'll do project creation, first configuration and set you admin

weblate will automatically update po files when you update the pot file
weblate can also update your LINGUAS file each time a language is added
please let me know if you want some help

@mchehab
Copy link
Collaborator

mchehab commented Feb 4, 2020 via email

@Jibec
Copy link
Contributor Author

Jibec commented Feb 4, 2020

thanks, first configuration is done: https://translate.fedoraproject.org/projects/camorama/
mchehab is admin

weblate will open a pull request three days after first translator contribution (earlier if a language reach 100%)
weblate will squash commit to limit the number of translations commits

please add the pot file in the repository, so Weblate can harmonize language files and allow contributors to add new languages

I don't know why, but Weblate doesn't detect your LINGUAS file, I feel like this is related to the fact the pot file isn't part of the repository

@Jibec
Copy link
Contributor Author

Jibec commented Feb 4, 2020

do you know what these files are used for? en@quot.header and en@boldquot.header

@mchehab
Copy link
Collaborator

mchehab commented Feb 8, 2020

do you know what these files are used for? en@quot.header and en@boldquot.header

No idea. I'm almost sure those were added when we upgraded to use latest gettext.

As everything there seems to be commented, perhaps they could simply be removed.

@mchehab mchehab closed this as completed Mar 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants