trans January 2020

trans@lists.fedoraproject.org

31 participants
32 discussions

Proposal: Fedora G11N Steering Committee
by Pravin Satpute 26 Jun '20

26 Jun '20

Hi All, I am sure, most of the people working with Fedora I18N, L10N from 5-6 year must be aware regarding Fedora L10N Steering Committee. [1] As far as i know this committee was active around 2009 and very effective. During Fedora G11N activity day discussions, we again felt there is need for some kind of official committee to drive Fedora Globalization activities. Fedora is growing faster with number of different domains and G11N also need to adapt those changes quickly to remain on the track. For this purpose and in line with [1], we were thinking of Fedora Globalization steering committee. I have created initial proposal for it. [2] Its open for feedback, please feel free to share other active members, discuss in your respective language groups. This is just initial proposal and i am sure, we can improve and make it more effective with active participation. Regards, Pravin Satpute 1. https://fedoraproject.org/wiki/L10N_Steering_Committee?rd=L10N/SteeringComm… 2. https://fedoraproject.org/wiki/Fedora_G11N_Steering_Committee_Proposal _______________________________________________ g11n mailing list g11n(a)lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org

10 28

Creating a new project
by Matej Marusak 01 Feb '20

01 Feb '20

Hello, I tried to create a new project in Weblate, but got an error saying I don't have permissions to do so. It was possible for anyone to create new projects in Zanata. Is this a new workflow? If so, is there some process how to request new projects? (opening ticket somewhere...?) Thank you! MM

2 1

[Fedocal] Reminder meeting : L10N
by jibecfed＠fedoraproject.org 26 Jan '20

26 Jan '20

Dear all, You are kindly invited to the meeting: L10N on 2020-01-27 from 13:00:00 to 13:30:00 Europe/Paris At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Localization meeting https://www.timeanddate.com/worldclock/converter.html?iso=20190916T150000&p… More information available at: [https://fedoraproject.org/wiki/L10N/Meetings](https://fedoraproject.org/wik… Source: https://apps.fedoraproject.org/calendar/meeting/9620/

1 0

Creating linked components
by Matej Marusak 26 Jan '20

26 Jan '20

Hey, so we created a new branch in cockpit[1], for we want to track translations separately. However, we want to have this new component (branch) connected to the master component. I know it is possible to create linked component, but could not find it. Can someone please advise me? Thank you! MM [1] https://translate.fedoraproject.org/projects/cockpit/ -- Matej Marušák Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig>

4 7

What does "generated" mean in bal (generated) (bal)
by Mike FABIAN 24 Jan '20

24 Jan '20

On: https://translate.fedoraproject.org/languages/bal/ I see: bal (generated) (bal) This is apparently used in the "fedora-websites" project. bal is the Balochi language: https://en.wikipedia.org/wiki/Balochi_language What does “generated” mean? -- Mike FABIAN <mfabian(a)redhat.com> 睡眠不足はいい仕事の敵だ。

3 4

Fedora & Weblate + cross project collaboration ; our priorities
by Jean-Baptiste 22 Jan '20

22 Jan '20

Dear translators, thanks to Fedora funding[1], I'll attend Weblate's BOF at FOSDEM: https://fosdem.org/2020/schedule/event/bof_weblate/ As included in Council funding request to pay the hosting of our translation platform[2], the cross project collaboration is still on track. We will have members of the Document foundation and OpenSuse community, so that we can discuss cross projects collaboration. My main idea here is to allow to connect using Fedora account and OpenSuse account to all platform (easy to set, it's a symbol), and to share translation memory (difficult to set, but it's important for contributor's efficiency). I'll be the voice of the Fedora project at this event, what should be our requests priority regarding the weblate tool? Here is my priority list, from most important to less important: 1. Allow to upload POT files for upstream projects: https://github.com/WeblateOrg/weblate/issues/3263 2. License change should trigger a notification: https://github.com/WeblateOrg/weblate/issues/3369 3. Allow to make license mandatory and to disable some licenses: https://github.com/WeblateOrg/weblate/issues/3370 4. Restrict access on component level: https://github.com/WeblateOrg/weblate/issues/3267 5. Validate repository browser links https://github.com/WeblateOrg/weblate/issues/3391 6. Differentiate anymous user from bot https://github.com/WeblateOrg/weblate/issues/3009 On hold: Pull request for Pagure hosted projects: https://github.com/WeblateOrg/weblate/issues/3346 You are welcome to share your thoughts, even if it is to say "it's fine". Jean-Baptiste [1] https://pagure.io/mindshare/issue/178 [2] https://pagure.io/Fedora-Council/tickets/issue/268

1 0

Project structure in weblate?
by Sundeep Anand 22 Jan '20

22 Jan '20

