Meeting minutes
Agenda Review
Action Items
addison: is there anything else we need to add to the agenda?
<addison> https://
<addison> #105
<gb> Action 105 Review https://deploy-preview-87--string-meta.netlify.app/#bp-consumers (on r12a) due 2024-06-13
<addison> #104
<gb> Action 104 follow up on action#4 by writing an email (on aphillips) due 2024-06-13
<addison> #4
<gb> 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
<addison> #103
<gb> Action 103 Migrate RADAR project (on aphillips)
addison: #103, it's a little more complicated since I clicked on the first step
<addison> #102
<gb> Action 102 ping alreq group to review our i18n-activity#1620 (on aphillips) due 2024-05-30
addison: if I run into anything, I may ping you
<addison> i18n-activity#1620
<gb> Issue 1620 [focusgroup] i18n: should arrow key navigation follow text direction? (by w3cbot) [close?] [tracker] [needs-attention] [s:open-ui] [cg:open-ui]
addison: #102, I did send emails to those lists and I don't think anybody's responded
… anybody gonna look or should I nudge again?
xfq: we can raise github issues
r12a: they're not terribly active at the moment
… Najib often comments on things but the hlreq folks haven't been active for a while now
<addison> #101
<gb> Action 101 research what if anything to do with dpub-pagination comments and old DPIG comments (on xfq) due 2024-05-30
<addison> #99
<gb> Action 99 ping unicode about emphasis skip property (see our #530) (on aphillips) due 2024-05-28
xfq: #101, still pending
addison: #99, done
… will bring it up with CSS in the upcoming call with them
<addison> #9
#98
<gb> Action 98 fix code points examples in lang-bidi-use-cases (on r12a) due 2024-05-23
<addison> #96
<gb> Action 96 evaluate and where necessary fix i18n-glossary#76 (on r12a) due 2024-05-02
<addison> #93
<gb> Action 93 create best practices for consumers in string-meta (on aphillips) due 2024-04-25
<addison> #90
<gb> Action 90 steal some of henri's text from scroll-to-text-fragment for string-search (on aphillips) due 2024-04-18
<addison> #89
<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18
<addison> #87
<gb> Action 87 write to IETF ADs about RFC9457 with JcK's assistance (on aphillips) due 2024-04-04
addison: #87, done
close #87
<gb> Closed issue #87
ACTION: addison: write to ietf group about rfc9457
<gb> Created action #106
<addison> close #87
<gb> Closed issue #87
<addison> #79
<gb> Action 79 schedule a follow-up call with WHATNOT in ~April (on aphillips) due 2024-03-07
<addison> #78
<gb> Action 78 compare infra to i18n-glossary export list and report back (on aphillips) due 2024-03-07
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #8
<gb> Action 8 Follow up on the status of Canvas and formatted text (on aphillips) due 18 Jul 2023
<addison> #7
<gb> Action 7 Remind shepherds to tend to their awaiting comment resolutions (Evergreen) (on aphillips, xfq, himorin, r12a, bert-github) due 18 Jul 2023
<addison> #4
<gb> 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
Info Share
<r12a> https://
<r12a> https://
r12a: Bidirectional Text (Part 1): The Basics of Bidi
… register here ^
RADAR Review
r12a: we have 3 documents for publication
… Kashmiri, Uighur, and Urdu
<addison> https://
r12a: will be published on Tuesday
xfq: haven't done HTML Ruby Markup Extensions
addison: Device Posture API is mine
… I have one minor comment
… we will review it in a minute
Pending Issue Review
atsushi: I have an issue on Controllers Documents
<addison> i18n-activity#1860
<gb> Issue 1860 type should be defined as identical to but not contain (by himorin) [pending] [wg:vc] [s:controller-document]
atsushi: I believe they want to match strings values in a JSON format
… but they do not refer to the string comparison def in Infra
https://
atsushi: I suppose they mean 'identical to'
addison: that doesn't seem like an i18n comment
… I'll tag that as non-i18n and then you can pass that along
atsushi: OK
<addison> i18n-activity#1859
<gb> Issue 1859 Device posture and direction interaction (by aphillips) [pending] [needs-resolution] [t:bidi_inline] [s:device-posture]
addison: I'll move controller-document to Completed
… since we're not going to track that issue
addison: my issue is #1859
<gb> Issue 1859 not found
addison: it's on the device posture spec
… device posture is whether a device is flat or folded
… they have an explainer about how device posture interacts with some other things
… so you can find out how the viewports are arranged
… and one of the interesting things is whether directionality might affect how things are arranged
… when you fold the device like a book
… anybody need more time?
I18N WG/IG recharter
addison: I'll forword
https://
xfq: Our WG and IG charter will expire at the end of September. I have prepared new charters for these two groups. They are mostly an extension of the current charters.
addison: need to rejoin the group after rechartering?
xfq: don't think so
… the scope is not changed
String-Meta Consumer guidance PR
<addison> https://
addison: does anybody have comments?
I18N+CSS prep
addison: we have a call with CSS on Tuesday
<addison> https://
addison: in addition to the item we mentioned earlier we only have 3 things on our list
r12a: there's been some discussion around quote
… the q element
<addison> w3c/
<gb> Issue 969 [css-content] Quote character choice must depend on surrounding language, not language of the quotation (by w3cbot) [s:css-content] [i:quotations] [needs-resolution] [t:typ_misc] [wg:css]
r12a: and how to choose quote marks
… maybe we should have some discussion on that
… in this meeting
<r12a> w3c/
<gb> Issue 5478 [css-content] Quote character choice must depend on surrounding language, not language of the quotation (by r12a) [css-content-3] [Agenda+] [Closed Accepted by CSSWG Resolution] [i18n-needs-resolution] [Needs Edits] [Needs Testcase
<gb> … (WPT)] [Needs Naming (Request to Bikeshed)] [Agenda+ i18n]
r12a: the CSSWG has been discussing it as well
… so perhaps we should put that on the agenda to keep the ball rolling
addison: OK
AOB?
addison: I have added that
r12a: we could informatively introduce them to the changes we've been making to the lreq documents
addison: OK
… I'll add that to the agenda as well