12:05:02 #startmeeting Fedora Trans 12:05:03 Meeting started Mon Dec 23 12:05:02 2019 UTC. 12:05:03 This meeting is logged and archived in a public location. 12:05:03 The chair is bkm. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:05:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:05:03 The meeting name has been set to 'fedora_trans' 12:05:58 #meeting name L10N 12:06:06 Hi 12:06:17 #meetingname L10N 12:06:17 The meeting name has been set to 'l10n' 12:06:23 Hi 12:06:56 #chair jibec[m] bkm 12:06:56 Current chairs: bkm jibec[m] 12:07:48 #topic migration to weblate 12:08:18 Testing seems to be going ok so far. 12:09:24 I guess there will be more activity in the New year. 12:09:42 #topic contract with Weblate 12:09:54 Has a contract been setup with Weblate? 12:10:07 Please share link to wiki with all the projects 12:10:20 In progress are ibus and cockpit 12:10:51 Great. 12:11:16 Done are little ibus projects 12:11:21 Thanks to mike fabian 12:11:56 Assume this link: https://fedoraproject.org/wiki/L10N_Move_to_Weblate 12:12:12 Current challenge with projects is that big projects don't want to store pot in their repo 12:12:56 * danpb waves - that'll be me with libvirt 12:13:09 Yes, this can be problematic. 12:13:47 fwiw, the libvirt-glib setup seems to work reasonably 12:14:01 So they prefer to interact with Weblate using manual pull/push 12:14:06 What is the libvert-glib setup? 12:14:27 main problem was we're unable to upload the libvirt.pot file so we had to call it en.po instead 12:14:50 Danpb, is it mandatory to upload it? 12:14:54 weblate seemed happy enough with using en.po as the template for new translations instead of the .pot file 12:15:13 Is this an issue that Weblate maintainers should be aware of? 12:15:40 Danpb I think it's because your component is configured as monolingual po files 12:15:47 possibly should be reported as a bug (RFE?) for their REST API 12:16:05 jibec[m]: even after i changed it to normal gettext, it was happy using en.po 12:16:32 You should be able this configure it as a classical one, I answered your issue with instruction on how to do so 12:17:05 we're lucky that a .pot & .po files are the same file format, and weblate lets you configure an arbitrary filename as the template file 12:17:46 so the fact that it was called en.po instead of libvirt-glib.pot wasn't a functional problem AFAICT - it just looks weird/unusual 12:21:26 So we do not have a full agenda, if there are other specific topics, please indicate them, otherwise can move to open floor. 12:22:01 (I'm back, cellphone crashed) 12:22:43 danpb do you mind if I tweak your component? 12:22:51 Sorry. Still on .pot and .po files, 12:24:24 jibec[m]: what sort of changes ? 12:32:12 Danpb: I'll write it in the issue, my internet is too bad for now :/ 12:32:41 Ok. 12:32:55 #topic Open Floor 12:33:16 Bkm, have you had progress with machine translation? 12:33:36 Still need to follow up further on this. 12:33:49 OK, let me know 12:33:52 jibec[m]: ok, that's fine - i just want to keep track of what's changed so i can make sure other libvirt projects get the same later 12:34:17 I did like the other service you sent a link to. Expanded translation memory was very nice. 12:35:05 It would be nice to have this possibly integrated in weblate, though using the two side by side also works but is a little cumbersome. 12:36:07 danpb: If many other projects use .pot files in addition to .po files, maybe better handling of .pot files would be helpful. 12:38:09 Any other topics? 12:39:00 Not on my side 12:40:18 Ok, translation memory in Amagama (https://amagama-live.translatehouse.org/) is nice. 12:40:44 If no other topics, we can end the meeting. 12:42:16 I think amagama will be included with weblate in the future 12:42:35 I read it in one of the weblate issues 12:42:42 Great 12:43:25 End meeting? 12:43:26 Thanks for attending. 12:43:39 jibec[m]++ 12:43:48 danpb++ 12:43:48 Thanks for leading this 12:43:53 #endmeeting