05:01:26 #startmeeting i18n 05:01:26 Meeting started Thu Nov 17 05:01:26 2011 UTC. The chair is tagoh. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:01:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:01:31 #meetingname i18n 05:01:31 The meeting name has been set to 'i18n' 05:01:40 #topic agenda and roll call 05:01:52 https://fedoraproject.org/wiki/I18N/Meetings/2011-11-17 05:02:03 hi 05:02:06 hi, time to have i18n meeting. 05:02:13 hi 05:02:15 hi 05:02:32 hi 05:02:35 feel free to add any topic to the agenda if you have. 05:02:37 hi 05:03:27 hi 05:03:51 hi 05:04:56 okay, let's get started. 05:05:11 #topic Supportaed language list 05:05:48 well, just added it because that would be a good idea to have the language support criteria from the i18n POV. 05:06:33 and clarify what langauges we support in the release. 05:07:06 tagoh: this will like (one can type, render and see locale), right? 05:07:20 pravins: yes 05:08:16 great, step. wikipedia support something around 300 language, i think we can take reference from that. ;) 05:08:16 great 05:08:38 perhaps we need a wikipage for that 05:08:46 juhp: yeah 05:09:18 do we need global language coverage page on fedorawiki? 05:09:49 paragan, I think it would be good - maybe we can start gradually? 05:09:59 say a table for Asian languages 05:10:05 paragan: IMHO good to add the list to relnote or something like that. 05:10:25 only? 05:10:30 both? 05:10:45 paragan: yeah that will be nice, it will truly reflect fedora's internationalization part 05:10:48 aha maybe 05:11:09 ok 05:11:28 nice thing about that would be we can easily look back and see how coverage evolved 05:11:44 anyway I guess wiki is the place to start 05:12:08 well, it may be different among the releases. so any places would be ok if it's obvious what release it is for. 05:12:12 also don't no if we have to list every single language like English etc 05:12:28 s/no/know 05:12:47 anyway I'd try with the non-trivial ones :) 05:13:31 i18n/Language_Support ? 05:13:45 s/try/start/ ugh 05:14:14 juhp: may depends; if we have more strict criteria? dunno if we can update our blocker bug process with it though. but would be nice if we could say it's a regression say. 05:14:32 aha 05:14:46 juhp: tagoh but this can be great, we will know where we are and where we want to go 05:16:21 guess minimal requirements would be whether or not the input, fonts, rendering, printing would works for the language. 05:17:40 tagoh: yes 05:17:44 we could build up the initial table for f16 perhaps and if we have certain criteria, any volunteers can check against it and add any language to the table. 05:18:22 sure 05:19:15 sounds good 05:19:17 let me try to make a draft on wiki.. any help are always welcome :) 05:19:48 great thanks 05:20:03 I can certainly lend a hand with some langs 05:20:07 any questions or suggestions so far? 05:20:18 juhp: thanks 05:21:36 ah, well, this can be reflected to the test day's testcase perhaps. 05:21:41 but anyway 05:22:35 okay, better move on 05:22:44 hi, thanks, that's good to have the language table 05:22:59 #topic F17 05:23:06 lijli: yep 05:24:22 so not too much things is going on yet. some features are already going to be submitted it seems. so any idea for f17 features on i18n? 05:25:17 anyone working on it if you have? 05:26:06 guess early submission would be good for development and testing too. 05:27:35 i am working on european -indic-table 05:27:58 I am working on ibus-pinyin with libpinyin back end. 05:28:08 thought the candidate from the last meeting was libpinyin, fonts-tweak-tool and Inscript2 though 05:29:45 good to make the plan clearer according to the template and propose it for f17 if it's worth promoting as f17 features 05:30:56 we still have a time for proposal though 05:31:32 anish_: once you setup git repo, do let us know. so we can test and give some suggestions 05:31:44 yeah to prepare Feature pages in good time - since that process also helps to clarify one's thinking :) 05:32:03 pravins: cool 05:32:12 juhp: right 05:32:27 anish_, perhaps you can do a feature for European completing input or English at least :) 05:32:50 pravins, juhp i will do that 05:33:14 anything else? 05:33:22 when you're ready :) 05:34:29 okay, let's move on then. 05:34:43 #topic Bugzilla house keeping 05:35:12 only fyi, we still have 37 bugs open in f14. 05:37:01 good to have a little time to review them and take an appropriate action for them. the goal is to avoid the unfortunate auto-close due to EOL, even though it's not yet fixed in any releases. 05:37:51 hmm 05:37:59 of course any volunteers to have a look at them are welcome and propose any fix for them 05:38:58 agreed - let's all try to re-triage open f14 bugs and either move to a newer release or close them out 05:39:32 if issues aren't reproducible, good to ask bug reporters. could be closed in any cases perhaps. 05:39:45 yes 05:40:16 it's not that surprised the issue is fixed in any release without any notice unfortunately or fortunately ;) 05:40:55 so let's revisit your bugs or i18n bugs to update. 05:41:12 #topic Input Methods 05:41:29 any news, updates or concerns to share? 05:43:01 I think there is still not consensus on what to do for IME menu for gnome ibus 05:43:16 sure 05:43:36 I think aday is pushing to have just one menu for input 05:46:43 hm, IMHO if any keybindings works enough, it could be dropped there. 05:47:28 tagoh: thinking to make booster as a default IME for supported language in Fedora 17 05:47:31 hm yeah 05:47:53 I'd think my idea still works with his thought. 05:48:11 but need to do some analysis and take some feedback prior to that from l10n 05:48:12 tagoh: the currently anthy keybindings for conversion are a bit hard to remember 05:48:26 fujiwarat, perhaps a mockup would help 05:48:36 s/ly// 05:49:00 juhp: assuming one uses the japanese keyboard though, but yeah might be hard on english keyboard 05:49:39 juhp: agreed 05:51:27 so which one may be hard to drop from the menu particularly? does anyone have any list per IME? 05:52:49 tagoh: right 05:53:29 tagoh: typing modes and selection dicts from anthy. 05:53:52 also mclasen was complaining that input with ibus seems slow - specially spacebar?? 05:54:15 (anyway I don't think we're planning to turn on ibus for everyone yet, right?) 05:54:44 I wonder how many people use kasumi? 05:54:53 space key? 05:55:07 juhp: still need some improvements for footprint I guess. 05:55:24 juhp: Why are you talking about kasumi? 05:56:18 fujiwarat: feels the response of activation with ctrl+space and such becames slow a bit regardless of using ibus-gnome3. 05:56:40 since new ctrl+space 05:56:55 guess it's a known issue? 05:57:02 tagoh: Do you mean the first ctrl+space? 05:57:45 fujiwarat: not first. but sometimes? ibus ignores it when typing faster. 05:58:34 juhp: it's only way to manage the anthy dictionary though 05:59:55 tagoh: yeah I have seen that too - particularly with ibus-gnome3 perhaps? 06:00:07 tagoh: yeah i mean from the menu :) 06:00:25 juhp: think it's known and there should be a bug in bz 06:01:04 dunno if it really affects without ibus-gnome3 though. 06:01:49 anyway, for the menu, IMHO would be good to have a list what the current status is and discuss against it if it can be dropped or not. 06:03:22 yes 06:03:39 or file a bug against IME and discuss on it? 06:04:54 any way is ok if it certainly works.. 06:04:59 anything else? 06:05:31 right 06:06:13 fujiwarat: for slow issue, if you think it's separate issue to with ibus-gnome3, I'll file one. 06:07:01 better move on. 06:07:12 #topic Fonts and Rendering 06:07:20 any news, updates or concerns to share? 06:08:48 .bug 748710 06:08:49 pravins: Access Denied - https://bugzilla.redhat.com/show_bug.cgi?id=748710 06:09:50 had a discussion with shankarprasad just, i think we can modify some shapes without affecting other thing 06:10:00 hmm 06:10:13 pravins: aha 06:10:37 tested it with windows yesterday windows also gives same result, i.e. character cutting with negative sidebrearing 06:10:44 so i think we need to handle it in font only 06:10:58 okay 06:11:25 this is upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=631585 06:12:27 tagoh: juhp i will work on this and give update 06:12:32 thanks 06:13:23 anything else from anyone? 06:15:28 if not, let's close the meeting shortly then. 06:16:33 okay, thanks everyone for the meeting! 06:16:39 #endmeeting