14:04:16 RRSAgent has joined #i18n 14:04:20 logging to https://www.w3.org/2024/10/15-i18n-irc 14:04:26 florian: there are some things we can do for latin 14:04:33 ... that we cannot do for other langs 14:04:51 ... for CJK, Hebrew, Thai, other SEA languages, etc. 14:05:03 ... there isn't a font metrics that corresponds to the top of the letters 14:06:03 fantasai: there's an official liaison statement on behalf of @@ to the opentype group at ISO 14:06:21 ... I believe Chris sent 14:06:41 florian: in that case the action item on fantasai and me to do a write up is not appropriate 14:07:04 ... because the write up has happened 14:07:13 ... an interesting question is then waht? 14:08:59 https://www.mpeg.org/standards/MPEG-4/22/ 14:16:52 https://github.com/w3c/i18n-actions/issues/116 14:16:53 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 14:17:03 xfq: haven't looked at koji's issue in detail yet 14:17:27 https://github.com/w3c/csswg-drafts/issues/11013 14:17:28 https://github.com/w3c/csswg-drafts/issues/11013 -> Issue 11013 [css-text] Use the Unicode East Asian Auto Spacing for `text-autospace` (by kojiishi) [Agenda+] 14:18:17 rrsagent, make log public 14:18:19 rrsagent, make minutes 14:18:21 I have made the request to generate https://www.w3.org/2024/10/15-i18n-minutes.html xfq 14:18:28 present+ fantasai, florian, xfq 14:18:28 scribe: xfq 14:18:49 rrsagent, make minutes 14:18:50 I have made the request to generate https://www.w3.org/2024/10/15-i18n-minutes.html xfq 14:19:09 Meeting: I18N ⇔ CSS 14:19:12 rrsagent, make minutes 14:19:13 I have made the request to generate https://www.w3.org/2024/10/15-i18n-minutes.html xfq 14:19:36 fantasai: maybe we should set up a work session about that 14:21:05 Topic: interaction between bidi and text-autospace 14:21:15 https://github.com/w3c/csswg-drafts/issues/10803 14:21:16 https://github.com/w3c/csswg-drafts/issues/10803 -> Issue 10803 [css-text-4] [text-autospace] Spacing across element boundaries for BiDi content (by vitorroriz) [css-text-4] [Agenda+] [i18n-tracker] [Agenda+ i18n] 14:21:21 https://github.com/w3c/csswg-drafts/issues/10803 14:24:03 fantasai: I think a lot of the cases the non-CJK text contains anything like it's a part of a string that contains anything other than @@1 14:24:17 ... bidi text gets reordered on its own 14:24:44 ... visual level @@2 14:25:20 florian: unless we imagine some different world where it's very common for people to be bilingual and fluent in Japanese and Arabic and write text in mixed languages all the time 14:26:34 ... I feel there's a correct answer, but it's going to matter very, very rarely 14:27:29 ... it will exist some of the time, it's just going to be in specialized publications 14:27:46 fantasai: those publications might decide that they just wrap all of their text in spans 14:28:00 ... so taht they could style them in a variety of different ways correctly 14:28:19 ... maybe add padding, but it doesn't work sometimes 14:28:27 ... like at the end of the line 14:28:47 ... I think the correct answer is define ti to be after reordering 14:29:21 ... require that at least when the entire bidi string @@3 14:29:30 ... not be sensitive to the internal reordering 14:29:39 ... if the internals are a single phrase 14:30:07 ... because I think that's the most common cases 14:30:14 ... and the most clearly wrong if you get it wrong 14:30:28 ... it should be defined as visual 14:30:52 ... we have a prioritization of getteing ceratin cases right more important than other cases 14:30:57 ... in terms of impl effort 14:31:31 ... the user agent is not required to get it right in all cases, but must get it right for these cases 14:31:51 florian: makes sense to me 14:33:41 florian: koji is the one who's waiting on us mostly 14:33:49 ... I need to look at it again 14:34:15 https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+css+label%3Aneeds-resolution 14:34:32 https://github.com/w3c/csswg-drafts/issues?q=is%3Aopen+is%3Aissue+label%3A%22Agenda%2B+i18n%22 14:36:20 https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Aneeds-resolution+label%3Awg%3Acss+ 14:38:31 Topic: UTR for the text-emphasis skip property 14:38:46 fantasai: I think currently the spec relies on the general category property with a few tweaks 14:38:53 ... are there issues with those definitions? 14:39:10 florian: I thought our worry was with a few tweaks 14:39:28 ... and the fact that as Unicode adds more chars we might need more tweaks 14:39:32 ... probably not often 14:40:29 florian: it would be nice if Unicode would just maintain this for us because that doesn't feel like something that is CSS specific 14:41:16 fantasai: I'm much more concerned about the text autospace 14:41:43 florian: we might want to keep it in our spec, that's fine 14:43:50 rrsagent, make minutes 14:43:51 I have made the request to generate https://www.w3.org/2024/10/15-i18n-minutes.html xfq 14:44:29 regrets: addison 14:44:40 s/langs/languages/ 14:48:19 > rrsagent, make minutes 14:48:23 rrsagent, make minutes 14:48:25 I have made the request to generate https://www.w3.org/2024/10/15-i18n-minutes.html xfq 16:37:10 Zakim has left #i18n