- From: Fuqiao Xue <xfq@w3.org>
- Date: Sun, 21 Apr 2024 12:24:12 +0800
- To: www-international@w3.org
https://www.w3.org/2024/04/18-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
18 April 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20240418T150000/
[3] https://www.w3.org/2024/04/18-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, Richard, xfq
Regrets
-
Chair
addison
Scribe
atsushi, xfq
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]Pending Issue Review
5. [8]New Thai and Lao lreq docs
6. [9]RFC9457
7. [10]CLDR and a Locale Service
8. [11]string-meta and PR about producers
9. [12]AOB?
10. [13]Summary of action items
11. [14]Summary of resolutions
Meeting minutes
Agenda Review
Action Items
<addison> #90
<gb> [15]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[15] https://github.com/w3c/i18n-actions/issues/90
<addison> #87
<gb> [16]Action 87 write to IETF ADs about RFC9457 with JcK's
assistance (on aphillips) due 2024-04-04
[16] https://github.com/w3c/i18n-actions/issues/87
addison: wrote,
<addison> #79
<gb> [17]Action 79 schedule a follow-up call with WHATNOT in
~April (on aphillips) due 2024-03-07
[17] https://github.com/w3c/i18n-actions/issues/79
addison: next WHATNOT is 18th, will ask them with our list
<addison> #78
<gb> [18]Action 78 compare infra to i18n-glossary export list
and report back (on aphillips) due 2024-03-07
[18] https://github.com/w3c/i18n-actions/issues/78
addison: for may
<addison> #77
<gb> [19]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
[19] https://github.com/w3c/i18n-actions/issues/77
addison: will be discussed in topic
<addison> #76
<gb> [20]Action 76 propose best practices for producers and for
examples in specs in string-meta (on aphillips) due 2024-03-07
[20] https://github.com/w3c/i18n-actions/issues/76
addison: PR raised
<addison> #43
<gb> [21]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[21] https://github.com/w3c/i18n-actions/issues/43
addison: message format will be published today
<addison> #33
<gb> [22]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[22] https://github.com/w3c/i18n-actions/issues/33
<addison> #12
<gb> [23]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips) due 18 Jul 2023
[23] https://github.com/w3c/i18n-actions/issues/12
<addison> #8
<gb> [24]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[24] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [25]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[25] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [26]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a) due
27 Jul 2023
[26] https://github.com/w3c/i18n-actions/issues/4
r12a: might someone ping also
Info Share
[silent]
<addison> [27]https://github.com/w3c/i18n-request/projects/1
[27] https://github.com/w3c/i18n-request/projects/1
addison: no new incoming
Pending Issue Review
<addison> [28]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[28]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
<addison> #1846
<gb> Issue 1846 not found
<addison> [29]w3c/i18n-activity#1846
[29] https://github.com/w3c/i18n-activity/issues/1846
<gb> [30]Issue 1846 Improve handling of malformed unicode bidi
control characters (by w3cbot) [pending] [tracker] [s:html]
[spec-type-issue] [alreq] [hlreq] [whatwg]
[30] https://github.com/w3c/i18n-activity/issues/1846
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 [31]i18n-activity#1846
[31] https://github.com/w3c/i18n-activity/issues/1846
<gb> Created [32]action #91
[32] https://github.com/w3c/i18n-actions/issues/91
addison: actioned to myself to respond on this
<addison> [33]w3c/i18n-activity#1844
[33] https://github.com/w3c/i18n-activity/issues/1844
<gb> [34]Issue 1844 Add getOSLanguage proposal (by w3cbot)
[pending] [tracker] [s:webextensions] [cg:webextensions]
[34] https://github.com/w3c/i18n-activity/issues/1844
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> [35]w3c/webextensions#252
[35] https://github.com/w3c/webextensions/issues/252
<gb> [36]Issue 252 Introducing `browser.i18n.getOSLanguage` (by
carlosjeurissen) [supportive: chrome] [supportive: safari]
[supportive: firefox] [proposal] [topic: localization]
[i18n-tracker]
[36] https://github.com/w3c/webextensions/issues/252
xfq: also RFC id need to be updated
<addison> [37]https://www.w3.org/International/core/langtags/
rfc3066bis.html
[37] https://www.w3.org/International/core/langtags/rfc3066bis.html
ACTION: xfq: fix the rfc3066bis page
<gb> Created [38]action #92
[38] https://github.com/w3c/i18n-actions/issues/92
xfq: will fix this page
… could be fixed by redirecting to bcp page
New Thai and Lao lreq docs
<addison> [39]https://lists.w3.org/Archives/Public/
public-i18n-core/2024AprJun/0011.html
[39]
https://lists.w3.org/Archives/Public/public-i18n-core/2024AprJun/0011.html
<r12a> [40]https://www.w3.org/International/sealreq/lao/
indexnew
[40] https://www.w3.org/International/sealreq/lao/indexnew
<addison> [41]https://www.w3.org/International/sealreq/thai/
indexnew
[41] https://www.w3.org/International/sealreq/thai/indexnew
r12a: simply copied from my stuff
… and would want to publish FPWD
<r12a> [42]https://www.w3.org/International/alreq/indexnew
[42] https://www.w3.org/International/alreq/indexnew
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> [43]Pull Request 603 Move editors to authors (by xfq)
[43] https://github.com/w3c/clreq/pull/603
r12a: clreq colleagues updates
RFC9457
addison: followed up with them on anything to say
<addison> [44]https://lists.w3.org/Archives/Member/
member-i18n-core/2024Apr/0014.html
[44]
https://lists.w3.org/Archives/Member/member-i18n-core/2024Apr/0014.html
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> [45]w3c/string-meta#86
[45] https://github.com/w3c/string-meta/pull/86
<gb> [46]Pull Request 86 Add best practices for writing
examples and for producers (by aphillips)
[46] https://github.com/w3c/string-meta/pull/86
addison: one open PR above
<addison> [47]https://
deploy-preview-86--string-meta.netlify.app/
[47] https://deploy-preview-86--string-meta.netlify.app/
addison: do need to identify some more?
<addison> [48]https://
deploy-preview-86--string-meta.netlify.app/#bp-producers
[48]
https://deploy-preview-86--string-meta.netlify.app/#bp-producers
<addison> [49]https://
deploy-preview-86--string-meta.netlify.app/#bp-writing-spec-exa
mples
[49]
https://deploy-preview-86--string-meta.netlify.app/#bp-writing-spec-examples
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 [50]issue #76
[50] https://github.com/w3c/i18n-actions/issues/76
ACTION: addison: create best practices for consumers in
string-meta
<gb> Created [51]action #93
[51] https://github.com/w3c/i18n-actions/issues/93
AOB?
[silent]
Summary of action items
1. [52]addison: respond to i18n-activity#1846
2. [53]xfq: fix the rfc3066bis page
3. [54]addison: create best practices for consumers in
string-meta
Summary of resolutions
1. [55]publish lao layout requirements and thai layout
requirements as fpwd
Received on Sunday, 21 April 2024 04:24:13 UTC