13:31:44 RRSAgent has joined #i18n 13:31:44 logging to https://www.w3.org/2021/06/10-i18n-irc 13:31:50 trackbot, prepare teleconference 13:31:53 RRSAgent, make logs public 13:31:56 Meeting: Internationalization Working Group Teleconference 13:31:56 Date: 10 June 2021 13:32:05 Chair: Addison Phillips 13:32:24 Sorry, I did not find an agenda. 13:34:12 Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2021Jun/0004.html 13:34:22 addison, sorry, could not get https://lists.w3.org/Archives/Member/member-i18n-core/2021Jun/0004.html (code 500). 13:34:51 agenda+ Agenda 13:34:55 agenda+ Action Items 13:34:59 agenda+ Info Share 13:35:02 agenda+ Radar 13:35:19 agenda+ CSS Counter Styles 13:35:54 agenda+ Developing Localizable Manifests (draft) 13:35:57 agenda+ String-Meta 13:36:12 agenda+ Review comments for timing specs 13:36:16 agenda+ AOB? 13:36:23 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html addison 13:36:51 regrets+ JcK 13:37:12 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html addison 13:52:23 xfq has joined #i18n 13:56:36 present+ Addison 13:56:49 present+ Fuqiao 13:57:26 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html addison 14:00:34 fsasaki has joined #i18n 14:01:44 present+ Richard, Atsushi 14:02:49 scribe: fsasaki 14:03:23 zakim, take up agendum 1 14:03:23 agendum 1 -- Agenda -- taken up [from addison] 14:03:28 agenda? 14:03:56 zakim, take up agendum 2 14:03:56 agendum 2 -- Action Items -- taken up [from addison] 14:04:06 https://www.w3.org/International/track/actions/open 14:04:28 action-925? 14:04:29 action-925 -- Addison Phillips to Update string-meta to include json-ld changes, etc. -- due 2020-07-09 -- OPEN 14:04:29 https://www.w3.org/International/track/actions/925 14:04:34 addison: started on that 14:04:40 action-946? 14:04:40 action-946 -- Addison Phillips to Create definition of 'ltr'/'rtl'/'auto' that can be referenced by other specifications in string-meta -- due 2020-09-03 -- OPEN 14:04:40 https://www.w3.org/International/track/actions/946 14:04:51 done by addison :) 14:04:55 close action-946 14:04:55 Closed action-946. 14:05:14 action-1017? 14:05:14 action-1017 -- Addison Phillips to Send wpwg list of specs that implement lang/dir -- due 2021-04-22 -- OPEN 14:05:14 https://www.w3.org/International/track/actions/1017 14:05:17 addison: pending 14:05:29 action-1031? 14:05:29 action-1031 -- Addison Phillips to Document the state of payment-request -- due 2021-06-03 -- OPEN 14:05:29 https://www.w3.org/International/track/actions/1031 14:05:51 addison: sent note to chairs, will keep action open until the github issue is update 14:05:54 action-1032? 14:05:54 action-1032 -- Richard Ishida to Propose text for html 4814 (datalist find/string search) -- due 2021-06-03 -- OPEN 14:05:54 https://www.w3.org/International/track/actions/1032 14:06:01 richard: pending 14:06:14 action-1033? 14:06:14 action-1033 -- Addison Phillips to Create skeleton of "best practices for manifests" -- due 2021-06-10 -- OPEN 14:06:14 https://www.w3.org/International/track/actions/1033 14:06:22 addison: done 14:06:24 close action-1033 14:06:24 Closed action-1033. 14:06:39 zakim, take up agendum 3 14:06:39 agendum 3 -- Info Share -- taken up [from addison] 14:07:18 zakim, take up agendum 4 14:07:18 agendum 4 -- Radar -- taken up [from addison] 14:07:27 https://github.com/w3c/i18n-request/projects/1 14:07:51 addison: css counter styles, richard responed to fantasai 14:08:05 ... is "in review", is deeper review needed? 14:08:29 richard: did not see anything that is a concern for us 14:08:38 ... small editorial thing has been fixed 14:08:46 ... review is done, nothing to report 14:08:53 ... we can move this to "done" 14:09:09 addison: any volunteer to read counter styles? just move it to done 14:09:14 xfq: I will have a look 14:10:13 richard: hope that this will be published as rec 14:10:38 xfq: chris and I go through all CSS specs, see what should be re-published 14:11:03 ... need to look at the tests for counter styles 14:11:22 addison: so some period after CR publication will be available 14:11:28 xfq: last CR was 4 years ago 14:11:47 richard: the review I did is an update of the current spec 14:11:56 ... not 4 years old, brand new again 14:12:19 addison: will go through normal CR & PR process 14:12:38 agenda? 14:13:18 atsushi: resource timing and user timing, is completed, part of the agenda 14:13:57 ... there is no issue for resource timing 14:14:08 addison: so I move the doc to completed? 14:14:15 atsushi: yes 14:14:21 addison: will do 14:14:42 ... performance timeline is incoming 14:14:49 atsushi: will take this 14:14:59 xfq: closely related to timing specs 14:15:19 agenda? 14:15:34 zakim, take up agendum 8 14:15:34 agendum 8 -- Review comments for timing specs -- taken up [from addison] 14:15:58 https://github.com/w3c/i18n-activity/issues/1392 14:16:16 atsushi: from level 2 to level 3, one feature was added 14:16:32 ... convert to timestamp function 14:16:43 ... in their ticket, "storing match" is defined as match 14:17:07 richard: what does a timestamp look like? 14:17:32 atsushi: something from page load, a numeric value 14:17:35 xfq: millisecond value 14:17:56 addison: since epoc, or millisecond lapsed? 14:18:04 atsushi: from epoch, I think 14:18:14 ... but could be both, per implementation 14:18:52 atsushi: used to measure the marks between two points 14:18:58 ... output from the two marks is important 14:19:19 richard: is the spec saying that they produce human readable output? 14:19:29 atsushi: user can define mark or @@@ 14:19:32 https://w3c.github.io/user-timing/#example-1 14:19:56 atsushi: see performance mark with text label 14:20:03 ... each label can be defined by a developer 14:20:29 addison: developer can name them, but these are just IDs, the rest is just numbers (time of milliseconds) 14:20:34 atsushi: yes 14:22:34 atsushi describing various process options 14:22:53 addison: using "is" is a good use of this, because otherwise they do not define matches 14:23:14 +1 14:23:16 addison: any objections about this comment? Other observations? 14:23:22 +1 14:23:27 +1 14:23:43 addison: atsushi, please file the comment 14:23:54 ... I will move the doc to "awaiting comment resolution" 14:24:03 zakim, take up agendum 5 14:24:03 agendum 5 -- CSS Counter Styles -- taken up [from addison] 14:24:53 https://www.w3.org/TR/predefined-counter-styles/ 14:25:08 https://lists.w3.org/Archives/Member/member-i18n-core/2021Jun/0006.html 14:25:15 richard: there is a new version on TR 14:25:30 ... xfq published the doc 14:25:41 ... I published more docs yesterday 14:25:50 ... counter styles changes are: 14:25:59 https://www.w3.org/TR/predefined-counter-styles/ 14:26:11 https://www.w3.org/TR/predefined-counter-styles/#affixes 14:26:42 ... section 1.1: we got examples about suffixes and prefixes 14:27:04 ... seemed to me that it would start to make the doc very large 14:27:25 ... so I say: we define the base algorithm 14:27:49 ... and we say: we used the common default, and a note saying "these are common ways to do the affixes" 14:28:02 .. so we have notes instead of dublicating the styles 14:28:54 ... a section shows how to have a different separator, using the "extends" keyword 14:29:24 ... andrew cunningham is still clarifying things, with a delay due to the situation in Mynamar 14:29:34 https://www.w3.org/TR/predefined-counter-styles/#myanmar-styles 14:29:35 Alternative prefix/suffix styles 14:29:46 https://www.w3.org/TR/predefined-counter-styles/#myanmar-styles 14:29:47 s/Mynamar/Myanmar/ 14:30:01 richard: I changed Myanmar, it used to have default space suffix 14:30:15 ... parenthesis is more common, it seems 14:33:01 richard: moved japanese and korean stuff into "japanese and korean" section 14:33:09 ... added bunch of other stuff 14:33:26 https://www.w3.org/TR/2021/NOTE-predefined-counter-styles-20210606/#app-c 14:34:27 richard: we are in good position with the doc, I think 14:34:39 ... also went through tests in the test suite and the gap analysis 14:35:09 addison: very cool! 14:35:19 ... should this be a "statement" in the new process? 14:35:34 richard: no 14:35:42 ... we update this regularly, once we get more information 14:36:31 https://www.w3.org/Consortium/Process/Drafts/#registries 14:36:46 richard: you can use whatever keyword you want 14:37:04 ... so there is no "normative" recommendation, just stuff you may want to use 14:37:17 ... also no intend to cover all things you need, or limit things 14:37:21 addison: ok 14:37:26 agenda? 14:37:56 zakim, take up agendum 7 14:37:56 agendum 7 -- String-Meta -- taken up [from addison] 14:38:19 https://github.com/w3c/string-meta/pull/55 14:38:29 addison: pull request has bidi keywords in it 14:38:45 ... I added small subsection 14:39:11 ... xfq commented that basically ltr and rtl refers to CSS, auto refers to definition in HTML 14:39:31 ... question whether I should bring definitions here or put them by reference 14:39:50 ... started to indicate difference between ltr and cases to bring in auto 14:40:03 ... open the floor to comments 14:41:19 richard: there might places where you need to use metadata, which resolves through other rules to left-to-right 14:41:34 ... if the direction of content is not known, you should use auto rules 14:41:51 addison: if there is no direction, you use auto 14:41:54 richard: you use auto 14:42:01 addison: that is UBA 14:42:12 richard: auto says: use the UBA 14:42:29 .. if you do not have auto, things are up to the application 14:42:50

