13:40:16 <RRSAgent> RRSAgent has joined #i18n
13:40:20 <RRSAgent> logging to https://www.w3.org/2023/10/26-i18n-irc
13:40:28 <addison> Meeting: Internationalization Working Group Teleconference
13:41:08 <addison> Chair: Addison Phillips
13:41:08 <agendabot> agenda: https://www.w3.org/events/meetings/c5b143d1-0a5b-4adb-8d60-0f5f9bfe5a41/20231026T150000/
13:41:08 <agendabot> clear agenda
13:41:08 <agendabot> agenda+ Agenda Review
13:41:08 <agendabot> agenda+ Action Items
13:41:08 <agendabot> agenda+ Info Share
13:41:08 <agendabot> agenda+ RADAR Review
13:41:08 <agendabot> agenda+ Pending Issue Review
13:41:08 <agendabot> agenda+ VC Urgent reviews
13:41:39 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/26-i18n-minutes.html addison
13:41:41 <agendabot> agenda+ Working with String Data Values (draft)
13:41:41 <agendabot> agenda+ Review some needs-attention issues
13:41:41 <addison> Regrets+ JcK
13:41:41 <agendabot> agenda+ AOB?
13:42:04 <addison> agenda+ no needs-resolution on vc-json-schema
13:50:49 <addison> present+ Addison
13:57:09 <xfq__> xfq__ has joined #i18n
13:57:50 <addison> present+ Atsushi
13:58:43 <xfq_> xfq_ has joined #i18n
14:00:35 <xfq> xfq has joined #i18n
14:04:22 <addison> present+ Fuqiao
14:06:33 <addison> agenda?
14:06:56 <addison> zakim, take up agendum 2
14:06:56 <Zakim> agendum 2 -- Action Items -- taken up [from agendabot]
14:08:24 <atsushi> xfq: there was some discussion on i18n-CSS joint call
14:08:35 <addison> #54
14:08:36 <gb> https://github.com/w3c/i18n-actions/issues/54 -> Action 54 read Murata-san's ruby-t2s-req and Chinese requirements and Zaima and see what we're going to do (on xfq) due 2023-11-01
14:08:55 <atsushi> addison: on ruby text-to-speech, what was discussion there and comment from Murata-san?
14:08:59 <xfq> https://w3c.github.io/ruby-t2s-req/
14:09:06 <atsushi> xfq: see link above for tracker issue
14:09:20 <atsushi> ... murata-san has been working on this document for a while
14:09:33 <atsushi> ... florian pointed this during i18n-css call
14:09:47 <atsushi> ... this document explains ruby requirements from Japanese point of view
14:10:15 <atsushi> ... and discussion was raised to see any additional requirement from clreq or other languages
14:10:35 <xfq> Zaima
14:10:41 <atsushi> ... I'll read Zaima document and will comment
14:10:59 <addison> #53
14:10:59 <gb> https://github.com/w3c/i18n-actions/issues/53 -> Action 53 come up with a set of information CSS want the i18n group to provide support for generic font families (on frivoal, fantasai) due 2023-11-01
14:11:11 <atsushi> addison: florian and fantasai presented on generic font support for i18n point of view
14:11:34 <atsushi> ... we had some discussion on generic font name, and had some idea for proposal
14:12:05 <atsushi> xfq: there seems some discussion on registries like document, but florian seems to have some disagreement on having such
14:12:21 <atsushi> ... and framwork has not been initiated yet
14:12:39 <addison> zakim, take up agendum 3
14:12:39 <Zakim> agendum 3 -- Info Share -- taken up [from agendabot]
14:12:54 <atsushi> addison: published specdev to /TR/
14:13:22 <xfq> scribe+
14:14:14 <atsushi> atsushi: Murata-san complained about replaced simple-ruby in jlreq
14:14:18 <xfq> https://github.com/w3c/i18n-activity/issues/1779
14:14:19 <gb> https://github.com/w3c/i18n-activity/issues/1779 -> Issue 1779 [css-text] Extra spacing between ideographs and non-fullwidth punctuation/symbols (by w3cbot) [tracker] [s:css-text] [i:spacing] [spec-type-issue] [jlreq] [clreq] [t:typ_misc]
14:14:33 <atsushi> https://w3c.github.io/jlreq/docs/simple-ruby/
14:14:39 <atsushi> xfq: have one point on text-spacing
14:14:46 <atsushi> ... between ideograph and other characters
14:15:03 <atsushi> ... this should be promoted to needs-resolution, since it's under real implementation
14:15:11 <atsushi> ... and discussion is required sonner than later
14:15:28 <atsushi> ... there are several issues identified
14:16:36 <atsushi> ... spacing between ideographs and others like wester characters, but there are open question on ideograph-like characters
14:16:36 <atsushi> addison: that seems reasonable to mark as needs-resolution
14:17:35 <xfq> atsushi: as I reported in i18n/CSS call, there was so much ambiguity in the general category code
14:18:03 <xfq> ... a lot of discussions about things like halfwidth kana
14:18:28 <xfq> ... we may have some questions in the next jlreq call next Tuesday
14:18:49 <xfq> addison: if the spec isn't quite right or the implementations aren't quite right
14:18:53 <xfq> ... then we should push on it
14:20:00 <xfq> atsushi: one interesting discussion is Circled Katakana characters
14:20:34 <xfq> ... combining characters are quite messy
14:20:43 <addison> agenda?
14:20:54 <addison> zakim, take up agendum 4
14:20:54 <Zakim> agendum 4 -- RADAR Review -- taken up [from agendabot]
14:21:02 <addison> https://github.com/w3c/i18n-request/projects/1
14:21:57 <addison> zakim, take up agendum 10
14:21:57 <Zakim> agendum 10 -- no needs-resolution on vc-json-schema -- taken up [from addison]
14:22:18 <Najib> Najib has joined #i18n
14:22:30 <xfq> atsushi: the spec has a i18n considerations section
14:23:47 <xfq> ... I believe there's no need to have a i18n considerations section, because the considerations are in another spec
14:24:10 <xfq> ... I raised an issue in i18n-activity
14:24:20 <xfq> https://github.com/w3c/i18n-activity/issues/1786
14:24:21 <gb> https://github.com/w3c/i18n-activity/issues/1786 -> Issue 1786 [VC-JSON-SCHEMA] overwritting internationalization consideration section? (by himorin) [pending] [s:vc-json-schema]
14:24:39 <addison> https://www.w3.org/TR/vc-json-schema/#example-example-name-credential-schema
14:24:44 <r12a> r12a has joined #i18n
14:24:59 <r12a> present+
14:25:00 <xfq> addison: I do see they have some examples that have name and description fields
14:25:22 <xfq> ... and they're not serialised with lang and dir metadata
14:25:58 <xfq> ... their example should include language=en and direction=ltr
14:26:11 <xfq> ... either at the document level or for those fields
14:26:52 <xfq> ... this document is about other stuff, but they exemplify natural language strings
14:27:03 <addison>   "name": "Name schema",   "description": "A schema capturing a human name",
14:27:05 <Najib_> Najib_ has joined #i18n
14:28:36 <xfq> ... there's nothing wrong with the serialisation stuff and it's all valid JSON Schema
14:28:50 <xfq> Schema.org -> https://schema.org/
14:28:56 <xfq> JSON Schema -> https://json-schema.org/
14:28:59 <atsushi> https://json-schema.org/specification
14:30:07 <xfq> atsushi: JSON Schema doesn't have anything about language and direction metadata
14:31:35 <gb> https://github.com/w3c/strategy/issues/108 -> Issue 108 JSON schema (by dontcallmedom) [Data]
14:32:14 <xfq> addison: file that issue and I'll move it over to Awaiting comment resolution
14:32:29 <addison> agenda?
14:36:00 <xfq> atsushi: there are discussions about JSON-LD VCs and JSON VCs
14:36:26 <atsushi> s/atsushi: there are discussions about JSON-LD VCs and JSON VCs//
14:36:26 <addison> zakim, take up agendum 7
14:36:26 <Zakim> agendum 7 -- Working with String Data Values (draft) -- taken up [from agendabot]
14:36:44 <addison> https://deploy-preview-121--bp-i18n-specdev.netlify.app/#working-with-non-localizable-and-localizable-data-values
14:36:47 <atsushi> scribe+
14:36:53 <atsushi> addison: this is from my action item
14:37:05 <addison> https://deploy-preview-121--bp-i18n-specdev.netlify.app/#working-with-string-data-values
14:37:18 <atsushi> addison: see hashed link above
14:37:37 <atsushi> ... early days I wanted to see feedbacks on these sections
14:38:07 <atsushi> addison: whole new section
14:38:08 <addison> https://github.com/w3c/bp-i18n-specdev/pull/121
14:39:25 <r12a> specificatino -> specification
14:39:46 <atsushi> xfq: second paragraph, above typo exists
14:39:54 <r12a> q+
14:39:55 <xfq> asigning -> assigning
14:40:30 <atsushi> rrsagent, publish minutes
14:40:31 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/26-i18n-minutes.html atsushi
14:40:37 <atsushi> rrsagent, make log public
14:41:41 <xfq> q+
14:41:48 <addison> ack r12a
14:42:12 <atsushi> r12a: couple of questions, this is in markup and syntax section, not quite sure why this is not in more general advice
14:42:23 <atsushi> ... what is the point of this 8.3 section
14:42:57 <atsushi> ... what we are saying in this section is not matching with title
14:43:26 <atsushi> ... string data values are very bake, you also categorize normal as down styel
14:43:31 <xfq> <xfq> maybe "predefined values" or "predefined constants"?
14:43:34 <atsushi> s/styel/style
14:44:16 <atsushi> addison: section marked as this is elements and attributes are identified as markup
14:44:26 <atsushi> ... names and values are written in syntax
14:44:43 <atsushi> ... we may state these to be syntaxed as well defined
14:45:05 <atsushi> r12a: what we should do for strings and captalized schema
14:45:33 <atsushi> addison: this is between strings and predefined strings, or seriarized strings
14:45:48 <atsushi> r12a: syntax is small, and could drop from here
14:46:08 <atsushi> ... idea is to have specific markup, or perhaps in some syntax in general
14:47:42 <addison> ack xfq
14:48:15 <atsushi> xfq: wanted to say another thing on markup and syntax, 8.3 is not specific to syntax
14:48:25 <atsushi> ... other markup is mentioned also
14:48:39 <atsushi> ... markups should be moved into another section?
14:48:53 <atsushi> addison: upper 8.2 talks about identifiers, so could be?
14:49:51 <atsushi> [discussion between markup and syntax...]
14:50:54 <addison> zakim, take up agendum 9
14:50:54 <Zakim> agendum 9 -- AOB? -- taken up [from agendabot]
14:51:13 <atsushi> r12a: small infoshare
14:51:14 <xfq> q+
14:51:32 <atsushi> ... mentioned last week, but I've been working on fonts' list and sample
14:51:43 <atsushi> ... and getting there
14:52:33 <atsushi> ... why decided to work on this, for generic callback categories, what kind of fonts exist in OS is important for generics' fallbacks
14:52:52 <atsushi> ... I think it's florian's ball to look into my article
14:53:40 <addison> ack xfq
14:53:40 <atsushi> ... this document makes understanding what is required
14:53:40 <xfq> https://github.com/w3c/i18n-activity/issues/1783
14:53:40 <gb> https://github.com/w3c/i18n-activity/issues/1783 -> Issue 1783 CSS `text-spacing` property and its longhands (by w3cbot) [pending] [tracker]
14:53:49 <atsushi> xfq: since we have issue above, there is TAG issue on css property, and as i18n-tracker
14:54:31 <atsushi> ... one alternative might be having another label
14:54:56 <atsushi> addison: we should be aware of these
14:56:41 <atsushi> addison: we may need to ask TAG that what HR groups should work on review requested from TAG issue
14:57:04 <atsushi> r12a: I would say we have s:tag for specific to document
14:57:33 <atsushi> ... alternatively s:design-review or something could work?
14:57:48 <xfq> s/we have s:tag for specific to document/we have s:css-text for specific to document
14:58:26 <atsushi> r12a: ask xfq for looking into these, for what is actual intention
14:59:01 <xfq> s/these, for what is actual intention/the triage permission of the w3ctag org on github
14:59:30 <atsushi> xfq: will take an action
15:00:00 <addison> action: xfq to check on permissions with w3ctag and follow up with plh on looking for notifications
15:00:10 <gb> Created -> action #56 https://github.com/w3c/i18n-actions/issues/56
15:00:45 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/26-i18n-minutes.html addison
15:00:52 <xfq> rrsagent, make minutes
15:00:53 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/26-i18n-minutes.html xfq