06:03:34 #startmeeting i18n 06:03:34 Meeting started Thu Apr 11 06:03:34 2013 UTC. The chair is tagoh_. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:03:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:03:34 #meetingname i18n 06:03:34 The meeting name has been set to 'i18n' 06:03:34 #topic agenda and roll call 06:03:35 #link https://fedoraproject.org/wiki/I18N/Meetings/2013-04-11 06:03:48 shall we have i18n meeting 06:03:52 Hi! 06:03:59 Hi 06:04:19 hi 06:04:33 hi guys 06:04:56 hi 06:05:13 hi 06:08:10 okay, let's get started. 06:08:28 hi 06:08:33 #topic Upcoming schedule 06:08:33 #info 2013-04-11 Test_Day:2013-04-11_Translation_(l10n) 06:08:34 #info 2013-04-16 Alpha Release 06:08:58 as you may read an announcment, today's l10n test day 06:09:30 good to join and test for your primary language 06:09:57 https://fedoraproject.org/wiki/Test_Day:2013-04-11_Translation_(l10n) 06:10:37 not sure may be it got postponed in India due to festival 06:11:17 well, it's not available today only. you can go through testing any time of course. 06:13:22 okay, move on. 06:13:27 #topic Outstanding topics 06:13:27 #info #16: Improving testcases/matrix for i18n test day (tagoh) 06:13:27 #link https://fedorahosted.org/i18n/ticket/16 06:13:37 http://fedoraproject.org/wiki/Test_Day:2013-05-02_Localization_(i18n) 06:14:46 anyone tried to update test cases? 06:15:11 as I mentioned in last meeting, you need to finish it by April 24 06:15:41 epico: any chance to draft zh-TW test case for IM btw? 06:16:00 https://fedoraproject.org/wiki/QA:Chewing 06:16:30 just added it. 06:16:39 aha, thanks! 06:16:55 welcome 06:17:05 can you add it to the test day page too? 06:17:22 which page? 06:17:37 see above :) 06:18:06 in Input (language-specific) section 06:18:44 thanks, I see. 06:19:57 anything else about test day stuff? 06:20:51 okay, add it. 06:20:57 s/add/added/ 06:20:59 epico: cool 06:21:24 okay, move on then. 06:21:46 #info #18: F19 i18n docbeats (tagoh) 06:21:46 #link https://fedorahosted.org/i18n/ticket/18 06:22:01 https://fedoraproject.org/wiki/Documentation_I18n_Beat 06:23:15 fujiwarat: was phuang back from his vacation btw? 06:23:37 tagoh_: No, unfortunately. 06:23:43 I see.. 06:25:09 fujiwarat: how about improved ibus GNOME integration? do you have any mind to add something into relnotes? 06:26:42 Maybe most updates could be bug fixes. 06:27:26 switcher? 06:28:05 dunno if it's worth adding there 06:28:06 Ah, good point. 06:30:00 docbeats is still in draft. so we can discuss and polish later. so maybe good to note anything at this moment if there are. 06:30:35 fujiwarat: if you have anything else, please add. 06:31:12 tagoh_: OK, I see. 06:31:16 thanks 06:31:19 I edited the IM section a bit - please check i didn't introduce any mistakes 06:31:38 juhp: sure. thanks! 06:31:54 Actually switcher GUI was done in ibus-gjs in f17. 06:32:27 fujiwarat, but not in f18 06:32:39 and it was an optional package I think? 06:33:17 juhp: Yes. 06:33:24 it could be a feature in f19 which has been integrated to gnome and available by default 06:33:26 but the new switcher really comes from I guess 06:33:36 + gnome 06:33:47 ok 06:33:51 I think it is worth mentioning anyway 06:33:59 nothing else ? 06:35:15 ah, default keybinding? 06:35:56 Super-Space 06:36:00 right 06:36:05 yes 06:36:33 fujiwarat, basically you can mention any new features since F18 GA 06:36:51 though of course things already in f18 updates might be less exciting 06:37:52 how about IM menu at panel? dunno if it's useful information for users? 06:38:44 hmm true - though it is almost a bugfix ;o) 06:39:07 but it is certainly new compared to f18 06:40:43 okay, anything else? 06:41:24 so might be good to reassure users that IME menus back and whitelist gone 06:41:41 sounds good to me. 06:43:30 if not, shall we move on then? 06:43:52 #topic Open Floor 06:44:11 well, we may want to discuss about 2 exception bugs being proposed? 06:44:24 .bug 927564 06:44:29 tagoh_: Bug 927564 F19 release-name “Schrödinger’s Cat” shown as "SchrA¶dingerâÇÖs Cat" on the linux console - https://bugzilla.redhat.com/show_bug.cgi?id=927564 06:44:29 .bug 949525 06:44:32 tagoh_: Bug 949525 f19 systemd ignores /etc/locale.conf and runs in LANG=C or locale configured in initramfs - https://bugzilla.redhat.com/show_bug.cgi?id=949525 06:45:08 yes they will not be fixed in Alpha alas 06:45:47 aha 06:46:15 there has been a bit of progress on 949525 though it is not completely fixed yet afaict - well maybe come even clearer once systemd-201 going into the repos 06:46:45 bit hard to test completely for install currently 06:46:56 since dracut depends on systemd 06:47:17 The font problem is not yet solved, not even with systemd-201. 06:47:18 also seems dracut should be run later in the install than currently 06:47:22 right 06:47:54 I hope there is no impact for the Translation test day :-| 06:48:15 I see 06:48:22 and I hope we have fix before the i18n one... 06:48:51 running system daemons in LANG=C is unacceptable to me 06:49:12 (for Live installs it is en_US.utf8 at least) 06:49:34 basically whatever is configured in the initramfs 06:50:08 right. we has ever used en_US instead of C 06:52:50 any other impact on this issue? particularly to re-consider to make it exception? 06:55:05 (actually even in f18 systemd itself runs with LANG=C but no child processes) 06:55:29 tagoh_, well it means gdm and g-i-s run in LANG=C 06:55:48 aha 06:55:55 I think that is the main immediate impact 06:56:17 but kind of expect there could be more else where 06:56:27 anyone tested kde? 06:56:35 is it a reason why we see ??? at g-i-s? 06:56:39 right 06:56:53 hmm 06:57:05 mfabian first noticed the LANG=C 06:57:06 is it not a fatal?? 06:57:28 do they know about it? 06:57:29 it was rejected as an Exception even :-( 06:58:09 on the basis of being too late to change systemd 06:58:10 for this 06:58:17 I think it is weird to reject that as an exception, it should be not that hard to fix and it is important. 06:58:19 kind of I think 06:58:25 I agree 06:59:00 disappointing - we need i18n criteria for Alpha and certainly Beta 06:59:46 Live installs are ok though as I mentioned at least 06:59:58 ok = utf8 07:00:23 reading logs of blocker review meeting, they were assuming text are available in English. but actually not. so good to mention at bug and propose it again 07:00:43 I think QA was worried about introducing regressions with a system version bump 07:01:04 tagoh_, aha 07:01:32 good point though guess it affect much less layouts for en_US? 07:01:47 in many languages is unreadable 07:02:03 but you are probably right that they don't fully understand the impact 07:02:29 yeah 07:02:31 the main argument I recall was that it might be fixable by an update but currently that is not true 07:02:54 a kernel update might do it - I haven't tested that 07:03:06 so perhaps 07:03:09 shrug 07:03:31 IMHO it should be blocker but it is not my decision... 07:03:35 anyway, we may need to clarify that 07:03:40 okay 07:04:23 okay, anything else we want to discuss in the meeting? 07:04:36 I can try to re-propose I guess but I don't think they will accept Exception even now - specially if it is not already clearly fixed 07:05:18 may depends on impact they see.. 07:05:20 Go/No-Go meeting is tonight UTC 07:05:28 hmm 07:05:55 to get fixed I think it needs to be accepted as a blocker likely at this stage 07:06:41 all accepted blockers seems in testing now and 5 additional blockers are being proposed btw 07:07:14 http://qa.fedoraproject.org/blockerbugs/milestone/19/alpha/buglist 07:07:34 anyway 07:07:56 mfabian, perhaps you could try to attend the blocker meeting and mention this issue? 07:08:21 juhp: When is the blocker meeting? 07:08:34 ah but it is late for you 07:08:44 When is it? 07:08:55 17:00 EDT I think 07:09:00 Today? 07:09:04 yes 07:09:07 I believe so 07:09:30 but it really need to be proposed 07:09:42 Where is the meeting info? 07:09:46 to get attention 07:09:51 let me try to find it 07:10:06 mfabian, I think it should be announced on fedora test list 07:10:48 http://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting ?? 07:12:03 https://fedoraproject.org/wiki/Go_No_Go_Meeting? 07:12:11 from devel announce. 07:13:12 mfabian, ah 1700 UTC 07:13:16 epico, thanks 07:13:25 np 07:13:29 calendar entry is wrong 07:13:37 thought it was a funny time to have a meeting 07:13:44 Which one, the Go_No_Go_Meeting? 07:13:49 indeed 07:14:06 Fedora 19 Alpha Go/No-Go Meeting, Thursday, April 11 @ 17:00 UTC 07:14:19 mfabian, are you on devel-announce? 07:14:25 mfabian, http://lists.fedoraproject.org/pipermail/devel-announce/2013-April/001135.html 07:14:56 they will have a look at blocker list. so maybe we can mention impact at bz and propose it as blocker perhaps? 07:15:10 tagoh_, right that is the only way 07:15:49 juhp: okay, can you update the bug? 07:15:50 weak side is they basically already reviewed the bug... and fix currently looks partial 07:15:53 okay 07:15:56 juhp: Yes, I am on devel-announce 07:16:36 thanks 07:16:37 maybe I will try to do a net install including 201 07:16:55 if I can talk anaconda into it not sure how to add repos 07:17:33 but to be honest I hate to admit but even i am not sure it is worth delaying Alpha a week for this 07:17:41 juhp: Would that make any difference to how I tested? 07:18:04 (install systemd-201 while gnome-initial-setup displays and reboot) 07:18:05 well it would pull 201 into the install package set itself but I dunno 07:18:23 it would affect the dracut -f in anaconda at least I guess 07:19:08 I was happy to see lennart add 201 to the initial-setup bodhi update but unfortunately it did not slip through ;o) 07:19:48 mfabian, so theoretically it might help but I am also skeptical 07:20:21 okay, let's see how they decide after all 07:20:24 the main problem currently seems to be that anaconda sets locale.conf too late for dracut to pick up 07:20:50 tagoh_, so you see there are probably 2+ packages involved in the fix 07:21:05 aha 07:21:31 so it looks quite unlikely but at least we could alert them again to the problem 07:21:33 I’ll join that meeting today. It is not too late here. 07:21:40 mfabian, thanks! 07:21:51 cool 07:21:56 anything else before closing the meeting? 07:22:17 https://github.com/mike-fabian/lang-table 07:22:22 oh! 07:23:08 aha 07:23:52 looks nice 07:24:10 cool! 07:24:56 No documentation yet, the test cases sort of show how I think it should work: https://github.com/mike-fabian/lang-table/blob/master/test_cases.txt 07:25:36 great 07:26:21 >>> test_language_country(show_weights=False, languageId="de", countryId="CH") # doctest: +NORMALIZE_WHITESPACE 07:26:22 de: ['de_DE.UTF-8', 'de_AT.UTF-8', 'de_CH.UTF-8', 'de_BE.UTF-8'] 07:26:22 CH: ['de_CH.UTF-8', 'fr_CH.UTF-8', 'it_CH.UTF-8', 'wae_CH.UTF-8'] 07:26:22 +: ['de_CH.UTF-8'] 07:26:25 de: ['de(nodeadkeys)', 'de(deadacute)', 'at(nodeadkeys)', 'ch', 'be(oss)'] 07:26:28 CH: ['ch', 'ch(fr)'] 07:26:31 +: ['ch'] 07:26:55 just wonder if there may be similar information in CLDR say? 07:27:20 Line marked with "de" is when only "de" is specified (list of possible locales or keyboards), line marked with "CH" is when only "CH" is specified, lines marked with "+" is when both is specified. 07:27:21 but maybe not everything 07:27:32 tagoh_: I get some of this from CLDR. 07:27:38 aha 07:27:49 There seems to be no useful keyboard information in CLDR. 07:28:09 so is it able to update by script say when they update something? 07:28:50 I get the language names (translations and endonyms) from CLDR, but I think we need to be able to "improve" the language and country names sometimes for political reasons (Taiwan, Israel,...) 07:28:54 or need to maintain by hand? 07:29:27 I want to update it semi-automatically. 07:29:46 sure 07:29:59 semi-automatically because I want to avoid overwriting changes we made for political reasons. 07:30:18 I.e. add new stuff from CLDR we don’t yet have automatically. 07:30:36 But if it is already there and different, just show the difference and decide manually. 07:30:39 yep 07:31:49 The keyboard information (what should be the default keyboard for a language or locale?) needs to be maintained manually at the moment. 07:32:07 ok 07:32:53 nice work anyway 07:33:20 okay, anything else? 07:34:33 if not, let's close the meeting shortly 07:35:52 okay, stop here then. thanks everyone for the meeting! 07:36:00 #endmeeting