Meeting minutes
<r12a> addison, meeting will start in 50 mins from now
<Bert> My regrets, I need to attend another meeting.
Agenda Review
Action Items
<addison> https://
<addison> #160
<gb> Action 160 review graphemes in specdev and add balinese example and otherwise fix the text (on aphillips) due 2025-03-06
addison: in agenda item
<addison> #159
<gb> Action 159 write up proposal for specdev char-string section, adding material that deals with the encoding interface et al (on aphillips) due 2025-02-27
<addison> #158
<gb> Action 158 research activity 1971 (html 10896) about ruby bidi isolation with jltf (on himorin) due 2025-02-27
atsushi: sent a comment to the issue
<addison> close #158
<gb> Closed issue #158
<addison> #157
<gb> Action 157 write glossary proposal identifying options and next steps for those options (on aphillips) due 2025-02-20
<addison> #142
<gb> Action 142 check if we can publish the new version of jlreq (on himorin) due 2024-11-21
addison: did, review last week, and will come back
atsushi: kida-san will talk with r12a and xfq
r12a: can I ask what the issue is Kida-san is going to ask?
atsushi: What is the scope of editors
addison: Contributors will be a much longer list than the list of editors
atsushi: yes, should be
<addison> close #142
<gb> Closed issue #142
<addison> #135
<gb> Action 135 follow up on XR issue 1393 about locale in session (on aphillips) due 2024-10-17
<addison> #127
<gb> Action 127 make a list of shared topics of interest between TG2 and W3C-I18N (on aphillips) due 2024-09-30
addison: 135, pending
addison: 127, also pending
<addison> #89
<gb> Action 89 update i18n specs to support dark mode (on xfq) due 2024-04-18
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
xfq: 89, no progress on dark mode
addison: 33, one item in agenda
<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, 7, see no item on this front
<addison> #4
<gb> Action 4 Work with respec and bikeshed to provide the character markup template as easy-to-use markup (on aphillips) due 27 Jul 2023
Info Share
<addison> https://
addison: unicode now have site for message format
… nice web site, but some issues on text
Review RADAR
<addison> https://
addison: no new incoming
addison: completed WebAuthn lv3
… and in agenda item
Pending Issue Review
<addison> https://
<addison> w3c/
addison: web authentication lv 3, went through, see no new issue but bunch of old issues still exist
<gb> Issue 1643 Use of in-field metadata not preferred (by aphillips) [type:technical] [i18n-needs-resolution] [@Risk]
addison: in TPAC we had some discussion and raised placeholder, on what they should do, but haven't performed yet
… will go back and ask on this
addison: despite from our recommendation in string, they developed their own way to deal with
… they have not performed alignment yet
<addison> https://
addison: any other pending issue?
HTML dir=auto inheritance (i18n-activity 1819)
xfq: one item in INFRA for pending, without topic label
… will clean up
<addison> i18n-activity#1819
<gb> Issue 1819 Should dir=auto with no strong characters inherit directionality from parent or be ltr? (by w3cbot) [close?] [tracker] [s:html] [needs-attention] [i:bidi_text] [spec-type-issue] [alreq] [hlreq] [t:bidi_markup] [Agenda+I18N+WHATWG]
<gb> … [whatwg]
<addison> whatwg/
<gb> CLOSED Issue 10097 Should dir=auto with no strong characters inherit directionality from parent or be ltr? (by dbaron) [i18n-tracker] [i18n-alreq] [i18n-hlreq]
addison: last comment in the issue, I was pushing personally, not to do that
… if the content of auto are all neutrals, make sense to meet with
<addison> my comment: whatwg/
r12a: I see comment from fantasai there
addison: my point is why we should do this way
r12a: fantasai seems to propose huristic based one
[checking browser behavior using bidi text demo tool]
r12a: one problem, difference between hebrew and arabic, in terms of number ordering
addison: still expecting to be default to surrounding text
r12a: using not number but range like 10-20, change happends between two
addison: if no strong character in sequence
addison: agreed on concern, and propose to reopen this with statement on concern
r12a: suggest to provide simple example and explanation
Specdev PR about characters and truncation
<addison> w3c/
<gb> Pull Request 153 Rewrite the character introduction (by aphillips)
<addison> https://
addison: kind of wanting to have more meta conversation
addison: making terminology consistent, and fix truncation stuff
<r12a> https://
r12a: it's best to make sure people can understand mustard stuff, mustard is the core of this document
addison: need to review mustards in character section coming from charmod
<Bert> ("back of a napkin": isn't it "back of an envelop" or just "napkin"?)
xfq: not all of description in non-mustard is essential
xfq: suggesting, going through non-mustard part
addison: I have thought about removing the example boxes and just making all the text flat
r12a: that would be a bit heavy
addison: I would be totally happy not to have any of these because I'm rewriting Essentials
r12a: and it may be that we need to improve Essentials
addison: A) I could commit this and then we can iterate
… B) I can push this to one side and we try it the other direction
… I should merge this to the ED
… and we'll work on the truncating separately from the characters section
r12a: sounds good
addison: I could revert the truncation part and put it in another PR
r12a: thank you addison for doing all this stuff