06:02:11 #startmeeting i18n 06:02:11 Meeting started Wed Sep 17 06:02:11 2014 UTC. The chair is tagoh_. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:02:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:02:11 #meetingname i18n 06:02:12 The meeting name has been set to 'i18n' 06:02:12 #topic agenda and roll call 06:02:12 #link https://fedoraproject.org/wiki/I18N/Meetings/2014-09-17 06:02:24 okay, time to have i18n meeting now 06:02:46 Hi! 06:02:48 hi 06:02:52 hi 06:02:57 hi 06:03:13 hi 06:06:14 let's get started. 06:06:25 #topic Upcoming schedule 06:06:26 #info 2014-09-23 Alpha Release 06:06:26 #info 2014-10-14 Software Translation Deadline 06:06:26 #info 2014-10-14 Beta Change Deadline 06:06:27 #info 2014-10-14 Accepted Changes 100% Complete 06:06:44 Hi 06:06:50 slipped one week again. RC1 is available now 06:12:06 seems gnome-initial-setup-3.13.6-1.fc21 should fix the g-i-s issue with existing new user 06:12:34 not sure if it will be in alpha though 06:12:52 (I haven't tested yet) 06:13:09 .bug 1116316 06:13:12 juhp: Bug 1116316 gnome-initial-setup does not run if user is created in anaconda - https://bugzilla.redhat.com/1116316 06:14:06 (still in f21-gnome) 06:14:14 I created user while installing F21 RC1 and I have not seen any such fix 06:14:24 there is no g-i-s run on first start 06:14:39 okay - I guess you have the older build, right? 06:15:12 yes 06:15:29 3.13.5-2.fc21 06:15:30 older build? 06:15:37 :) 06:15:39 Ah, OK. 06:17:24 I guess gnome-3.13.92 is still being built 06:17:41 so presumably will be a post-alpha update 06:18:09 unless there is more slip or it can be squeezed in 06:20:05 is it a FE bug right? 06:20:12 in alpha, but blocker in beta 06:23:14 tagoh_, right 06:23:43 well proposed blocker :) 06:24:32 aha 06:24:50 okay, shall we move on 06:24:58 #topic Oustanding topics 06:24:58 #info #31: Fedora 21 i18n docbeats (tagoh) 06:24:59 #link https://fedorahosted.org/i18n/ticket/31 06:25:17 https://fedoraproject.org/wiki/Documentation_I18n_Beat 06:26:30 updated a bit since last week. anything else we should have in relnotes? 06:33:47 better move on then 06:33:52 #info #33: Keep watching MozTrap related discussion (pnemade) 06:33:52 #link https://fedorahosted.org/i18n/ticket/33 06:36:58 paragan: do you have anything you want to talk about? 06:38:05 no updates 06:38:28 I think probably MozTrap will not be used 06:39:12 aha 06:41:35 okay, move on then 06:41:39 close? 06:41:45 #topic Outstanding task 06:41:46 #info #32: Fedora 21 i18n test day (tagoh) 06:41:46 #link https://fedorahosted.org/i18n/ticket/32 06:43:29 just a reminder for those who not yet tried or put the result onto the test day page, though not set the due date for this at this moment, encourage you to join it to improve your language support. 06:43:52 #topic Open Floor 06:43:59 tagoh_: yeah, i will do it in couple of days, just download alpha-1 06:44:08 pravins: thanks 06:44:16 anything else we want to discuss before stop the meeting? 06:46:27 juhp: maybe good to keep watching until making any decision? dunno 06:46:33 if one has an input engine active (doesn’t matter which one) and executes “ibus restart”, is it normal that the engine stops working? 06:46:34 ok 06:47:02 Switching to some other engine and back makes it work again, but after “ibus restart” the current engine stops working. 06:47:34 hmm I seem to see this sometimes when I start ibus (desktop) session 06:47:57 I have to switch IME and return to get it active 06:48:06 It is 100% reproducible for me when I do “ibus restart” from the command line. 06:48:11 aha 06:48:16 I can try too 06:48:23 Is that a bug or something one has to accept? 06:48:43 fujiwara should be back next week 06:48:44 I mean should I report this as a bug or is this “normal”? 06:48:56 mfabian, feels like a bug to me anyway 06:49:33 OK, then i report it. 06:50:10 thanks 06:50:30 is ibus supposed to keep the state anyway? e.g. when the engine is active and shut down the machine, should the engine be active when one logged in to the desktop? is it the same question? 06:50:58 tagoh_: At least when Gnome is used, the state seems to be remembered. 06:51:12 Some people don’t like that: 06:51:27 okay 06:52:42 When one uses the mode where the input source can be different for each window, the input source active for the window which has focus when logging out of gnome is remembered and becomes the default next time. 06:52:54 ah hmm 06:53:32 right in that case local state makes less "sense" or maybe should behave differently 06:56:23 anything else? 06:56:32 https://bugzilla.redhat.com/show_bug.cgi?id=1133127#c68 06:57:19 So this user does not like that Gnome remembers the last used input source. 06:57:32 (I don’t care whether it remembers or not) 06:58:37 mfabian, might be vocal minority ;) :) 06:58:56 Yes ☺ 06:59:46 though yeah ideally per app state cache be ideal or somehow to override it 07:00:04 s/how/way 07:02:01 if no more topics to discuss, will stop the meeting shortly. 07:05:31 okay. thanks everyone for the meeting! 07:05:41 #endmeeting