06:32:42 #startmeeting i18n 06:32:42 Meeting started Wed Jan 17 06:32:42 2018 UTC. The chair is paragan. Information about MeetBot at http://wiki.debian.org/MeetBot. 06:32:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 06:32:42 The meeting name has been set to 'i18n' 06:32:43 #meetingname i18n 06:32:43 The meeting name has been set to 'i18n' 06:32:43 #topic agenda and roll call 06:32:43 #link https://fedoraproject.org/wiki/I18N/Meetings/2018-01-17 06:32:45 hi.. 06:32:48 ☺ 06:32:52 hi 06:33:23 hello 06:33:25 hi 06:33:57 hi 06:34:08 let's start 06:34:28 hi 06:34:43 hi 06:35:42 hi all 06:35:54 #topic Upcoming schedule 06:35:54 #info 2017-11-14 Fedora 27 Release 06:35:54 #info 2018-01-09 Change Checkpoint: Proposal submission deadline (System Wide Changes) 06:35:54 #info 2018-01-09 Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild) 06:35:54 #info 2018-01-30 Change Checkpoint: Proposal submission deadline (Self Contained Changes) 06:35:55 #info 2018-01-31 Mass Rebuild 06:36:07 so the current schedule is this 06:36:26 Change proposal submission is going on 06:36:47 I think mostly we are done with Change submission which we will discuss in next topic 06:37:07 https://fedoraproject.org/wiki/Changes/ChineseDefaultFontsToNoto 06:37:21 * epico will submit it later. 06:38:35 thanks epico 06:38:49 welcome 06:38:57 let's move 06:38:58 #topic No assignee issues 06:38:59 #info #83: Tracker for Fedora 28 Changes (pnemade) 06:38:59 #link https://pagure.io/i18n/issue/83 06:39:10 so I have created per Change tickets today 06:39:29 these are from tickets 87 to 91 06:39:48 I have also assigned Change owners as these ticket owners 06:39:51 ah thanks! 06:42:21 so is there anyone want to discuss anything about Changes here? 06:42:40 hopefully all the Changes will get completed on time and soon 06:43:14 when do we plan to have the fonts changes in place? 06:43:37 particularly JK :) 06:44:11 petersen: I'm planning to finish my work in this month 06:44:41 great 06:44:50 so can be tested earlier 06:45:06 are the mono fonts different between adobe and noto? 06:45:17 tagoh_: that would be really good 06:46:46 cool 06:47:12 if no more questions on this ticket then we can move to next ticket 06:47:25 petersen: strictly speaking no mono fonts in Source Han. 06:47:58 it has now... 06:48:26 it is called HW. 06:48:36 https://github.com/adobe-fonts/source-han-sans/tree/release/OTF/SimplifiedChineseHW 06:51:20 what does HW stand for? 06:51:28 * epico dunno. 06:51:37 guess half width? 06:52:07 ah 06:52:15 hmm, that looks like not monospace 06:52:32 aha 06:52:40 the document says: Font resources that include "HW" in their names use half-width glyphs for ASCII by default. 06:52:49 they don't mention about mono for HW at all 06:53:55 maybe relevant to the ambiguous characters in Unicode? 06:53:59 dunno 06:55:14 it looks like the monospace in noto-cjk fonts. 06:57:24 tagoh_: isn't it implied? :) 06:58:31 petersen: I don't think so... non-ascii must have fixed width also in monospace. 07:01:14 hmm okay, I dunno 07:01:33 to me can't be half-width without being monospace but icbw 07:02:01 * epico think so 07:02:03 maybe ascii means Latin here? :) 07:02:29 seems worth testing anyway - though Noto should be fine 07:02:35 Just curious how they compare 07:02:45 they may be identical even?? 07:02:48 for instance, Adobe clearly says the Source Code Pro is a monospaced font. no need to imply anything. they could say it is if that is true 07:02:57 that is true 07:03:07 I don't think it is clear though 07:03:57 the distinction is minor minor anyway IMHO 07:04:06 erm s/minor// 07:04:27 Code Pro has quite limited coverage I guess 07:04:38 right 07:04:41 I mean compared to the CJK fonts 07:04:54 anyway let's move on :) 07:05:19 we are discussing something that can be easily tested :-) 07:05:31 and adobe has Source Han Code JP for japanese monospaced font. dunno why they didn't release it as a part of Source Han though 07:05:42 tagoh_: right I wondered too 07:06:14 how about CN and KR? 07:07:00 no 07:10:51 okay 07:12:40 Maybe good to have some wiki page if we are comparing some fonts about their comparison 07:12:54 true 07:13:27 actually some scripts to generate screenshots for different fonts would be nice 07:13:59 well script to generate for a given font I mean 07:14:00 hm okay 07:15:02 I think we have some package fntsample 07:15:24 hm, dunno. we want to package HW too? at this moment we don't have them in Fedora right? 07:15:46 are they released? 07:16:44 there seems zip available. 07:18:55 Okay we can continue discussion later on. Let's move to next issue 07:19:08 #info #82: Fedora 28 i18n test day (pnemade) 07:19:08 #link https://pagure.io/i18n/issue/82 07:19:33 I am not sure if we have any updates here to discuss 07:19:48 if not I will keep this pending again for next meeting 07:22:22 Is there more to discuss around the date? 07:22:46 Well 13th March or 5th April 07:25:27 I am still voting for 5th April (More late more updates get tested though I accept we get less time to fix and test but then we can request as a blocker/exception) 07:25:55 it also means more time for preparation. 07:26:13 but if rest team thinks early testing is good then 13th March also okay 07:26:53 * pravins checking schedule of Fedora 07:27:30 Beta Freeze is happening on 6th March 07:28:17 Why to wait till 5th April then? We can extend Window of test day 07:28:26 anyway, we never complete all testing on 1st day 07:28:38 i think, good to go for 13th Marc 07:28:41 March 07:29:16 Please note many important changes lands around Beta release 07:29:32 There may be slip 07:29:35 but anyway early testing is always good 07:29:39 true 07:29:48 if we are unable to decide then I am going to mark 07:29:52 I am okay either way - as long as we get lots of testing :) 07:29:57 13th March as our test day 07:30:07 if we start early, we can get more testing :) 07:30:17 may depends how many exceptions has been made after the freeze to break it. 07:30:25 if it slips, then can we slip test day as well? 07:30:53 pravins, yes that is why do test day as late as possible 07:31:22 I think we should target dates not milestones 07:31:37 as we are anyway using the recent working Live iso for testing 07:32:05 * petersen has to go to a meeting now 07:32:30 if there was too much that "freeze" is meaningless in fact, better wait for the beta release perhaps. otherwise we could assume less drastic changes after freeze. 07:32:58 and good to have more time for fixing then. 07:33:08 in that sense I'd vote on earlier testing 07:33:41 thanks. I am going to mark our decision as 13th March as i18n test day. 07:33:57 tagoh_: good point. !! 07:34:10 paragan: 👍 07:34:35 #info we decided today 13th March as F28 i18n test day 07:35:51 #info #84: Fedora 26 Bug triaging (pnemade) 07:35:51 #link https://pagure.io/i18n/issue/84 07:36:04 still there are many bugs 07:36:28 bug list is at https://da.gd/sFmG 07:37:03 keep triaging and fixing them 07:37:06 :) 07:39:28 #topic Open Floor 07:39:35 anything to discuss here? 07:40:06 if not will close the meeting. Thanks all who came to this meeting :) 07:43:21 #endmeeting