#1013 please migrate to the new Fedora translation platform
Closed: Fixed 2 years ago by jibecfed. Opened 3 years 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 and gitlab hosted projects, Weblate open pull request. For other git hosting, 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

I opened a Pull Request to test the impact of Weblate on our websites with some questions: https://pagure.io/fedora-websites/pull-request/1014

I should be able to do most of the migration with some guidance of people with experience on how generation works.

#1014 was cancelled
#1015 applied the required change to move to zanata
#1016 is waiting for review

last step are:

  • fix the sync-po files with help of @misc (either remove it or adapt it)
  • add a cron to call the tools/l10N_update.sh every day or weeks.

So, I did remove the sync-pos target, but maybe it would have been better to just replace the target by a call to tools/l10N_update.sh ?

Hello, just noting this here: a new page was added to labs.fp.o for the Comp-neurofedora lab. The page contains the required bits for translation, but it seems to be missing from weblate completely.


We need the pot files to be refreshed, either manually by or automatically.

So, I did remove the sync-pos target, but maybe it would have been better to just replace the target by a call to tools/l10N_update.sh ?

I think l10N_update.sh requires to have commits rights on https://pagure.io/fedora-web/translations which probably isn't the case for most contributors.

I feel like a daily task calling l10N_update.sh would do the job.


Just checking if this is still an issue? I wanted to get the comp-neuro lab translations done before we get to the release days.



Sorry for another ping. Is this still an issue? We'd like to try to have the pages updated before the release this time.


I did not see these ping and manually updated sources a few days ago to prevent outdated content.
Thanks to misc, this PR may solve the issue "forever": https://pagure.io/fedora-websites/pull-request/1054

@ankursinha we may have a publication issue for labs (and maybe other)
When I go to: https://labs.fedoraproject.org/fr/comp-neuro/
I see a lot of English content.

Let's take a simple sentence: "Users and developers are also available"
is translated in French: https://pagure.io/fedora-web/translations/blob/master/f/labs.fedoraproject.org/fr.po#_755
which was translated two months ago already: https://pagure.io/fedora-web/translations/c/85f970d78425a9771090f9805deb19ae7ac7e170

which makes me think the po folder should not exist anymore in this repository.

and that build script should always use the content from websites/websites
I only touched the pot generation and never gave a look at content generation, as I was sure it was using pullpos

@misc : same question as the PR 1054: would you mind pointing where the syncpo is called and what the build script does exactly to publish our websites?

I do not know where it comes from. I found that while investigating who was using fedora.zanata.org, and seeing a IP from IAD 2 DC.

I suspect there is a host somewhere Fedora side who still run make syncpos, but I wasn't able to find where/how. I do not see anything in ansible repo, so it could come either from a openshift container, and/or a cronjob still in place that should have been removed (so removed from ansible, but still running).

Sorry @jibecfed @misc , I missed the notifications here too. It just popped up on my backlog to check on the status here.

Is there anything I can help with to ensure that the translations are correct for the F34 release?

I think we resolved everything with @darknao 's help, have a nice day!
please open new issues if require, and quote darknao and i in it, we'll be pleased to help

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

2 years ago

Login to comment on this ticket.