15:02:07 RRSAgent has joined #i18n 15:02:12 logging to https://www.w3.org/2024/12/17-i18n-irc 15:02:19 Meeting: I18N ⇔ CSS 15:02:24 rrsagent, make log public 15:02:28 rrsagent, make minutes 15:02:29 I have made the request to generate https://www.w3.org/2024/12/17-i18n-minutes.html xfq 15:02:44 present+ florian, fantasai, atsushi 15:02:49 present+ xfq 15:02:54 scribe: xfq 15:03:00 rrsagent, make minutes 15:03:02 I have made the request to generate https://www.w3.org/2024/12/17-i18n-minutes.html xfq 15:04:04 agenda: https://www.w3.org/events/meetings/3833355b-c0e8-4139-8521-6776fba82f3f/20241217T070000/ 15:04:05 clear agenda 15:04:05 agenda+ Agenda 15:04:05 agenda+ Action Items 15:04:05 agenda+ Info Share and Progress Reports 15:04:05 agenda+ Review on-going issues 15:08:54 zakim, take up item 1 15:08:54 agendum 1 -- Agenda -- taken up [from agendabot] 15:10:31 fantasai: I filed an issue about trying to start a document for text edges 15:10:46 ... to describe the text edges of different writing systems 15:11:10 https://github.com/w3c/csswg-drafts/issues/11384 15:11:12 https://github.com/w3c/csswg-drafts/issues/11384 -> Issue 11384 [css-fonts-5][css-inline-3] Text Edge Metrics Registry (by fantasai) [css-inline-3] [i18n-tracker] [css-fonts-5] [Agenda+ i18n] 15:11:18 agenda+ ext edges of different writing systems 15:11:32 atsushi has joined #i18n 15:11:37 zakim, close this item 15:11:37 agendum 1 closed 15:11:38 I see 4 items remaining on the agenda; the next one is 15:11:38 2. Action Items [from agendabot] 15:11:40 zakim, take up item 2 15:11:40 agendum 2 -- Action Items -- taken up [from agendabot] 15:11:56 https://github.com/w3c/i18n-actions/issues?q=is%3Aissue+is%3Aopen+label%3Acss 15:12:20 #120 15:12:21 https://github.com/w3c/i18n-actions/issues/120 -> Action 120 add dicussion document to i18n-discuss repo of seeking font metrics for various writing systems (on frivoal, fantasai) due 2024-09-24 15:13:07 florian: work in progress 15:13:11 ... fantasai filed an issue 15:13:23 fantasai: I think we can register several writing systems 15:13:35 ... then at a point we can start to build a document with them 15:13:37 s|an issue|issue https://github.com/w3c/csswg-drafts/issues/11384 15:13:52 ... but I described all the fields we would need in each registry entry 15:14:02 ... I think ideally we will co-publish this 15:14:31 florian: do you think we need a formal registry or do we need something vaguely registry shaped? 15:14:40 fantasai: it doesn't need to be a formal one 15:15:25 fantasai: one benefit of doing it as a registry is we can say that any member of CSSWG or i18n or the Team can just add things 15:15:41 ... we don't have to get WG consensus to republish stuff 15:16:32 florian: I don't really know how long we need this because if OpenType start dealing with this kind of problem in their fonts hopefully they take over the whole problem and just deal with it correctly 15:17:14 fantasai: technically this applies to formats other than OpenType 15:17:19 florian: true 15:17:45 ... to bootstrap this, I think off the top of my head, clearly there's Hebrew to be documented 15:18:02 ... I think Thai also fits there 15:18:59 fantasai: we're not asking ourselves to figure this out, we're asking graphic designers to figure it out 15:19:24 florian: I'm not sure that in all languages we'll find definitive answers 15:19:37 ... there might be disagreements but that's fine as well 15:21:01 xfq: sounds useful 15:21:14 #116 15:21:15 https://github.com/w3c/i18n-actions/issues/116 -> Action 116 sort out the various categories of things that get autospaced with koji (on frivoal, fantasai) due 2024-08-27 15:21:46 florian: we talked about this one in a CSS call recently 15:22:07 fantasai: we got agreement to incorporate this into the CSS spec but the edits haven't been done yet 15:22:41 florian: I think in particular we had agreements that we will use Unicode, but we didn't have full agreement about the exact details 15:23:00 fantasai: the main thing we didn't have agreement on is what is the default behaviour 15:23:16 ... Unicode says the default behaviour is not to auto space 15:23:25 ... but CSS might want to say that you do it all the time 15:24:20 fantasai: character lookups are not that fast 15:24:33 ... but if we can do it fast enough, then hopefully we can make it the default 15:30:11 florian: @@1 15:30:29 ... I think Unicode tells us without categorization 15:30:45 ... they do not divide them between alphabetic and numeric 15:31:08 ... we need to have another look at what Unicode is doing and if they have any symbols in there 15:31:56 florian: I didn't review the detail of the Unicode proposal 15:34:28 zakim, close this item 15:34:28 agendum 2 closed 15:34:29 I see 3 items remaining on the agenda; the next one is 15:34:29 3. Info Share and Progress Reports [from agendabot] 15:34:33 zakim, take up next 15:34:33 agendum 3 -- Info Share and Progress Reports -- taken up [from agendabot] 15:35:04 agenda? 15:35:22 zakim, close this item 15:35:22 agendum 3 closed 15:35:23 I see 2 items remaining on the agenda; the next one is 15:35:23 4. Review on-going issues [from agendabot] 15:35:27 zakim, take up item 4 15:35:27 agendum 4 -- Review on-going issues -- taken up [from agendabot] 15:35:55 https://github.com/w3c/csswg-drafts/issues/11257 15:35:56 https://github.com/w3c/csswg-drafts/issues/11257 -> Issue 11257 [css-text-decor] Control the line height of text containing emphasis marks (by xfq) [css-text-decor-3] [css-text-decor-4] [i18n-tracker] [i18n-jlreq] [i18n-clreq] [i18n-klreq] [i18n-mlreq] 15:37:45 [xfq introduces the issue] 15:38:10 fantasai: this is not the font's fault because currently this is specced just like ruby 15:38:29 ... I can't remember whether it's defined to increase the line height or not 15:39:13 ... it might make sense for us to change the rule somehow to be less dependent on the font by using a metric 15:39:51 ... I think the thing we probably want to do is there's a proposal for a new property called line-fit-edge 15:40:17 ... we'll probably want to use that metric for measuring where emphasis marks and ruby go 15:40:24 ... rather than the ascent 15:41:07 https://bug-239693-attachments.webkit.org/attachment.cgi?id=458218 15:42:03 florian: might be a bit too many links to follow to get to the answer so you could post a follow-up comment in the CSS issue 15:43:24 florian: this is too detailed for me to figure it out on the fly and I have to slow down and read the issue closely 15:43:38 fantasai: I guess another question is where are we at with ruby 15:43:50 florian: I haven't touched it in a while 15:43:56 ... we have a first draft 15:44:39 fantasai: did we initiate wide review? 15:44:41 florian: yes 15:44:52 fantasai: once we address the comments we can just go to CR 15:45:14 florian: TAG and privacy review completed 15:46:22 https://www.w3.org/PM/horizontal/?repo=w3c/i18n-activity#HTML%20Ruby%20Markup%20Extensions 15:46:44 ... security and accessibility no answer 15:47:00 florian: need to wrap it up 15:48:50 action: fantasai to look into the line height of text containing emphasis marks, CSSWG issue # 11257 15:48:58 Created -> action #151 https://github.com/w3c/i18n-actions/issues/151 15:49:16 agenda? 15:50:29 rrsagent, make minutes 15:50:31 I have made the request to generate https://www.w3.org/2024/12/17-i18n-minutes.html xfq 17:30:41 r12a has joined #i18n