05:06:37 #startmeeting i18n 05:06:37 Meeting started Thu Jun 14 05:06:37 2012 UTC. The chair is tagoh_. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:06:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:06:41 #meetingname i18n 05:06:41 The meeting name has been set to 'i18n' 05:06:46 #topic agenda and roll call 05:06:53 https://fedoraproject.org/wiki/I18N/Meetings/2012-06-14 05:07:00 hi 05:07:05 sorry for late start. 05:07:13 hi 05:07:33 hi guys 05:07:44 Hi 05:07:45 hi 05:07:50 hi 05:09:10 hi 05:09:17 okay, let's get started. 05:09:24 #topic F18 05:10:03 well, so any updates or suggestions for i18n related features on f18? 05:10:48 tagoh_: anish_ we have lot to do for ibus-hunspell-table :) 05:10:49 i am going to file ibus-hunspell-table feature in this week 05:11:06 anish_: cool 05:11:08 as a first step i have retired all IT-booster packages in F18 05:11:22 pravins, thanks i will do that 05:11:30 pravins: okay 05:12:15 ibus-libpinyin is imported into rawhide. 05:12:47 #action anish_ to file a feature proposal for ibus-hunspell in this week 05:13:00 epico: cool 05:14:51 anything more on f18? 05:16:11 if there are any important features upstream is about to introduce in f18 timeframe, it may be good to consider proposing a feature on f18 05:16:35 okay 05:16:58 feel free to ask if you are not sure 05:18:04 even if it's good enough without feature proposal, it may be a good idea to write something in relnotes. sharing information here would be helpful to remind it for relnotes. 05:19:44 anyway, if no particular things to talk about f18, shall we move on then 05:20:10 #topic Bugzilla cleanup 05:20:59 any activities to recheck f14/15 bugs? for reminder, f15 EOL is June 26. 05:21:04 does anything obsolete the booster packages? 05:21:42 juhp: I guess ibus-hunspell does? 05:21:58 tagoh_, juhp yes 05:22:28 maybe not yet? :) 05:22:35 I mean at the rpm level :) 05:24:18 juhp: true. looks like not. 05:24:54 so that should be done before alpha at least 05:25:04 agree 05:25:23 (sorry late comment to previous section) 05:25:44 juhp: np. thanks for bringing it up 05:26:19 juhp: yes, i have created bug for ibus-hunspell table, interesting part is -typing-booster should be obsolete by hunspell- 05:26:39 pravins, aha 05:26:55 hmm yeah maybe 05:27:04 .bug 829658 05:27:10 pravins: Bug 829658 should Obsoleted/Provided marathi-typing-booster at least for Fedora 18 - https://bugzilla.redhat.com/show_bug.cgi?id=829658 05:27:14 .bug 829637 05:27:17 pravins: Bug 829637 ibus-hunspell-table should Obsoleted/Provided indic-typing-booster from Fedora 18 onwards - https://bugzilla.redhat.com/show_bug.cgi?id=829637 05:27:21 hmm, but hunspell- itself isn't alternatives for ITB right? 05:27:22 pravins, or maybe we could do it with yum-langpacks dunno 05:27:30 right 05:27:54 tagoh_: ibus-hunspell-table need hunspell- to get language displayed in ibus-preferences 05:28:07 I was saying the same to pravins that hunspell- is not alternative to ITB 05:28:14 I think also it might be better for i-h-t (why isn't it called i-h ;-P) to obsolete tb-* 05:28:22 so if someone wants to install marathi-typing-booster. I think it should install ibus-hunspell-table and hunspell-mr 05:28:32 right 05:28:41 pravins, and yum-langpacks can do that... 05:28:56 once configured of course 05:29:17 pravins: no explicit deps to hunspell-* in ibus-hunspell-table though, how are you going to pick up for certain languages then? 05:29:37 did I mention yum-langpacks :) 05:30:08 but yeah that will only work for one's locale 05:30:28 otherwise maybe "tough luck" 05:30:29 ? 05:30:34 what if no hunspell-* corresponding to the lang? :) 05:30:44 hmm 05:30:47 ditto? :) 05:31:28 in that case, there will be no display of engine for that lang in ibus-preference-table :) 05:31:28 well maybe we need more thought on this - can't see a simple perfect solution anyway 05:31:33 dunno if there are any safe-check in i-h-t in that case 05:31:42 anish_: frankly i am still bit confuse for this ;) But since we are planning to make it default we have to take care for these things 05:32:07 pravins: aha 05:32:34 I guess other question is how confident are we about making it the default for Indic input? 05:33:12 good question 05:33:32 we are replacing it with typing booster package 05:33:43 anyway we definitely need a feature page for that as soon as possible 05:33:45 I am confident since now we are using libtranslit which uses m17n in background. So we can assure user will get same result as m17n by using ibus-hunspell-table 05:33:55 juhp: right. it should be mentioned there. 05:34:20 yes as already brought up earlier 05:34:38 ok 05:34:50 but i am sure, it will pop-up some challenges. We need to start early 05:35:02 so let's discuss the feature page next week here? 05:35:14 pravins, I think so 05:35:23 pravins: okay. the point is if it's visible public. that would be useful when one has similar question. 05:35:32 but are we making lang-typing booster or just typing-booster 05:35:44 anish_, ? 05:36:11 do we require marathi or english typing booster 05:36:15 I thought we were dropping *-tb completely 05:36:24 or do you propose new metapackages? 05:36:25 yes 05:36:49 can't we have only typing booster package 05:36:55 anish_: we will work together on feature proposal 05:37:05 pravins, okay 05:37:23 pravins, how about f17 and earlier though - no change there? 05:37:25 i think writing feature will make some doubts more clear :) 05:37:29 yes 05:37:31 anyway, would be nice if you can prepare the feature page before next meeting. so we can discuss about it then. 05:37:37 right 05:37:41 tagoh_, thanks 05:38:01 ibus-hunspell-table there so yes user can test, if they can switch from m17n .mim to hunspell-table 05:38:22 pravins, I mean we will still keep TM packages there for now? 05:38:38 or also transition? 05:38:48 erm s/TM/TB/ 05:39:13 anyway 05:39:41 ideal plan I guess would be to migrate to i-h-t. but it may depends on its quality and stability etc? 05:40:10 yeah anyway I agree it is not urgent and can wait 05:40:54 okay, we can discuss it too in next meeting what to do for contingency plan anyway. 05:41:10 sure 05:41:18 sure 05:42:48 yes 05:43:18 so back to the topic, please spend some time to have a look at bugzilla for any of your bugs or any interesting bugs in 43 + 6 i18n related bugs. 05:43:59 will try to catch up in next meeting or later if we have time but definitely before EOL. 05:44:07 ok 05:44:16 #topic Input Methods 05:44:59 any updates on IM? 05:46:09 I see some discussion again for the default keybinding issue on bz recently though 05:47:19 yes 05:47:39 ah do you mean gnome bz? 05:47:50 no, our bz 05:47:53 ah 05:48:17 also I saw some discussion about switcher UI in upstream bz 05:48:32 aha 05:49:07 related to ibus gnome integration right? 05:50:37 fujiwarat: talking about switcher UI discussion in gnome bz. can you summarize what's going on? or juhp? 05:51:20 https://bugzilla.gnome.org/show_bug.cgi?id=641531 05:51:37 Currently there is no IME switcher UI in the latest patch although it's provided in ibus 1.5. 05:52:08 Probably I need to ask previous toggle hotkey in the latest patch. 05:52:47 well I saw some questions about why the switch popup is needed and then if so they were saying it should be done using gnome-settings-daemon iiuc 05:53:12 anyway seems to be proceeding at least 05:53:28 Yeah, I'm not sure if they understand the UI. 05:53:41 aha 05:53:54 right - I was going to suggest they try it themselves... 05:54:12 tagoh_, what was the issue about fedora keybindings? 05:54:46 keybinding conflict on eclipse it has been brought up some while ago 05:54:47 I think mclasen also commented that gnome should control the IM shortcuts 05:54:50 ah 05:55:30 any new "developments" there? 05:55:30 as far as I tried on f17, there seems no default assignment to ctrl+space on eclipse though. 05:55:37 aha 05:55:47 I see 05:56:05 https://bugzilla.gnome.org/show_bug.cgi?id=641531#c108 05:56:18 so we can all live happily together now? :) 05:56:22 juhp: one suggestion to rethrow the key event when pressing to ctrl+space. 05:56:23 The 'frontend' means 'initialize'? 05:56:30 aha 05:56:57 fujiwarat, I think frontend means gnome :) 05:57:04 Ah, ok. 05:57:23 juhp: given that we do so, wanted to make sure if UI or anything doesn't conflict to typing. 05:57:26 s/to/the/ I guess 05:57:52 https://bugzilla.gnome.org/show_bug.cgi?id=676102 05:58:09 tagoh_, interesting idea 05:58:40 juhp: yep 05:58:57 though also sounds a little risky :) 06:00:23 "FWIW, Windows 8 uses Windows+Space to switch input sources." 06:00:24 indeed. that would mean application behaves something prior to input. which may be not expected for one who is going to use IM right. 06:01:06 fujiwarat, how is that discussion going? 06:01:15 juhp: aha, interesting. i think earlier they were using "control-shift" or "Alt-shift" 06:01:46 pravins, yeah it might have depended on the language I think 06:01:49 pravins: isn't it to switch the language? 06:01:52 I think it's still on progress. 06:02:02 or IME 06:02:22 fujiwarat, any obstacles? 06:02:58 Currently the latest patch has no default trigger key :(. 06:03:39 tagoh_: it was for input method 06:04:01 I think Windows+space is next/prev trigger key instead of toggle trigger key. 06:05:16 I see 06:05:25 fujiwarat, ok 06:05:59 fujiwarat, but there will be UI to allow setting a trigger key? 06:06:49 is there any impact for other desktops/generic X? 06:07:00 juhp: guess they may want to integrate it into the shortcut settings perhaps? 06:07:17 I think rtcm will notice that issue today. Yes, technically the trigger key can be added. 06:07:48 ok 06:08:16 I'm not sure if IME switcher dialog is implemented or trigger key. I think they need to play f17. 06:08:32 I see 06:08:42 hm, I'll postpone the keyboard layout issue to next meeting since it's not so urgent btw. 06:09:25 anyway, anything more on IM? 06:10:09 tagoh_, sorry was the eclipse issue or something else? 06:10:18 ah ibus? 06:10:38 s/was/was that/ 06:10:47 juhp: adding the unexpected keyboard layout after turning on ibus. 06:10:53 ok right 06:11:39 okay, better move on 06:11:43 #topic Fonts and Rendering 06:12:22 development snapshot of fontconfig is available on rawhide now, which contains various fixes and improvements. fyi 06:12:43 nice 06:13:29 .bug 825104 06:13:31 pravins: Bug 825104 Glyphs of NGA and NYA with vowel signs in Lohit Kannada font are improperly formed - https://bugzilla.redhat.com/show_bug.cgi?id=825104 06:13:31 resolved this 06:13:41 .bug 829143 06:13:44 pravins: Bug 829143 [ta_IN] Fix Rendering of Letter RA,RI,RII per GoTN standards - https://bugzilla.redhat.com/show_bug.cgi?id=829143 06:14:05 didn't still have a time to check the font packages that possibly be warned due to the malformed config files. probably try to do that shortly. 06:14:19 this is interesting one, Unicode has different standard and Tamil Govt. has different :) 06:14:24 pravins: cool 06:14:31 oh 06:14:38 aha 06:14:42 pravins, any resolution? 06:14:42 finally community member came to some consensus :) 06:15:10 Yes, We have presently 2 Tamil fonts. "Lohit Tamil" and "Lohit Tamil Classical" 06:15:17 ah right 06:15:25 hm 06:15:35 Changes specific to Tamil govt. doing in Lohit Tamil 06:15:45 and keeping Lohit Tamil Classical as per Unicode 06:15:56 I see 06:15:56 pravins: which one is default for Tamil? 06:16:08 Lohit Tamil is default 06:16:27 for ta_IN 06:16:52 https://bugzilla.redhat.com/show_bug.cgi?id=829143#c8 this person is from wikipedia 06:16:55 so Gov is more "modern"? :) 06:17:00 is it maybe a good idea to mention in relnotes how to switch the font? 06:17:35 tagoh_: yeah, yesterday replied regarding same on lohit-devel 06:17:38 yes will add it. 06:17:43 great 06:17:52 juhp: yeah, we can say. Or rather govt. does not follow Unicode ;) 06:18:20 While fixing this bug i have optimized Lohit Tamil by removing around 13 glyphs. 06:18:24 okay 06:18:36 hoping to complete this soon. 06:18:53 just wondered if name "Lohit Tamil" would be better for Unicode but I guess it is a detail 06:19:07 #action pravins to add relnotes how to change Lohit Tamil to Lohit Tamil Classical for the default font 06:19:23 tagoh_: fonts-tweak-tool :) 06:19:51 heh. sure 06:20:05 juhp: yeah, i am still not sure. But i think yes we have to support community. 06:20:16 tagoh_: yes, will do it. 06:20:44 okay, anything more? 06:20:57 pravins, well I am just thinking from global perspective (Lohit Tamil and Lohit Tamil Modern) but maybe it is fine, shrug 06:21:25 eg if Lohit Tamil was to be a Unicode reference font... 06:21:43 anyway 06:21:49 just a comment 06:22:27 juhp: yes. i do agree. But same time it is default for ta_IN locale 06:22:36 and same time we do not have any other ta_* locale ;) 06:22:38 but if Classic is new then it doesn't make sense to rename Lohit tamil 06:22:45 I am doing the Lohit Tamil Classical font package review. Was just thinking if this font can be added to lohit-tamil upstream tarball 06:22:55 aha 06:23:44 okay, shall we move on 06:23:47 juhp: i saw the SakalBharati fonts release by Govt. is also following standard defined by Tamil Govt. 06:24:33 paragan: since both Tamil and Tamil Classical are 80% same. I think user will use either of them. So better to have different release tarball and different packages 06:24:34 pravins, or maybe Unicode should be updated? 06:24:59 pravins, ok 06:25:00 juhp: yes exactly. that is what i am to thinking. Need to ask with CDAC once 06:25:05 paragan: thanks 06:25:10 s/to/too 06:25:28 juhp: sounds reasonable since no competitors to keep current one. 06:26:37 #topic Open Floor 06:26:58 okay, any other topics we are missing in the agenda? 06:27:23 guess it would be better bringing something up in next meeting atm ;) 06:29:17 okay, if not, will close the meeting shortly 06:30:07 thanks everyone for the meeting! 06:30:11 #endmeeting