05:04:22 #startmeeting i18n 05:04:22 Meeting started Tue Oct 27 05:04:22 2009 UTC. The chair is tagoh3. Information about MeetBot at http://wiki.debian.org/MeetBot. 05:04:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 05:04:37 https://fedoraproject.org/wiki/I18N/Meetings/2009-10-27 05:04:51 hi 05:04:51 hi 05:04:53 I'm chairing today's meeting 05:05:31 who's here today? 05:05:44 hi 05:06:09 hi 05:07:05 ping phuang, fujiwarat, 05:07:32 hi 05:07:36 hi 05:07:54 let's get started 05:08:05 #topic F12 05:09:16 well, 12-beta has been out. and RC will be coming soon. please keep your hard work to find out any critical issues on beta and improve them on RC hopefully 05:10:16 yeah I think f12 i18n is looking reasonably good - still I don't see any major issues currently? 05:10:28 s/still/at least 05:10:44 we have about one week for RC (Nov 4 is on the schedule) 05:11:53 juhp: the keyboard issue on gdm seems to be gone - I haven't tried the fixed package yet though 05:12:00 aha 05:12:17 right 05:12:28 that's good then 05:13:20 any concerns on this topic? guess we could say something on the bugs topics later perhaps 05:13:52 yeah, we will get some on test day 05:13:57 yeah - I should probably have added TestDay at the end 05:14:18 pravins: likely :) 05:14:26 ok, let's talk about bugs first then. 05:14:41 #topic bugs 05:15:27 no blocker bugs for i18n related and some target bugs 05:17:00 we need to check for F12Target and F12Blocker bugs 05:17:46 paragan: sure. may missed any bugs without Cc'ing fedora-i18n-bugs 05:18:51 well turns out there is one s-c-l bug cloned off a F12Blocker 05:19:13 .bug 530698 05:19:15 juhp: Bug 530698 firstboot errors when loading modules: language module - https://bugzilla.redhat.com/show_bug.cgi?id=530698 05:19:18 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=530698 high, high, ---, psatpute, ASSIGNED, firstboot errors when loading modules: language module 05:19:19 Bug 530698: high, high, ---, psatpute, ASSIGNED, firstboot errors when loading modules: language module 05:19:31 sorry doh - did it wrong again ;) 05:20:22 seems the direct list does not show blockers of blockers... 05:20:36 aha 05:21:31 just need to add it to F12Blocker too? 05:21:57 not sure when that started happening - think firstboot has been crashing for a while perhaps or was at least 05:22:08 dunno 05:22:18 i think but this will be quicj fix 05:22:27 s/quick 05:22:43 dunno if I saw that crash when I tried to install beta 05:23:13 ok 05:24:17 does it just work but output the error messages? 05:24:36 maybe? 05:25:26 aha. I've not paid more attentions on the console 05:26:40 anyway I can't see more i18n issues on the blocker list 05:26:58 anything concerns on i18n bugs to discuss now? 05:28:20 QT 05:28:23 that may be good to revisit other i18n bugs if you have a time - we have over 100 bugs. may need to triage them 05:28:33 i have seen some bug for indic in qt 05:28:57 pravins: bug number? 05:29:01 rendering is not working at all, all thing look broken 05:29:07 oh 05:29:29 pravins: is it in bz? 05:29:36 yes 05:30:01 bug 528303? 05:30:03 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=528303 medium, low, ---, than, NEW, [ml_IN] Rendering of cons+virama+ra is wrong in KDE 05:30:15 yeah, thanks 05:30:27 pravins: is it just ml? 05:31:05 yes 05:31:22 i have seen, some time back with l1on, but looks they have not filed 05:31:34 i have requested them to file 05:32:22 hm 05:32:28 pravins: more bugs? :) 05:32:42 they will file soon 05:32:52 i think we will get some in test day 05:32:58 ok 05:33:17 I think Ani was keen on contributing to TestDay 05:33:26 yes 05:33:47 bug 530085 05:33:48 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=530085 medium, low, ---, mclasen, NEW, [or_IN] - Editor's Title appearing with Underline for Oriya Lohit Fonts (Default Fonts) 05:34:30 tagoh3: this is same we discussed last time 05:34:44 but now in this case there is no fontconfig file as well 05:34:53 pravins: aha 05:35:04 hmm 05:35:31 guess "editor" in summary is misleading? 05:36:08 this bug is not appearing in gnome, but in KDE 05:36:21 and i saw with firefox title bar as well 05:36:27 pravins: have you tried to see with other ml fonts as I suggested before? 05:36:31 oh 05:37:05 thing is good now with ml fonts, as we modified fonconf file for smc 05:37:45 pravins: which applications you use doesn't matter because the title bar is managed under the window manager. 05:38:10 * juhp updated the summary :) 05:38:12 aha 05:38:25 bug 530085 05:38:26 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=530085 medium, low, ---, mclasen, NEW, [or_IN] - window titles appearing with Underline for default Oriya Lohit Font 05:39:21 is it still the theme issue? 05:39:28 confused by "KDE" though 05:39:51 i think so 05:40:03 pravins: default theme is ok? 05:40:07 no 05:40:13 ok 05:40:37 sorry but seems quite a bit of noise in the report 05:41:31 hmm, but dunnon why problem happens with with Kwriteand firefox application 05:41:44 pravins: 530085 is appearing on kde only but not on gnome? - I'm getting confused. 05:41:58 kde apps 05:42:00 me too since it is against gnome-themes 05:42:01 like kwrite 05:42:04 on gnome? 05:42:13 yeah, on gnome try open kwrite 05:42:21 or firefox 05:42:26 hmm 05:42:30 how about kwrite on KDE say? is it ok? 05:42:51 * pravins checking 05:42:58 app toolkit should not affect window decor 05:43:21 unless the font itself is buggy ;) 05:43:34 :) 05:44:26 pravins: but gnome-terminal also has the line 05:44:38 yeah 05:45:11 but nautilas not, i am still confused why its no in consistent 05:45:43 s/no in consistent/inconsistent 05:45:47 pravins: just seems to depend on the font used in the title no? 05:46:22 hmm 05:46:41 does it make sense to reassign to lohit-oriya-fonts until it is fully triaged? 05:47:26 ah 05:47:36 juhp: looks good, though i have tried something with fonts 05:47:41 i will try littlebit more 05:47:51 might be some fonts attribute making problem 05:47:55 thanks 05:48:01 ok 05:48:53 anything else we want to talk about on bugs? 05:49:28 let's move on if nothing else. 05:50:31 #topic test day 05:50:50 okay I can update a little 05:51:00 juhp: thanks 05:51:06 the event is this Thu! 05:51:15 in two days time... 05:51:31 I think we don't need any more modification in test cases right? 05:52:01 I think the testpage is getting there - should be closer to finished now - planning to do a bit more consolidation and simplifying of the testcases 05:52:11 jlaska seems need some more input there 05:52:22 paragan: well I think we might yes 05:52:25 yup 05:52:36 IMHO current test cases looks good 05:52:43 ok 05:52:50 but I feel 6 is too many? 05:53:37 well it doesn't have to be absolutely perfect but I feel they could be improved a bit more... 05:53:39 not sure if people will get confused by 1st and 2nd test cases 05:53:49 hehe 05:53:54 and also from 5th and 6th 05:54:07 some might feel they looks similar 05:54:16 indeed... 05:54:26 got ibus bugs to im-chooser last time :) 05:54:26 hence my comments but anyway 05:54:36 aha 05:55:24 anyway would appreciate people looking over them by tomorrow and sanity-checking itself 05:57:06 juhp, sure 05:57:13 do we need to have separate test case for the browser? 05:57:22 should I talk through the testcases provided by Rui He? 05:57:34 tagoh3: good question - maybe not... 05:57:50 though browser printing is pretty important I guess 05:58:27 I should have mentioned https://fedoraproject.org/wiki/Test_Day:2009-10-29 05:59:10 so I will try to cleanup a little more and then ask you guys to review and check 05:59:11 juhp: right - since we are expecting people to test the rendering, the inputting and the printing, it may be good enough to have those three cases instead of 6? if we want to simplify it 05:59:15 juhp, I guess we can have browser testcase for checking rendering in firefox, konqueror and then printing from it 05:59:22 right 05:59:49 I 3 or 4 testcases may be sufficient hopefully 05:59:52 I hope 06:00:10 yesterday I just massaged them a bit... 06:00:41 and also trying to get fedora-l10n (FLP) to participate :) 06:01:02 cool 06:01:30 oh one more question: about the results... 06:01:44 currently it is split by good/bad 06:02:00 copied from an earlier testday 06:02:25 I guess it helps to clarify feedback though might also mean two entries required 06:03:20 also simpler columns than last time 06:04:15 but since it is a bit more open ended this time maybe it is ok... 06:04:26 that is about it I think 06:05:07 two entries? 06:05:25 anyway at the end of the day I guess the bug reports generated is most interesting but it is also good to have people testing our work 06:05:43 tagoh3: as in two separate tables 06:06:08 Problems identified and Just worked 06:06:10 currently 06:06:18 juhp: people just need to put into either of them? 06:06:43 well hopefully not everything will fail or succeed :) 06:07:00 aha 06:07:18 hmm maybe it is too conspicuous dunno 06:07:37 are you suggesting to have detailed result page per testcases then? 06:07:38 and people will be shy to separate the problems so we might combine them? 06:08:36 yeah so different testdays seem to use different result formats depending on what is appropriate I guess 06:08:59 one even has script and testers would upload the output 06:09:35 aha 06:09:46 hmm let's see how things like after revising the testcases I guess 06:10:22 ok, we could improve in next testday then. 06:10:58 yeah 06:11:41 ok, anything else to discuss? 06:13:24 can't think of anything else :) 06:13:39 that's everything on the agenda so far. if no one has any topics anymore, let's close the meeting 06:14:11 thank you for the meeting, everyone. 06:14:30 thanks tagoh3 06:14:40 #endmeeting