Hi, It would be really helpful if we keep project structure as: 1 source repo : 1 weblate project : 1 fedora package Project components could be either - fedora releases f32 f33, or - git branches, or - upstream releases thoughts? thanks, sundeep

3 3

GO/NOGO for Weblate in production
by Jean-Baptiste Holcroft 22 Jan '20

22 Jan '20

Dear translation team, we are experimenting Weblate for a few months now. It's time to say if you feel confident the tool can allow us to do our job as a translation community. Please share the language in which you translate and answer: +1 to confirm Weblate is suitable for the Fedora translation community +0 is sometimes used to indicate a disagreement but willingness to stand aside, this should also be accompanied with an explanation -1 to disagree, this should also be accompanied with an explanation GO is if the sum of answer is greater than zero. Please note: you can +1 and share your feedback about what is good and what is to improve in Weblate. Jean-Baptiste

19 18

Re: DNF and Anaconda ask to delay Zanata migration in March
by Jean-Baptiste Holcroft 21 Jan '20

21 Jan '20

Ludek, please use this UI to register to the mailing list: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/ You can also respond without registering using the same URL. >>> 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. > > Absolutely. We are pushing our translations to Zanata/ Weblate approx. > 4 times a year during the RHEL 7 and RHEL 8 localization schedules. > Our scope is limited though, we focus on customer critical components > such as: installation (anaconda, dnf), administration (cockpit, > composer), storage, networking, selinux, comps. Good, then, I should be able to create a component list for these projects to make it easier to find. > This is something which needs to be coordinated with the respective > RHEL sub teams. If you need, I can provide you with contact > information but I am no the person who has access to their git > repositories, unfortunately. What you can do: go in this list of issues to tell the team they can migrate if they make sure it won't impact RHEL 8 localization schedules: https://bugzilla.redhat.com/show_bug.cgi?id=1785028 (anaconda) https://bugzilla.redhat.com/show_bug.cgi?id=1787204 (dnf) https://bugzilla.redhat.com/show_bug.cgi?id=1789350 (rhel-comps) I'm unsure of what you call "storage" and "networking": I have blivet in storage category: https://github.com/storaged-project/blivet/issues/821 Could you provide a more precise list? selinux looks like to have one fork per platform, I feel like we should probably merge the effort upstream instead of translating multiple time the same content: https://github.com/SELinuxProject/selinux/issues/198 (selinux) Could you contribute or invite RH dev team to contribute the discussion? Jean-Baptiste

1 0

Fwd: Re: DNF and Anaconda ask to delay Zanata migration in March
by Jean-Baptiste Holcroft 21 Jan '20

21 Jan '20

Another answer out of mailing list. -------- Courriel original -------- Objet: Re: DNF and Anaconda ask to delay Zanata migration in March Date: 2020-01-21 11:05 De: Luděk Janda <ljanda(a)redhat.com> À: Jean-Baptiste Holcroft <jean-baptiste(a)holcroft.fr> Cc: duffy(a)fedoraproject.org, Fedora Translation Project List <trans(a)lists.fedoraproject.org>, Matej Marusak <mmarusak(a)redhat.com>, jkonecny(a)redhat.com, Michal Konecny <michal.konecny(a)packetseekers.eu>, mblaha(a)redhat.com Hi Jean-Baptiste, I am afraid my messages don’t get to the Fedora translation project list because I am not subscribed there. > On 20.01.2020, at 10:19, Jean-Baptiste Holcroft > <jean-baptiste(a)holcroft.fr> wrote: > > 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? I am comparing workloads in Zanata vs Memsource (our internal platform), because we used to get PO files from Zanata. We had no experience with Weblate till recently, that’s why I don’t have the comparison numbers ready for that new platform. > >> 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? > Weblate is currently checking for example Leading/trailing colons, periods etc. We are checking only Leading/trailing spaces. Weblate is checking plurals in Asian languages, I wonder why because those languages have no plurals. Checking missing plurals in French in words such as fois, mois, etc does not make much sense either. Weblate is checking English words in the target language which is also a sort of annoyance in UI projects. We won’t be probably able to perform such detailed check in Memsource. >> 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. Absolutely. We are pushing our translations to Zanata/ Weblate approx. 4 times a year during the RHEL 7 and RHEL 8 localization schedules. Our scope is limited though, we focus on customer critical components such as: installation (anaconda, dnf), administration (cockpit, composer), storage, networking, selinux, comps. Our aim is to have 100% Japanese completed. But partially we are covering the other strategic languages too: Chinese (China), Korean, French. It’s great to see our translations could be reused by the community. > > 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 > This is something which needs to be coordinated with the respective RHEL sub teams. If you need, I can provide you with contact information but I am no the person who has access to their git repositories, unfortunately. Thanks, Ludek > We have much to learn from each other. > > Jean-Baptiste >

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans January 2020