06:02:54 #startmeeting i18n 06:02:54 Meeting started Thu Sep 27 06:02:54 2012 UTC. The chair is tagoh_. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:02:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:02:54 #meetingname i18n 06:02:54 The meeting name has been set to 'i18n' 06:02:55 #topic agenda and roll call 06:02:56 #link https://fedoraproject.org/wiki/I18N/Meetings/2012-09-27 06:03:04 okay, shall we have a meeting 06:03:22 hi 06:03:26 hi 06:03:31 hi 06:03:33 hi 06:04:06 hi 06:04:24 hi 06:05:07 hi 06:05:40 okay, let's get started 06:05:44 #topic Upcoming schedule 06:06:36 just a reminder, in planning, tomorrow is l10n test day 06:06:43 https://fedoraproject.org/wiki/Test_Day:2012-09-28_l10n 06:07:37 good to help if you have a time. 06:07:54 * juhp guesses they don't have a fix for the anaconda locale problem 06:08:20 and this gives us an opportunity to take a look carefully for rendering maybe. 06:09:08 juhp: maybe. need to do some steps manually to address it 06:09:30 yes 06:09:40 not very easy 06:09:45 right 06:09:52 though not impossible... 06:10:04 tagoh_: yes agree, hoping will get some bugs against harfbuzz and lohit 06:10:37 pravins: yep 06:11:37 okay, move on 06:11:41 #topic Outstanding topics 06:11:42 #info #1: FEAT: GNOME IBus Integration (fujiwara) 06:11:42 #link https://fedorahosted.org/i18n/ticket/1 06:11:43 #link https://fedoraproject.org/wiki/Features/GNOMEIBusIntegration 06:11:55 fujiwarat: can you update? 06:12:42 I guess 3.6 is about to be released or out already I guess. so it may be a time to update the feature page. 06:14:18 and for the menu items for modes etc, apparently it seems supporting ibus-anthy only so far. as pwu concerned, we need to fix it for other engines too. 06:14:59 what is the process for whitelisting IME menu items? filing an rfe in gnome bz? 06:15:11 yes 06:15:41 http://git.gnome.org/browse/gnome-control-center/tree/panels/region/gnome-region-panel-input.c#n67 06:16:06 pwu won't be back until the week after next though... 06:16:20 looks like it's impossible to add IME menu items 06:16:28 paragan: not what engines appears. 06:16:51 for anthy they patched in GNOME's shell 06:17:07 Now main features are integrated. Unfortunately switcher UI is not implemented yet. 06:17:18 they have hard corded IME's menus 06:17:49 fujiwarat, sorry for what switcher UI is needed? 06:18:18 fwiw gnome-initial-setup seems not in f18. so we missed the place to set up the default engines and key bindings. 06:18:38 http://git.gnome.org/browse/gnome-shell/commit/?id=9659d934ac190a6363fc5b59f3c62ef305f56c52 06:19:30 other than that, possibly a concern is upgrading. once one upgrade to f18, they may miss IM working until they do configure the input source on g-c-c. 06:19:36 fujiwarat: any idea for that? 06:20:24 paragan, i don't see any menu items in that file? 06:20:37 if we have any plans for that, it should be described in the common bugs maybe. 06:20:51 juhp, http://git.gnome.org/browse/gnome-shell/commit/?id=9659d934ac190a6363fc5b59f3c62ef305f56c52 06:20:53 anish__: aha. thanks 06:20:58 juhp, menu items? 06:21:17 paragan, yeah we are talking about IME menu items not IMEs :) 06:21:21 anish__: yes, it's what we are talking about :) 06:21:26 ok they are not there 06:21:27 thanks 06:22:03 actually its impossible for other IME's to have menu items 06:22:12 hmmm 06:22:21 actually upstream should consider having one .conf file 06:22:32 to configure each IME's menu items 06:22:54 in this way they can accommodate all the IME's menu item 06:23:16 tagoh_: Allll we do might be the release note. gnome components are out of our maintainances. 06:23:40 fujiwarat, kind of wish the kana<->romaji was not exposed in the menu 06:23:59 that is why GNOM's upstream will never white list all the IME's 06:24:10 fujiwarat, well we can file rfe and patches to upstream for future 06:24:19 juhp: ? 06:24:38 kana<->romaji 06:24:39 fujiwarat: well, upgrading issue is certainly a bug. it's not something we should write in relnotes. 06:25:11 fujiwarat, I thought we agreed to drop the input style config from the menu 06:25:15 but anyway 06:25:38 tagoh_: But do you mean to note adding engines & trigger keys with g-c-c? 06:26:05 for menu items, would be better filing a bug upstream as long as it's hardcoded in gnome-shell. 06:27:21 fujiwarat: well, the important point is to let users know IM won't work after upgrading. 06:27:32 which is a bug. 06:27:50 juhp: Ah, you mean Typing method is shown unexpectedly. I thought either showing the menu or not is fine. 06:28:00 fujiwarat, yes 06:28:42 fujiwarat: or is it possible to add any migration script or so in postinst of ibus? to convert configuration in ibus to gsettings say? 06:28:47 tagoh_: ok, got it. I have no idea if the rel-note reaches the dead line. 06:30:07 tagoh_: Hmm.., can ibus beak gnome ui freeze? 06:30:16 s/beak/break/ 06:30:31 fujiwarat: breaks what? 06:31:11 I think changing gnome's gsetting by ibus would break the gnome code freeze. 06:31:33 I'm not sure if we can do it. 06:33:33 anyone can do run gsettings to modify everything there. they might breaks something in runtime if they do unexpected things. but I don't think it breaks release-schedule-wise matter. 06:34:03 ok 06:34:36 well, it's just an idea to address the upgrading issue. if there are any more better idea, I'm fine. 06:34:56 I'm not sure if we should do it. 06:35:24 any comments? 06:35:39 do you think it's not a bug then? 06:36:19 looks like an regression bug to me though 06:38:13 regardless of how it is fixed, it should be filed into bz first anyway. I'll do that. 06:40:01 anything more we are possibly missing concerned around ibus? 06:40:14 tagoh_: Do you mean both engines and trigger keys? 06:40:46 fujiwarat: ideally, yes. 06:41:23 ok 06:42:02 One thing is that we don't resolve the ctrl+space between applications. 06:42:07 given that users are not changing anything and using as default configuration, is it likely that any configuration isn't stored into any files? 06:43:08 fujiwarat: are you talking about sharing IM context among applications? 06:43:39 tagoh_: No, no, I mean ibus, emacs, eclips... 06:43:46 ah, I see 06:44:23 well, we have no conclusion about it yet. so need to keep a discussion I guess. 06:44:45 it's a separate issue to this upgrading issue. 06:45:38 so is it all the issue we know so far? anyone has anything? 06:46:08 tagoh_: we do have Liberation fonts issue pending, but i think will be good to discuss in next meeting 06:46:45 sure. okay, it's another topic. 06:46:51 yes 06:47:16 tagoh_: Another idea is to launch g-c-c by imsettings in the initial login. 06:48:39 fujiwarat: hmm, no functionality to detect for first boot or not in imsettings. 06:49:57 Probably imsettings could create a dummy gsettings for the initial login as f17 ibus did. 06:50:19 well, once filing a bug, adding any ideas there and discuss would be nice. 06:50:20 aha 06:51:08 fujiwarat, do we need to use im-chooser or imsettings in normal gnome? 06:51:25 or just providing a migration script may be good in worst case. dunno 06:51:48 ibus gtk panel can configure the default engines in non-gnome-shell. 06:53:44 paragan: im-chooser works on GNOME3 if a) on fallback mode b) non-ibus IM is running 06:54:46 ok 06:55:35 do I need to start in fallback mode to choose different IM? 06:55:37 What means “fallback mode”? 06:56:33 mfabian: gnome-panel is running instead of gnome-shell 06:57:03 tagoh_: I see, thank you! 06:57:20 it's rarely happening since the software rendering is enabled. 06:57:48 mfabian, http://library.gnome.org/users/gnome-help/3.3/fallback-mode.html.en 06:58:28 #action tagoh_ to file a bug for upgrading issue on ibus 06:59:06 #action engines maintainer to file a bug upstream to add ime menu items as needed 06:59:22 okay, anything more? 07:00:36 fujiwarat: ah, well, please update the feature page :) 07:01:13 #action fujiwarat to update the feature page 07:01:18 if not, let's move on 07:01:47 #topic Open Floor 07:02:15 anything more topics we are missing in the agenda? particularly if any urgent. 07:04:23 okay, let's stop here then. 07:04:30 thanks everyone for the meeting 07:04:35 #endmeeting