Le 2020-01-20 04:37, Luděk Janda a écrit :
That’s just a small misunderstanding. We prefer to translate in our internal platform because this way we can share RHEL UI translation memory with other projects such as RHEL documentation, our translators working on docs can easily verify the appropriate UI strings translation when necessary. We can also leverage easier our past translations from other projects / other RHEL components.I do not have numbers for Weblate, but comparing Zanata with our internal platform - when sharing TM in our internal platform we are to reduce workload by ~20% (e.g. Cockpit in Korean, Zanata workload: 1107, Memsource workload: 802). We also have access to our MT engines (DeepL) that speed up delivery. Etc.
Thanks your answer.
What is unclear here: you say you are not using Zanata internally and then compare Zanata vs Weblate. Could you please elaborate? Which tool are you using internally and how is it related to fedora.zanata.org? Is there RHEL requirements for translate.stg.fedoraproject.org?
Yeah, it was surprisingly easy, thanks, Matej, for giving me that opportunity. Challenging part seems to be the GA check. I will need to align our internal QA tools to highlight the same errors as in Weblate.
Good to see it was easy. Why would you like to "highlight the same errors as in Weblate"? What can of tests does the RHEL internal QA tools runs on a release?
Because Cockpit and Composer already moved to weblate, we can definitely finish our translations there.
But in general I would really prefer to have RHEL 8.2 translation cycle finished first (18 February) and migrate after that.
Could we turn things around and see the situation as an opportunity? Since I joined Fedora in 2015, I never had an opportunity to contribute a RHEL release, and being able to see RHEL translators' work/feedback always were really limited.
Here, with your translation import for Cockpit in Weblate, I was able to see Red Hat contributions for the first time.
I would love to: 1. see all projects to migrate to translate.stg.fedoraproject.org 2. announce your schedule in Fedora blogs so community contribute to RHEL From past translations I did, I consider 95% of translation done for RHEL are the same strings that what we have in Fedora. 3. see RHEL work imported back into translate.stg.fedoraproject.org 4. work with you a retrospective of this collaboration so we can improve
To migrate a project to Weblate: * allow Weblate configuration: choose the git repository for Weblate that will handle pot and po files (it can be dedicated for translation or shared with source code) run `zanata pull` (using zanata python client) make sure there is no translation files with no translations (use pocount from translate-toolkit) from there, translation can start. load: about 30 minutes per project in your team and 10 minutes of configuration on my side * allow to package releases: change your make files load: a few hours for your teams to make sure all automation works well
We have much to learn from each other.
Jean-Baptiste