Meeting minutes
<addison> trackbot, prepare teleconference
Agenda Review
Action Items
https://
action-1173?
<trackbot> action-1173: Richard Ishida to Raise gap report on nnbsp issue in french -- due 2022-07-28 -- OPEN
r12a: ACTION-1173, still ongoing
addison: ACTION-1183, I sent another ping, hasn't worked out yet
r12a: read the email about font generics
… need to think about it more
addison: we spent time talking about it at TPAC
… fantasai said what seemed to me is a high bar
… provide a catalog of variations
<r12a> https://
addison: monospace may pass that test
… the other generics don't
… I think this catalog is what we were looking for
r12a: I think it is very important
… particularly when talking about Syriac
… is separating a heading from text alongside it a different meaning?
… Urdu people can't read nasta’liq easily
addison: should this become a document?
r12a: it's possible
action-1195?
<trackbot> action-1195: Addison Phillips to Follow up with r12a and others about gap analysis for font generics -- due 2022-09-19 -- OPEN
close action-1195
<trackbot> Closed action-1195.
r12a: I should read what fantasai said in the minutes
ACTION: addison: with r12a follow up on font generics with elika and CSS
<trackbot> Created ACTION-1209 - With r12a follow up on font generics with elika and css [on Addison Phillips - due 2022-10-06].
addison: I'm not sure that it captures the nuances of what she said
… maybe a conversation
ACTION: richard: convert csswg#4910 comment 619342561 into an article
<trackbot> Created ACTION-1210 - Convert csswg#4910 comment 619342561 into an article [on Richard Ishida - due 2022-10-06].
action-1196?
<trackbot> action-1196: Atsushi Shimono to Follow up with jlreq on csswg#6091 to see if non-cjk enclosing punctuation should be included in space-trimming -- due 2022-09-19 -- OPEN
atsushi: in progress
<r12a> https://
action-1198?
<trackbot> action-1198: Richard Ishida to Find instructions for doing reviews and add to i18n-editors page -- due 2022-09-20 -- OPEN
close action-1198
<trackbot> Closed action-1198.
close ACTION-1198
<trackbot> Closed ACTION-1198.
action-1199?
<trackbot> action-1199: Richard Ishida to Add instructions for t: labels to the github review instructions -- due 2022-09-20 -- OPEN
close action-1199
<trackbot> Closed action-1199.
<r12a> https://
action-1200?
<trackbot> action-1200: Richard Ishida to Improve ijam/tashkil definitions in glossary -- due 2022-09-20 -- OPEN
r12a: included some ijam/tashkil information
… here are the decomposed characters, here are the precomposed characters
… searching for an alternative example to the Arabic letters
… usually the precomposed character will be ijam and the decomposed character will be tashkil
… it's in progress
action-1202?
<trackbot> action-1202: Richard Ishida to Publish current specdev to tr -- due 2022-09-20 -- OPEN
close action-1202
<trackbot> Closed action-1202.
r12a: Published current specdev, clreq-gap, and jlreq-gap documents to /TR
r12a: ACTION-1203, in progress
action-1204?
<trackbot> action-1204: Addison Phillips to Add comment to secure-payment-confirmation#205 about cr transition and i18n support -- due 2022-09-21 -- OPEN
close action-1204
<trackbot> Closed action-1204.
action-1205?
<trackbot> action-1205: Addison Phillips to Triage the linked issues in #1579 into active vs. non-active -- due 2022-09-22 -- OPEN
close action-1205
<trackbot> Closed action-1205.
action-1208?
<trackbot> action-1208: Addison Phillips to Propose text for specdev about url references -- due 2022-09-29 -- OPEN
close action-1208
<trackbot> Closed action-1208.
Info Share
addison: the Unicode Consortium had an event
… 187 people attended
… all of those will be posted on YouTube
… for people to watch
JcK: there is discussion in IETF on what email addresses should look like
… related to HTML input type="email"
addison: basically we're still in the same place
… we need to try to push them to the left hand side
RADAR Review
https://
https://
fuqiao: viss spec comment ^^
… updated the spec to change 3986 -> 3987
… satisfied?
Definition about allowed file names
Close this issue and move VISS to completed
https://
https://
https://
[xfq describes the issue]
addison: we could publish a reference
… we're not chartered to work on normative documents
r12a: or another group could define this, we could point to that
addison: could be a UTN
r12a: I worry about the idea that people would link to this section
… normative requirements
addison: this section would change based on our understanding of best practices
r12a: we could ask Unicode folks
ACTION: addison: ping unicode about file naming UTN/UTR possibility
<trackbot> Created ACTION-1211 - Ping unicode about file naming utn/utr possibility [on Addison Phillips - due 2022-10-06].
Exemplary Personal Names in Specdev
https://
https://
r12a: need to publish to /TR
addison: I've taken various input
… made the table sortable
… plenty of Japanese examples
… hardly any Chinese examples
… some of the other language tagging is kind of questionable
… more female than male
… is this close enough to merge?
r12a: rename 'Notes' to 'Region'
https://
https://
https://
https://
r12a: 'Icelandic' should be 'Europe; Icelandic'
xfq: the table can only be sorted in ascending order, not in descending order.
… if I want to see 'zh-Hans', being able to sort it in descending order would be useful
r12a: we could have two Fátima rows
… one for West Asia, one for Europe
… Livia lives in Europe, Latin America
… Sofia lives in Europe; Latin America
addison: more work to do
URL Referencing in Specdev
addison: should we merge it?
r12a: works for me, these are all editorial stuff
https://
https://
addison: I drew an action item to make a PR on URLs
… specdev still links to a copy of an I-D of IRI
… maybe 'resource identifier' should be in the glossary instead
… I patched up the first part of the mustard
… basically previously said you need to allow non ascii chars in your urls
… the bottom mustard is the same, i'm not 100% happy with it
… I'm looking for feedback
… it's super unsatisfying
… and it does not solve the problem
… I also added a link to the WHATWG URL
r12a: we should say 'don't use RFC 3986, use RFC 3987, because blah blah blah'
JcK: least bad in a terrible situation
… rough edges in RFC 3987
addison: I think we hoped URL solved the problem
… browser vendors are the most visible implementers
addison: URL is good, but it's kind of a subset
… and our problem is to know what to point to
addison: I should try to add some text under the second mustard
… add IRI reference to it to make it clear
r12a: I think the second mustard is from charmod fundamental, isn't it?
addison: it was just here
… I'll look it up
https://
addison: as a reminder, there is a portion of charmod, which we retired
… looking at charmod fundamentals, there's no mention of IRIs
… should I add links to charmod-resid?
r12a: but it has been retired
… we want to add things to specdev
addison: let me go back and do some work