13:48:25 RRSAgent has joined #i18n 13:48:25 logging to https://www.w3.org/2022/04/14-i18n-irc 13:48:37 trackbot, prepare teleconference 13:48:40 RRSAgent, make logs public 13:48:43 Meeting: Internationalization Working Group Teleconference 13:48:43 Date: 14 April 2022 13:48:45 agenda: https://www.w3.org/events/meetings/83b1d2d3-7389-437a-b0d5-32441827a9a3/20220414T150000 13:48:45 clear agenda 13:48:45 agenda+ Agenda Review 13:48:45 agenda+ Action Items 13:48:48 agenda+ Info Share 13:48:50 agenda+ RADAR Review 13:48:51 Chair: Addison Phillips 13:48:52 agenda+ Pending Issue Review 13:48:55 agenda+ AOB? 13:50:01 agenda+ request to approve preparation of new WG Note for English ruby terminology and to have a new repository 13:50:14 Regrets: Fuqiao 13:57:33 JcK has joined #i18n 13:58:24 present+ Addison, Atsushi 13:58:29 present+ JcK 14:03:51 present+ Bert 14:04:16 scribe: atsush 14:04:19 scribe: atsushi 14:04:22 scribe- atsush 14:04:27 zakim, take up agendum 1 14:04:27 agendum 1 -- Agenda Review -- taken up [from agendabot] 14:04:30 agenda? 14:04:41 Najib has joined #i18n 14:05:49 zakim, take up agendum 2 14:05:49 agendum 2 -- Action Items -- taken up [from agendabot] 14:05:49 addison: noticed about github repository for idn/http 14:06:06 https://www.w3.org/International/track/actions/open 14:06:34 addison: 1094, depends on TAG 14:06:58 addison: 1133, not yet done, need some time for update 14:07:05 ... 1134, will work this week 14:07:10 addison: 1137? 14:07:23 r12a: have to go back to the discussion last week 14:07:29 addison: saw comment on the issue 14:07:54 r12a: did comment on the thread, will follow later 14:08:11 addison: 1138, i did and all of them were satisfied, and closed 14:08:18 action-1138? 14:08:18 action-1138 -- Addison Phillips to Check indexeddb issues -- due 2022-04-14 -- OPEN 14:08:18 https://www.w3.org/International/track/actions/1138 14:08:22 close action-1138 14:08:22 Closed action-1138. 14:08:30 zakim, take up agendum 3 14:08:30 agendum 3 -- Info Share -- taken up [from agendabot] 14:09:14 https://w3c.github.io/i18n-drafts/articles/ruby/styling.en 14:09:28 r12a: link above, an article, last update 2016 14:09:36 ... started working on this again, this week 14:09:45 ... haven't posted updates yet 14:10:19 addison: what is focus on your revision? 14:10:38 r12a: first section is for basic configurations, what you will do what will happen 14:10:54 ... tends how Japanese use, and Chinese uses 14:11:08 ... following sections are tweaks, like below or above 14:11:33 ... trying to a bit more information, about when you will do rather than just you can, for reason you want to do 14:11:49 ... syntax on test on your browser, more inline like MDN docs 14:12:10 ... plus, updating information what browsers support 14:12:43 ... rb parsing also on Chrome, so update with that information 14:13:02 ... havn't updated along with MDN docs 14:13:49 addison: cool to have tests in the page. people can check with these 14:14:01 r12a: not hard to do, just to place things 14:14:16 zakim, take up agendum 4 14:14:16 agendum 4 -- RADAR Review -- taken up [from agendabot] 14:14:24 https://github.com/w3c/i18n-request/projects/1 14:14:56 r12a: I know people are discussing on ruby terminology, not to stop these, but back them later 14:15:06 addison: no new request for review 14:15:24 ... xfq put number of pending issues on webgpu, wait for next week 14:15:38 addison: SPC, got email to set phone call later today 14:15:54 ... expect to move this item somewhere else 14:16:07 addison: any resolution? 14:16:37 addison: CSS-cascade, in 2020, to mark as closed - all issues closed 14:16:50 addison: no objection, move to completed 14:17:02 addison: also for css-logical 14:17:26 agenda? 14:17:37 zakim, take up agendum 7 14:17:37 agendum 7 -- request to approve preparation of new WG Note for English ruby terminology and to have a new repository -- taken up [from addison] 14:17:47 scribe+ 14:17:55 present+ 14:18:01 atsushi: reported last week, in JLTF call this week 14:18:05 ... discussed ruby terminology 14:18:15 ... most attendees have some reaction to japanese terminology 14:18:22 ... not so interested in English 14:18:31 ... most positions neutral, but okay to proceed 14:18:45 ... kida-san is performing last review on explainer on terms we want to propose 14:19:06 ... want to propose to have separate draft of WG-Note and want new W3C repo 14:19:20 ... not easy to a list of terms, one term with short description 14:19:45 ... concluded to propose to start drafting dedicated document 14:19:56 https://github.com/w3c/jlreq/pull/331 14:19:59 richard: link to the text? 14:20:06 atsushi: ^^^ 14:20:29 atsushi: once new repo, seek comments from wider community including clreq and css 14:21:09 richard: not sure about having separate repo 14:21:17 ... might want to integrate with i18n-glossary 14:21:32 ... helpful to have examples and a bit more than we'd have in glossary 14:21:40 https://www.w3.org/International/questions/qa-ruby.en 14:21:42 ... one is that we have an article "what is ruby" 14:21:56 ... it's a short article, but has some on japanese ruby 14:22:18 ... article I mentioned in info share and its companion have some examples 14:22:37 ... another possibility is that rather than writing a new document that we write an article 14:22:56 ... we have essential concepts for character encoding, other topics, could have one 14:23:43 addison: is the goal to have something in the TR space?? 14:23:57 atsushi: want to refer to definitions from css-ruby 14:23:57 https://www.w3.org/International/articles/ruby/markup.en#mono_group_etc 14:24:15 ... glossary is one possibility, but something in /TR is desired 14:25:37 richard: definitions need to cover japanese, chinese, and mongolian 14:25:44 ... possibly not Korean but maybe 14:26:02 atsushi: for this time we want to have language-independent 14:26:17 ... something in simple-ruby is not in our scope 14:28:24 addison: don't want to force it; using japanese words is okay if there is nothing better (cf. mojibake, ruby) 14:28:44 richard: some other examples.... at bottom 14:29:02 ... we've been calling this "tabular ruby" (calls out "layered") 14:29:16 I have made the request to generate https://www.w3.org/2022/04/14-i18n-minutes.html addison 14:29:56 atsushi: murata-san's idea was concept independent, not sure where want to go 14:30:20 richard: when it comes to things like 'para ruby', might be useful, move away from japanese because not explanatory 14:30:32 ... making more general so fits other languages is a good goal 14:30:50 ... people who find it think it can be used for glossing text in any language 14:31:00 ... any interlinear == ruby is not a good idea 14:31:01 fantasai has joined #i18n 14:31:10 ... move a little way but not too far 14:31:19 I have made the request to generate https://www.w3.org/2022/04/14-i18n-minutes.html addison 14:31:40 atsushi: have both terms, interlinear and ruby? some people complain about mixing 14:32:13 ... at this moment want broad terms 14:32:23 s/broad/brought/ 14:32:45 present+ 14:32:58 I have made the request to generate https://www.w3.org/2022/04/14-i18n-minutes.html fantasai 14:34:01 ack fantasai 14:34:23 fantasai: want to mention if this were a doc on the TR pages 14:34:43 ... no opinion if in glossary or in a standalone doc 14:35:04 ... useful to have explanation with terms 14:35:35 richard: were talking about alternatives, we have an article that explains ruby 14:35:39 ... 2 more about styling et al 14:35:47 ... these are other things we can look at 14:36:04 ... have to have this terms in the i18n-glossary, but it's just a link source, not a doc you'd read 14:36:13 ... glossary can point out to docs 14:36:27 (addison points out that it *does* point out) 14:36:51 fantasai: murata-san's goal is to have it ref from jlreq, clreq, etc. plus outside W3C 14:37:08 richard: that's what glossary is 14:39:54 i18n-glossary 14:39:54 https://github.com/w3c/i18n-glossary/ 14:40:35 richard: too generalized is not helpful 14:40:38 “intermittent ruby” 14:41:12 ... some sort of term like maybe "inline annotation" 14:41:26 ... mechanism in ja/zh/etc. is ruby 14:41:50 fantasai: try to draft a pull request 14:42:06 richard: ruby is a technique for doing inline annotations 14:42:20 ... it's a *way* of doing it 14:46:14 action: atsushi: convert ruby terminology to wiki page for direct comments and track progress for i18n 14:46:14 Created ACTION-1139 - Convert ruby terminology to wiki page for direct comments and track progress for i18n [on Atsushi Shimono - due 2022-04-21]. 14:58:50 zakim, take up agendum 6 14:58:50 agendum 6 -- AOB? -- taken up [from agendabot] 14:59:39 I have made the request to generate https://www.w3.org/2022/04/14-i18n-minutes.html addison