Meeting minutes
Agenda Review
Action Items
<addison> #103
<gb> Action 103 Migrate RADAR project (on aphillips)
addison: github migration of RADAR
… will prepare by next meeting, and will let you know about
r12a: xfq is trying to investigate
<xfq> https://
xfq: actually did some before
… tried to produce something here
… looks like it's possible, good to try migration and use
<addison> #102
addison: let us talk next meeting
<gb> Action 102 ping alreq group to review our i18n-activity#1620 (on aphillips) due 2024-05-30
addison: sent email
<addison> https://
<addison> https://
addison: about direction etc., and email above
<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> #100
<gb> Action 100 complain to plh about the new IRC tool (on aphillips) due 2024-05-30
<addison> #99
<gb> Action 99 ping unicode about emphasis skip property (see our #530) (on aphillips) due 2024-05-28
addison: sent, and will get advice
xfq: about latin lreq, clreq meeting yesterday talked about
… would update document with the same structure as new alreq documents
… can do later
addison: sent email to Unicode, and how do all want to do
<addison> #98
<gb> Action 98 fix code points examples in lang-bidi-use-cases (on r12a) due 2024-05-23
addion: got information/advice from them, and check these
<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: more work on this, suggestion welcome
<addison> ```suggestion
<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> #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> #43
<gb> Action 43 pull together the list of win/mac/etc apis for setting base direction and/or language (on aphillips) due 2023-09-18
<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 r12a) due 27 Jul 2023
Info Share
<r12a> https://
r12a: FPWD of adlam layout document has out today
RADAR Review
<addison> https://
addison: no new incoming
… did pointer events lv3 issue
addison: did web translation api
bert: about web trasnlation explainer, did some check, and filed some
RADAR Review
Pending Issue Review
<addison> w3c/
<gb> Issue 1853 ‘Logical’ values for the ‘touch-action’ property (by bert-github) [s:pointerevents]
bert: found only one potential issue on pointer events
… about touch-action property
[describe draft review issue]
addison: this spec should work as other CSS specs, on bidi etc.
bert: CSS groups trying to use commonly sheared terminology like logical one
<xfq> pan-inline, pan-inline-start, pan-inline-end, pan-block, pan-block-start, pan-block-end
r12a: will take up these possible values and put as comments
<xfq> w3c/
<gb> Issue 272 Add logical dimension values for touch-action property, since logical is/has shipped (by jonjohnjohnson) [future]
xfq: there is existing issue above
<addison> w3c/
<addison> w3c/
<gb> Pull Request 496 Add logical/abstract values for `touch-action` (by patrickhlauke) [future]
bert: PR is corresponds to existing issue
addison: any objection to make this as needs-resolution?
bert: will file new issue, after rewritting
<addison> w3c/
<gb> Issue 1854 Internationalization checklist (by w3cbot) [tracker] [s:device-posture]
<addison> i18n-activity#1852
<gb> Issue 1852 [css-text-3][css-text-4] Japanese small kana and `line-break: normal` (by w3cbot) [pending] [tracker] [s:css-text] [spec-type-issue] [jlreq]
addison: added as agenda later
Emphasis skip property
<addison> https://
addison: suggested three different approaches
xfq: CJK and mongolian need to consider
… if they want to discuss on different behavior/character
addison: potentially these should be included in cldr
xfq: even for language dependent stuff, some of them can be in UCD instead of CLDR
String-Meta Consumer PR
<addison> w3c/
<gb> Pull Request 87 Create best practices for consumers (by aphillips)
<addison> https://
addison: some work done for this
addison: rewrote some masterd with clear text
addison: 3rd and 4th ones are somehow redundant
r12a: wondering but see some addition
addison: wondring about writing example box with html text
… something like how to isolate string and language metadata
… link to fancy illustration
<r12a> https://
r12a: here is some description on that front
<r12a> https://
<addison> https://
<r12a> https://
addison: do we have some action for fixing up isolation part?
addison: missing anything else?
AOB?
[silent]