14:41:13 RRSAgent has joined #i18n 14:41:13 logging to https://www.w3.org/2022/01/13-i18n-irc 14:41:25 trackbot, prepare teleconference 14:41:28 RRSAgent, make logs public 14:41:31 Meeting: Internationalization Working Group Teleconference 14:41:31 Date: 13 January 2022 14:41:36 Chair: Addison Phillips 14:41:44 agenda: https://www.w3.org/events/meetings/baf262b7-7551-4c04-96a0-662d85c35505/20220113T150000 14:41:44 clear agenda 14:41:44 agenda+ Agenda Review 14:41:44 agenda+ Action Items 14:41:47 agenda+ Info Share 14:41:49 agenda+ RADAR Review 14:41:51 agenda+ String-Meta 14:41:54 agenda+ Security issues in bidi 14:41:56 agenda+ Radar Assignments 14:41:58 agenda+ AOB? 14:42:22 I have made the request to generate https://www.w3.org/2022/01/13-i18n-minutes.html addison 14:46:39 agenda+ How to order items in a multilingual list 14:53:19 xfq has joined #i18n 14:57:50 present+ 14:57:55 present+ Atsushi 14:58:01 present+ Erik Nordin 14:59:24 nordzilla has joined #i18n 15:00:11 present+ Fuqiao 15:01:23 present+ Richard 15:02:17 scribe: atsushi 15:04:15 present+ Bert 15:05:24 zakim, take up agendum 1 15:05:24 agendum 1 -- Agenda Review -- taken up [from agendabot] 15:05:33 agenda? 15:06:20 richard: web authentication, use gettext from GNU for localization 15:06:21 agenda+ webauth recharter and gettext 15:06:36 zakim, take up agendum 2 15:06:37 agendum 2 -- Action Items -- taken up [from agendabot] 15:06:45 https://www.w3.org/International/track/actions/open 15:07:12 addison: 1094, on ecma-402 15:07:22 ... start that conversation, and working on explainer 15:07:30 ... backoff next week 15:07:45 addison: 1097, no time on this 15:07:58 addison: 1098, on lang-bidi-use-cases 15:08:14 richard: not yet. (first week after off) 15:08:43 addison: 1100, get this shortly 15:09:01 addison: 1101, did and they replied that they are welcome 15:09:06 ... will create items 15:09:12 action: addison: create naur review item 15:09:15 Created ACTION-1108 - Create naur review item [on Addison Phillips - due 2022-01-20]. 15:09:18 close action-1101 15:09:18 Closed action-1101. 15:09:45 addison: 1103, the same explainer as ecma-402, not yet done 15:09:52 JcK has joined #i18n 15:10:03 addison: 1104 15:10:23 addison: 1106, still need? 15:10:36 close action-1106 15:10:36 Closed action-1106. 15:10:37 jck: still need 15:10:59 https://github.com/WICG/handwriting-recognition/issues/1 15:11:01 present+ JvK 15:11:08 addison: 1107, did do, and close this 15:11:11 present+ JcK 15:11:41 zxx-x-shape 15:11:45 ... they decided to use zxx 15:11:51 present- JvK 15:12:29 close action-1107 15:12:29 Closed action-1107. 15:12:34 zakim, take up agendum 3 15:12:34 agendum 3 -- Info Share -- taken up [from agendabot] 15:12:55 addison: welcome back, happy gregorian new yera 15:13:06 ... and welcome new member, Nordin joined yesterday 15:13:25 s/yera/year/ 15:13:45 erik: internationalization team at Mozilla, joined this year with my colleagues 15:14:04 ... one is in trainig of company and not here with me today 15:14:12 (other new person from Mozilla is Eemeli) 15:14:30 ... internationalized domain, ICU, i18n toolings 15:15:02 ... joining to the WG, involved to message format 2.0 15:15:13 ... interested in DOM internationalization 15:15:33 ... we hope to be more involved and to get world more internationalized 15:16:21 s/DOM internationalization/DOM localization/ 15:17:37 https://github.com/w3c/documentreview/issues/28 15:17:40 xfq: new status called registry, this needs wide review as well 15:17:49 ... added an issue to documentreview on this 15:18:05 ... we can add some correspondence template into our repository 15:18:18 addison: registration strategy or value? 15:18:35 xfq: basically strategy and documentation 15:18:40 Oh, in case that got lost over the holidays, the magic BCP link is https://www.rfc-editor.org/info/bcpNNN 15:19:01 xfq: no published registry document yet 15:19:32 ... we will see whether they will really need review or not 15:19:47 addison: we could need different tag or status? 15:19:57 ... who want to think about these? 15:20:29 richard: inclined to wait until we need to look into 15:20:42 xfq: same for me, and this is just a heads up 15:21:11 addison: chickin and egg 15:21:16 ... wait until one comes 15:21:28 ... for now, at least one in our pipeline? 15:21:44 xfq: webcodecs is creating registry, and coulbe in the pipeline 15:21:52 addison: keep it open 15:22:10 richard: monotype is interested in looking Arabic justification automatically 15:22:18 ... especially on window stretching 15:22:32 ... 6 people together and look into this area 15:22:54 ... should be useful if we can find some solution 15:23:23 ... could be plugged into CSS at some point 15:23:44 ... they also seek to extend from Arabic to others 15:23:56 zakim, take up agendum 4 15:23:56 agendum 4 -- RADAR Review -- taken up [from agendabot] 15:23:57 addison: so, taking Arabic as one of majors 15:24:52 https://github.com/w3c/i18n-request/projects/1 15:25:05 s/chickin and egg/chicken and egg/ 15:25:07 addison: it might be useful to bring thease into alreq repository once some secured text created 15:25:34 addison: no incoming review request 15:25:38 ... any status update? 15:25:58 agenda? 15:26:41 richard: a month ago, tried to raise gap-analysis pipeline, on rewritting for testing 15:27:02 ... started raising bugs, and Mozilla is working on these bugs 15:27:09 ... continue to do that 15:27:47 https://github.com/w3c/i18n-activity/projects/3 15:27:56 zakim, take up agendum 10 15:27:57 agendum 10 -- webauth recharter and gettext -- taken up [from addison] 15:28:32 richard: charter states to use gettext for localization facility 15:28:44 ... read gettext, long documentation 15:29:18 addison: not hopeless, but why W3C spec pickes up this localization technology 15:29:35 richard: this is also kind of internationalization technology 15:29:38 https://www.gnu.org/software/gettext/manual/gettext.html 15:29:56 VC WG charter -> https://w3c.github.io/vc-wg-charter/#ig-other-deliverables 15:30:06 ... wondering how bidi is handled 15:30:12 white-space 15:30:12 # translator-comments 15:30:12 #. extracted-comments 15:30:14 #: referenceā€¦ 15:30:16 #, flagā€¦ 15:30:18 #| msgid previous-untranslated-string 15:30:20 msgid untranslated-string 15:30:22 msgstr translated-string 15:30:42 eg. 15:30:44 #: lib/error.c:116 15:30:44 msgid "Unknown system error" 15:30:44 msgstr "Error desconegut del sistema" 15:30:47 richard: one line for original as id, one line for translation 15:30:54 ... just a text file 15:31:26 addison: you may want to escape bidi, and make text as human readable 15:31:58 ... but don't remember of escaping 15:32:11 bert: using gettext for some of my software, simple text file 15:32:28 ... don't think any standard on markup nor escape 15:33:06 ... usually tags are not for translation 15:33:27 addison: back to my meta question, whey would W3C points these specific thing 15:33:50 https://www.w3.org/TR/mlw-metadata-us-impl/#Using_ITS_2.0_with_GNU_gettext_utilities.2FPO_files 15:33:59 ... why not other internationalization or localization scheme? 15:34:37 xfq: our document has some lines for using GNU gettext 15:35:45 ... gettext is stream comversion 15:36:07 addison: does this WG use it for ones like angle brackets 15:36:27 ... and be careful of bidi controls 15:37:00 richard: gettext uses language code, two char with subtags 15:37:37 addison: Linux systems are using gettext for long time, and original source 15:38:23 richard: several advices on prurals also 15:39:03 addison: any other action? 15:39:08 agenda? 15:39:09 richard: will make some comments 15:39:50 VC WG charter -> https://w3c.github.io/vc-wg-charter/#ig-other-deliverables 15:40:01 example of targets -> https://github.com/w3c/vc-wg-charter/issues/19#issuecomment-994607242 15:40:39 zakim, take up agendum 9 15:40:39 agendum 9 -- How to order items in a multilingual list -- taken up [from addison] 15:40:58 https://github.com/w3c/i18n-discuss/issues/20 15:41:38 richard: this thread is wondering also of direction which has clear guidelines 15:41:51 ... discussing what order list is shown in a page 15:42:11 ... and second point, getting item to the top based on users' preference 15:42:42 ... conclusion could be different when you have long list or not 15:42:58 bert: wikipedia uses order of language code 15:43:12 richard: it is predictable 15:43:30 ... same number of translations to be shown in pages of translation 15:43:49 ... you will get one solid idea between pages on this order 15:44:29 richard: even picking some languages, we need to order lists 15:44:51 addison: randomly ordered list is possible... 15:45:12 richard: any preference? 15:45:30 ... over whole list if there is no preferred language 15:45:32 https://www.w3.org/International/articlelist 15:45:46 addison: it works ok 15:46:07 ... if you are on long list, you need to know which language is in which code 15:46:31 ... when we have completed list of cldr language list, many unknowns 15:46:40 https://r12a.github.io/app-charuse/ 15:46:43 richard: just typing and finding could work most of time 15:47:14 ... above page has all in English and can filter and jump by typing 15:47:38 richard: starting talking on ways of getting information 15:47:44 ... what order is preferred 15:48:15 addison: my preference is ordered by lang code, and pulling by typing 15:48:37 ... for example, currency selection has the same issue 15:48:59 richard: that is the preference on W3C site redesign 15:49:31 ... I think we should provide customized list, rather than providing ordered list 15:50:09 addison: if the list is large, people could miss the group at the top 15:50:25 bert: found pros/cons for that grouping 15:50:53 richard: if you only have three translation, could be picked up by browser preference 15:51:49 ... I suspect not selecter 15:52:14 ... in our article, like 40 translations, ordered list is better 15:52:41 addison: including English also seems better 15:52:49 ... and also regionaly sorted groups 15:53:47 richard: to find a language quicker, having items at the top from preference could be better 15:54:57 addison: haven't done, keens to test that 15:55:36 ... draw back is people could remember around where item was 15:57:07 richard: number of languages could differ per page 15:57:37 ... if you have 6 languages for a page, you can look without checking selections by scrolling 15:58:51 addison: just to have lists in the same order as language tag, not to cause flame 15:59:36 eric: mozilla is always aware of identifying information than just ordering 16:01:03 addison: language preference is sent to all web server as header 16:01:15 zakim, take up agendum 8 16:01:15 agendum 8 -- AOB? -- taken up [from agendabot] 16:01:23 addison: around top, any other? 16:02:10 (But need to take into account that the lang pref may be wrong on purpose, precisely because people care about protecting their personal data.) 16:03:12 I have made the request to generate https://www.w3.org/2022/01/13-i18n-minutes.html addison