13:53:57 RRSAgent has joined #i18n 13:54:01 logging to https://www.w3.org/2024/09/19-i18n-irc 13:54:05 Meeting: Internationalization Working Group Teleconference 13:54:11 agenda: https://www.w3.org/events/meetings/bc275b6e-6c38-4ed5-b324-6606a0c6cca7/20240919T150000/ 13:54:11 clear agenda 13:54:11 agenda+ Agenda Review 13:54:11 agenda+ Action Items 13:54:14 agenda+ Info Share 13:54:16 agenda+ RADAR Review 13:54:17 Chair: Addison Phillips 13:54:18 agenda+ Pending Issue Review 13:54:21 agenda+ TPAC Planning Review 13:54:23 agenda+ I18N ⇔ CSS Review 13:54:25 agenda+ Engage Privacy? 13:54:27 I have made the request to generate https://www.w3.org/2024/09/19-i18n-minutes.html addison 13:54:29 agenda+ AOB? 14:00:13 present+ Addison, JcK 14:01:18 present+ Fuqiao, Richard 14:01:25 present+ Atsushi 14:02:20 scribe: xfq 14:02:53 zakim, take up agendum 1 14:02:53 agendum 1 -- Agenda Review -- taken up [from agendabot] 14:02:55 agenda? 14:03:36 zakim, take up agendum 2 14:03:36 agendum 2 -- Action Items -- taken up [from agendabot] 14:03:42 https://github.com/w3c/i18n-actions/issues 14:03:48 #122 14:03:49 https://github.com/w3c/i18n-actions/issues/122 -> Action 122 reach out to alan to see if we can schedule i18n/css to morning (on aphillips) due 2024-09-24 14:04:30 addison: the answer from CSS is basically no 14:04:34 atsushi has joined #i18n 14:04:44 ... but we'll try to have some time of our meetings for CSS topics 14:04:48 close #122 14:04:52 ... does that sound like a plan? 14:04:57 Closed -> issue #122 https://github.com/w3c/i18n-actions/issues/122 14:05:00 #119 14:05:01 https://github.com/w3c/i18n-actions/issues/119 -> Action 119 write back on css 10844 saying maybe RLM/LRM from direction of elided chars (on aphillips) due 2024-09-19 14:05:22 #121 14:05:24 https://github.com/w3c/i18n-actions/issues/121 -> Action 121 add additional comment to css 10844 to emphasize logical truncation (on aphillips) due 2024-09-24 14:05:36 addison: #119, discussed in the i18n & CSS meeting 14:05:38 close #119 14:05:40 Closed -> issue #119 https://github.com/w3c/i18n-actions/issues/119 14:05:43 ... I have an additional action item 14:05:53 #115 14:05:53 https://github.com/w3c/i18n-actions/issues/115 -> Action 115 review i18n-activity#1783 (on r12a) due 2024-08-22 14:05:55 present+ Bert 14:06:12 #90 14:06:13 https://github.com/w3c/i18n-actions/issues/90 -> Action 90 steal some of henri's text from scroll-to-text-fragment for string-search (on aphillips) due 2024-04-18 14:06:26 #89 14:06:26 https://github.com/w3c/i18n-actions/issues/89 -> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18 14:06:38 #33 14:06:38 https://github.com/w3c/i18n-actions/issues/33 -> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips) 14:06:47 #8 14:06:47 https://github.com/w3c/i18n-actions/issues/8 -> Action 8 Follow up on the status of Canvas and formatted text (on aphillips) due 18 Jul 2023 14:06:50 #7 14:06:51 https://github.com/w3c/i18n-actions/issues/7 -> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023 14:07:09 #4 14:07:09 https://github.com/w3c/i18n-actions/issues/4 -> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on aphillips, r12a) due 27 Jul 2023 14:07:22 zakim, take up agendum 3 14:07:22 agendum 3 -- Info Share -- taken up [from agendabot] 14:07:51 zakim, take up agendum 4 14:07:51 agendum 4 -- RADAR Review -- taken up [from agendabot] 14:07:58 https://github.com/orgs/w3c/projects/91/views/1 14:08:37 addison: we have a new incoming request from wasm 2 14:08:48 ... they have requested that we do this in 2 weeks 14:08:56 ... and one week is TPAC 14:09:03 ... not gonna happen 14:11:01 xfq: I can review this, but not before 2024-10-03 14:11:19 Bert: still working on Accessibility Conformance Testing (ACT) Rules Format 1.1 14:11:36 addison: WebXR Device API is on me 14:11:47 zakim, take up agendum 5 14:11:48 agendum 5 -- Pending Issue Review -- taken up [from agendabot] 14:11:52 ... I found one potential issue which we will discuss in a couple of minutes 14:11:55 https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Apending 14:11:59 ... otherwise that one is done 14:12:04 #1907 14:12:05 Issue 1907 not found 14:12:13 i18n-activity#1907 14:12:14 https://github.com/w3c/i18n-activity/issues/1907 -> Issue 1907 Adopt GB18030-2022 (by w3cbot) [pending] [tracker] [s:encoding] 14:13:39 i18n-activity#1906 14:13:39 https://github.com/w3c/i18n-activity/issues/1906 -> Issue 1906 input profile name limited to ASCII lowercase? (by aphillips) [pending] [s:webxr] [t:application_internal] [wg:immersive-web] 14:13:51 xfq: I haven't looked at the details yet, but some Chinese vendors are looking forward to browsers adopting GB18030-2022 14:14:41 atsushi: input profile name is not a human readable string 14:14:47 ... it's an identifier 14:14:56 addison: they have a lot of things like that in the spec 14:15:13 ... which are only for internal consumption 14:15:19 ... but this one seems to leak 14:16:07 ... you don't want those to have every localization on earth in them 14:16:22 ... but internal identifiers shouldn't leak like this 14:16:51 atsushi: I understand there will be some string used for display 14:16:56 https://github.com/immersive-web/webxr/issues/1121#issuecomment-682689709 14:16:56 https://github.com/immersive-web/webxr/issues/1121 -> CLOSED Issue 1121 Input profile name generation and normalization rules incomplete (by aphillips) [i18n-needs-resolution] 14:17:02 https://github.com/immersive-web/webxr-input-profiles/tree/master/packages/registry 14:18:33 addison: I'll add a note about this preview response 14:18:39 ... to the issue when I file it 14:18:52 ... if you really feel that no one will ever see these, then never mind 14:19:17 i18n-activity#1903 14:19:28 https://github.com/w3c/i18n-activity/issues/1903 -> Issue 1903 XML and XMLName should account for U+061C (ALM) (by aphillips) [pending] [t:char_string] 14:19:52 addison: I was working on MessageFormat and implementing bidi 14:20:32 ... one of the things that we noticed in the course of doing that was U+061C ARABIC LETTER MARK is permitted in XML identifiers and XML names 14:20:44 ... including NameStartChar 14:21:00 ... this is because XML was written before ALM was created 14:21:10 ... and ALM is kind of an unusual beast 14:21:45 JcK: Tim Bray is trying to push a new spec about @@ 14:22:30 Bert: we have some sort of process for making errata on documents that we don't have a WG anymore 14:22:34 agenda? 14:22:37 ... we can try it out 14:22:49 addison: I'll look into that 14:23:04 zakim, take up agendum 8 14:23:05 agendum 8 -- Engage Privacy? -- taken up [from agendabot] 14:23:19 addison: I had a chat with Shane Carr 14:24:15 ... he is effectively the chair of the JS i18n group at Ecma 14:24:25 ... and he does some other things with Unicode 14:24:44 ... one of the things that he was interested is whether we were gonna meet with privacy 14:25:04 ... we've seen this pattern of attempting to add @@ 14:25:51 ... fingerprinting vector vs good for international users 14:26:20 xfq: we have a breakout session for horizontal groups at TPAC 14:26:26 https://github.com/w3c/tpac2024-breakouts/issues/65 14:26:27 https://github.com/w3c/tpac2024-breakouts/issues/65 -> Issue 65 Horizontal reviews at W3C and beyond (by plehegar) [session] [track: Standards] 14:26:42 xfq: if we have time, we can mention that in the breakout session 14:26:57 addison: yeah, but that's usually about the process 14:27:16 ... I don't know if the accessibility people have the same problem 14:27:28 https://github.com/w3c/strategy/issues/477 -> Issue 477 [wg/css] CSS Working Group Charter (by svgeesus) [Horizontal review requested] [Accessibility review completed] [Internationalization review completed] [Security review completed] [charter] 14:28:09 action: xfq: reach out to the privacy person (Tara?) about meeting at TPAC 14:28:18 Created -> action #123 https://github.com/w3c/i18n-actions/issues/123 14:28:30 zakim, take up agendum 6 14:28:30 agendum 6 -- TPAC Planning Review -- taken up [from agendabot] 14:28:42 https://www.w3.org/groups/wg/i18n-core/calendar/ 14:29:02 https://www.w3.org/events/meetings/900ac419-eda7-404d-9750-d87b8c83dc05/ 14:29:45 https://www.w3.org/events/meetings/57789807-76fd-4d76-a1f9-e434efa7a4a9/ 14:29:59 addison: one of the main tasks on Monday will be to flesh out our joint meetings with CSS and accessibility and WHATWG 14:30:13 ... then we have a meeting on Friday 14:30:21 ... the agenda is very similar to the first agenda 14:30:40 ... I would welcome people suggesting topics for any of these days 14:30:51 ... agenda+ emails work 14:30:57 ... if we have specific things for any of the groups 14:31:29 agenda? 14:31:44 zakim, take up agendum 7 14:31:44 agendum 7 -- I18N ⇔ CSS Review -- taken up [from agendabot] 14:32:03 addison: most of you were on that call 14:32:04 https://www.w3.org/2024/09/17-i18n-minutes.html 14:33:39 ... we were very productive 14:33:59 ... we have 100+ years open at any given moment in time 14:34:43 ... florian has an outstanding action item about logical vs physical 14:35:18 s/years/issues/ 14:36:02 r12a: they have a lot of things to do, and we have a lot of things that we're waiting for them to do 14:36:35 ... in the meantime, there are lots of other issues that could be resolved much more quickly 14:36:40 ... which are not getting any attention 14:37:07 ... let's push them harder on getting these things done in reasonable timeframe 14:37:14 addison: I think I agree 14:38:32 ... I think we should have a couple of big items if we think there are reasonable chances 14:38:57 ... but if there's low hanging fruit, maybe we should go and say, hey, we have low hanging fruit 14:39:05 ... easier things that you could resolve 14:39:28 ... if you can't move the moveable object, maybe move the moveable ones 14:39:48 addison: who can make a list? 14:40:03 r12a: we've got some already, because some of them are marked needs-resolution 14:40:08 https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Awg%3Acss 14:40:18 ... as I mentioned on Tuesday, there's also the gap analysis pipeline 14:41:04 ... writing mode sideways 14:41:10 ... it shouldn't be too hard 14:41:17 ... Gecko already does it 14:41:34 action: addison: we'd like to see writing-mode sideways implemented (in spec, just need traction) 14:41:35 Created -> action #124 https://github.com/w3c/i18n-actions/issues/124 14:41:36 ... and if we had WebKit and Gecko doing it, then we might be able to make Google do it 14:41:58 ... that's something to socialize during TPAC 14:42:07 https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3AAgenda%2BI18N%2BCSS 14:42:15 ... because it's been a while now, and not too hard to implement 14:43:34 zakim, take up agendum 9 14:43:34 agendum 9 -- AOB? -- taken up [from agendabot] 14:44:08 r12a: please recruit people 14:44:12 ... during TPAC 14:46:57 [Discuss how to recruit and retain more participants for the i18n WG] 14:49:11 r12a: I still think we need to work on the format of the agenda 14:49:33 ... I know we did that already, but the first dozen lines is always the same from week to week 14:49:53 ... and I don't have time to dig down and find out what interesting new topics we're gonna discuss 14:50:13 addison: I'm totally open to changing the format 14:51:01 r12a: I think the very first thing should be the topics for this week, and then the regular stuff that we also go through 14:51:18 addison: I can do that 14:52:54 addison: for those of you traveling, safe travels 14:53:03 ... I'll see you in the county of Oranges 14:53:23 rrsagent, make minutes 14:53:24 I have made the request to generate https://www.w3.org/2024/09/19-i18n-minutes.html xfq 15:09:04 bigbluehat has joined #i18n