dldld .......

14:43:09 richard: discussing section 2.4 ... that is "auto" 14:43:18 addison: my thinking is two-fold: 14:43:27 ... if you send s.t., you should indicate the direction 14:43:35 ... if you do not know the direction, "auto" is not helpful 14:43:38 richard: agree 14:43:48 addison: if you do not know the direction, do not send it 14:44:03 ... if you define e.g. HTML, you need all three values 14:44:50 scribe+ 14:45:10 r12a: some of the formats for which we wrote this document 14:45:24 ... we do recommend auto 14:45:45 addison: we recommend the auto heuristics, but not necessarily the auto keyword 14:45:59 ... two things 14:46:10 ... first is define the direction, the dir attribute 14:46:35 ... under what situations you will allow those values and consume 14:47:13 r12a: is there a problem if somebody uses the auto label? 14:47:33 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html xfq 14:48:09 addison: i think i have enough information to do some more edits 14:48:36 ... do we want to draw specific distinctions or recommendations for when to use direction and when to use dir 14:49:07 r12a: I read that and I had the same questions 14:49:12 s/questions/question 14:49:35 addison: i could be less prescriptive and just leave that aside 14:49:46 ... we would be super sad to see both 14:49:59 r12a: you could have lang and language 14:50:12 addison: it's the same problem 14:50:22 r12a: language is usually used for metadata 14:51:05 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html xfq 14:52:18 epub: https://w3c.github.io/epub-specs/epub33/core/#sec-shared-attrs 14:52:49 Publication Manifest: https://www.w3.org/TR/pub-manifest/#manifest-lang-dir-global 14:53:05 "property" not "data value" 14:53:33 addison: i'll take another whack at it 14:53:41 bert: i like it 14:54:37 zakim, take up agendum 9 14:54:37 agendum 9 -- AOB? -- taken up [from addison] 14:55:05 addison: developing localizable manifests 14:55:16 ... i used respect to create the draft 14:55:22 s/respect/respec/ 14:55:36 ... i used i18n-draft as the home 14:56:08 ... r12a do you suggest we should just make a new repo? 14:56:18 r12a: it may end up being a very short note 14:56:34 ... if it's going to be an article it should be in an article format 14:57:49 xfq: If we are writing for spec developers, a note might be better 14:59:18 r12a: if we decide to make it into an article we don't want it to be in a repo 14:59:46 addison: i'll move it to temp and we'll discuss whether it should be a note 15:00:26 r12a: it depends on whether we're going to have mustards in it 15:00:38 addison: it's a best practice document 15:01:10 r12a: mustards are not normative, they are recommendations 15:01:27 ... a way of getting the message across 15:01:52 ... it wasn't to say these are the normative bits 15:02:01 ... even in charmod fundamental 15:02:40 addison: if you have comments on the text 15:02:47 ... that would be super useful 15:03:15 will join immediaterly after i18n finished 15:03:23 ... i'll email the list 15:04:07 rrsagent, make minutes 15:04:07 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html xfq 15:04:15 Najib has joined #i18n 15:04:18 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html addison 15:06:28 s/will join immediaterly after i18n finished// 15:06:42 I had the same issue for today's another meeting... 15:13:01 rrsagent, draft minutes 15:13:01 I have made the request to generate https://www.w3.org/2021/06/10-i18n-minutes.html r12a 15:13:33 xfq, seems to be working now