Meeting minutes
Agenda Review
Action Items
<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> #87
<gb> Action 87 write to IETF ADs about RFC9457 with JcK's assistance (on aphillips) due 2024-04-04
addison: wrote,
<addison> #79
<gb> Action 79 schedule a follow-up call with WHATNOT in ~April (on aphillips) due 2024-03-07
addison: next WHATNOT is 18th, will ask them with our list
<addison> #78
<gb> Action 78 compare infra to i18n-glossary export list and report back (on aphillips) due 2024-03-07
addison: for may
<addison> #77
<gb> Action 77 create an issue against html requesting the list of named entities based on work in action 73 (on r12a) due 2024-03-07
addison: will be discussed in topic
<addison> #76
<gb> Action 76 propose best practices for producers and for examples in specs in string-meta (on aphillips) due 2024-03-07
addison: PR raised
<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: message format will be published today
<addison> #33
<gb> Action 33 Close issues marked `close?` or bring to WG for further review (on aphillips)
<addison> #12
<gb> Action 12 Upgrade/edit the explainer to address issues raised by google (on aphillips) due 18 Jul 2023
<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
r12a: might someone ping also
Info Share
[silent]
<addison> https://
addison: no new incoming
Pending Issue Review
<addison> https://
<addison> #1846
<gb> Issue 1846 not found
<addison> w3c/i18n-activity#1846
<gb> Issue 1846 Improve handling of malformed unicode bidi control characters (by w3cbot) [pending] [tracker] [s:html] [spec-type-issue] [alreq] [hlreq] [whatwg]
addison: break isolation by inserting individual bidi control sequences into text
xfq: they seem wanted to update behaviors?
addison: only happens when user inputs bidi controls
addison: challenge is easy to describe but hard to implement
r12a: should already happen within content editable ones
addison: it seems, to isolate unicode bidi with inserting specifical bdi/bdo-s
xfq: bdi is designed to isolate bidi control, but bidi control characters are directly inserted, it will be broken..
… may need to think about side effects
xfq: have we WG consensus on this?
addison: I think we want to right things happen...
… solution could be more complex than he coded here
addison: like pdi or fsi
ACTION: addison: respond to i18n-activity#1846
<gb> Created action #91
addison: actioned to myself to respond on this
<addison> w3c/i18n-activity#1844
<gb> Issue 1844 Add getOSLanguage proposal (by w3cbot) [pending] [tracker] [s:webextensions] [cg:webextensions]
addison: it's to get OS language to be used by browser
xfq: without using browser accept-language, but system language
r12a: it's good to be aware of accept-language, not OS language
atsushi: if Accept-Language in English but OS lang is Japanese
… from i18n point of view it might be better to get these kind of information
… but maybe there are privacy concerns
addison: it's super common that browser set language from OS one
addison: would ping them that privacy is aware on this change
<addison> w3c/
<gb> Issue 252 Introducing `browser.i18n.getOSLanguage` (by carlosjeurissen) [supportive: chrome] [supportive: safari] [supportive: firefox] [proposal] [topic: localization] [i18n-tracker]
xfq: also RFC id need to be updated
<addison> https://
ACTION: xfq: fix the rfc3066bis page
<gb> Created action #92
xfq: will fix this page
… could be fixed by redirecting to bcp page
New Thai and Lao lreq docs
<addison> https://
<r12a> https://
<addison> https://
r12a: simply copied from my stuff
… and would want to publish FPWD
<r12a> https://
r12a: also this is alreq long time existing
addison: arabic one is quite nice
… need resolution for two FPWDs
<addison> proposed: publish a first public working draft of lao and thai layout requirements (two documents)
+1
<r12a> +1
<addison> +1
<Bert> +1
<xfq> +1
<atsushi> +1
RESOLUTION: publish lao layout requirements and thai layout requirements as fpwd
r12a: next is for chinese layout, and will plan to link to clreq
<gb> Pull Request 603 Move editors to authors (by xfq)
r12a: clreq colleagues updates
RFC9457
addison: followed up with them on anything to say
<addison> https://
addison: some comment provided
… one is to fix RFC, another is how you all like to review IETF stuff?
addison: any comment?
[discussion on I-Ds]
addison: keep action item open.
CLDR and a Locale Service
addison: wrote to Unicode, and got some responces
addison: they are about publishing CLDR 45
… will take some more time
string-meta and PR about producers
<addison> w3c/
<gb> Pull Request 86 Add best practices for writing examples and for producers (by aphillips)
addison: one open PR above
<addison> https://
addison: do need to identify some more?
<addison> https://
<addison> https://
addison: one section for producers, another for examples
xfq: we only have note for producers, but not for consumers
addison: some difference on two, it's document for spec authors
addison: we could add more stuff later
xfq: seems good to me
r12a: in my rader, commit and will comment later
addison: will merge
<addison> close #76
<gb> Closed issue #76
ACTION: addison: create best practices for consumers in string-meta
<gb> Created action #93
AOB?
[silent]