16:04:43 #startmeeting L10N 16:04:43 Meeting started Mon Nov 4 16:04:43 2019 UTC. 16:04:43 This meeting is logged and archived in a public location. 16:04:43 The chair is jibec[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:04:43 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:04:43 The meeting name has been set to 'l10n' 16:04:51 #meetingname L10N 16:04:51 The meeting name has been set to 'l10n' 16:05:02 .hello2 16:05:03 suanand: suanand 'Sundeep Anand' 16:05:21 #chair suanand jibec 16:05:21 Current chairs: jibec jibec[m] suanand 16:05:27 .hello2 16:05:28 jibec[m]: Sorry, but you don't exist 16:06:36 .hello2 jibecfed 16:06:40 jibec[m]: Sorry, but you don't exist 16:06:52 #topic Phase 1 - weblate beta period 16:07:05 congratulations on setting up weblate staging and some initial momentum .. 16:07:18 this are going quite well, https://translate.stg.fedoraproject.org/stats/ 16:07:38 we have 54 contributors, about 2000 translations, which is good 16:07:43 nice! 16:08:13 I'm wondering if you had time to look at FPCA suanand ? 16:08:32 FPCA.. please expand . 16:08:35 the idea is as follow: make sure all contributors validates the FPCA 16:09:21 the actual feature is: https://docs.weblate.org/en/latest/admin/licensing.html#contributor-agreement 16:09:27 contributor agreement be platform-wide in Weblate? 16:09:42 the goal was allow a platform wide agreement 16:09:43 yes 16:10:20 aha - actually (sorry) I didn't started working on it. (was on vacations) .. shall start working on it.. on priority :) 16:10:45 (just looking) do we have a ticket .. 16:11:54 if you may have a look at the feasability it would be sweet, if you can't, I'll ask the weblate dev 16:12:19 but I like the idea of our community to have basic weblate knowledge :) 16:12:28 umm.. okay shall I let you now by next meeting? 16:12:32 next subject? 16:12:52 #action feasibility of contributor agreement be platform-wide in Weblate? 16:13:22 well, whenever you can, I think it will be a mandatory feature in january 16:13:36 so if you can have a look this month, it's fine 16:13:43 #topic Set-up a contract with the Weblate company 16:13:45 aha, sure!.. for sure! 16:13:56 I'm stuck in that subject, action is on bex' side 16:14:06 ops! 16:14:28 I stopped adding new projects for now, because I don't have configuration from Brian that we have a good legal agreement 16:14:47 it's about data privacy, and being able to pay the bill ;) 16:15:13 aha 16:15:36 not too complex normally, but brian was traveling a lot, he said it should be fixed soon 16:15:51 okay - shall we follow up (I mean wait for some more time) 16:15:53 #topic Phase 2 - Weblate in production 16:15:54 ah - cool! 16:16:27 weblate will push events in our infrastructure https://pagure.io/fedora-infrastructure/issue/8291 16:16:42 okay, nice 16:16:58 this will allow stats and badges <3 16:17:15 and we may use it for side usages 16:17:31 right.. Yes :) 16:17:35 like feeding a dedicated l10n tool (I'm thinking about Benson's will to create a translation machine service) 16:18:10 I also created a change for F32: https://fedoraproject.org/wiki/Changes/Translation_platform_migration_to_Weblate 16:18:12 translation machine.. as-in memory or.. 16:18:23 this was published on devel mailing list 16:18:43 suanand: like deepl or google translate, etc. 16:18:58 hmm. that would be awesome! 16:19:23 yes, but it's really complicated, let's hope he will succeed ;) 16:19:51 next topic? 16:20:08 I agree - it's really really complicated.. and hard to attain accuracy in.. (I'm also interested looking into it) 16:20:32 I guess weblate has feature of creating personal memories for translators? 16:21:00 yes 16:21:04 cool 16:21:31 and this is the field I would like to get involved for our community: create a large translation memory taking strings from every packages 16:21:52 but the machine translation service is way more complex and I'm sure I won't have time for it 16:21:58 #topic Fedora docs localization 16:22:06 the generation works fine: https://docs.stg.fedoraproject.org/ar/council/contact/ 16:22:08 it is complicated too.. as in classifying as per domains, tagging them etc etc 16:22:36 msg-context plays imp role here 16:22:37 but we still have some built issues, that's why I'm not talking much about it 16:22:49 once fixed, we'll publish it 16:23:14 sure, sure - I agree.. good to have all these.. on our path.. 16:23:30 yes suanand, I asked to have a collaboration with someone with a PHD on the matter to have advices/feebacks and stuff 16:23:49 we need NLP professionals.. 16:23:51 I'll tell you more about it in the future 16:24:04 sure - shall collaborate ..:) 16:24:36 #topic open discussions 16:25:02 What about the pt_PT/pt problem? 16:25:03 ah - I need to ask about priority.. 16:25:04 yes, probably, but without data we don't need them :p 16:25:47 mfabian: the portugal language is handled as pt_PT instead of just pt? 16:25:52 Yes. 16:26:00 I am not 100% sure about it. 16:26:19 On Fedora, it seems that translations for pt_PT.UTF-8 locale usually live in only pt. 16:26:33 And pt_BR.UTF-8 translations live in pt_BR. 16:26:51 So Portuguese Portuguese is the fallback for pt_BR if that does not exist. 16:27:05 Similar like fr would be the fallback for fr_CH 16:27:08 * suanand nod 16:27:18 Probably nobody translates fr_CH. 16:27:33 I think it's a political dilema, the standard uses pt for the country with the most speakers, and BR wins, so they changed it, I have no idea what to do for now, I'll investigate 16:27:33 So having the French translations in fr_FR would be not nice for fr_CH. 16:27:41 I may be wrong ;) 16:27:50 it depends on how different these Portuguese variants really are. 16:28:13 like zh for example: zh_CN and zh_TW are different enough that falling back from one to the other makes no sense. 16:28:22 As far as I know. 16:28:38 But when the difference is not so big, such a fallback makes sense. 16:28:38 (I would suggest to prefer locale xx_YY over language-id xx) 16:28:52 I'll have a look at it this week, but I don't really know what to do for now, thanks for raising attention on the subject 16:29:13 #topic next meeting 16:29:16 Indian Languages also have these variants.. 16:29:22 suanand: I we would put the German translations into de_DE, user from Austria or Switzerland (de_AT and de_CH would get almost no translations). 16:29:40 Even though the German langauge in Germany, Austria and Switzerland is almost the same. 16:29:46 I was quite fast on this meeting, I have to go. next meeting is next monday 1PM french timezone, I'll change the meeting invite 16:30:06 So it is very good to put the German translations only into de, then de_DE, de_AT, and de_CH can all use it. 16:30:38 hmm. mfabian - okay.. so it's depends (no universal rule) :p 16:30:48 My guess is that pt is a good choice for Portuguese. 16:31:25 probably, let's just understand the reasons why Weblate does that to anticipate other issues 16:31:43 I have to go, thanks a lot for coming 16:31:49 #endmeeting