- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 23 Aug 2024 14:21:06 +0800
- To: www-international@w3.org
https://www.w3.org/2024/08/22-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
22 August 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/bc275b6e-6c38-4ed5-b324-6606a0c6cca7/20240822T150000/
[3] https://www.w3.org/2024/08/22-i18n-irc
Attendees
Present
Addison, atsushi, Bert, Fuqiao, JcK, r12a
Regrets
-
Chair
Addison Phillips
Scribe
xfq, addison
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]I18N+CSS Follow up
7. [10]input type=email discussion
8. [11]string-search
9. [12]AOB?
10. [13]Summary of action items
Meeting minutes
Agenda Review
Action Items
<addison> #90
<gb> [14]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[14] https://github.com/w3c/i18n-actions/issues/90
<addison> [15]w3c/string-search#23
[15] https://github.com/w3c/string-search/pull/23
<gb> [16]Pull Request 23 Address I18N-ACTION-90 by adding text
from scroll-to-text-fragment#233 (by aphillips)
[16] https://github.com/w3c/string-search/pull/23
addison: #90, still open
<addison> #33
<gb> [17]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[17] https://github.com/w3c/i18n-actions/issues/33
<addison> #16
<gb> [18]Action 16 Keep track of line-breaking in Korean for
i18n-discuss#11 (on aphillips) due 1 Jan 2024
[18] https://github.com/w3c/i18n-actions/issues/16
<addison> #8
<gb> [19]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[19] https://github.com/w3c/i18n-actions/issues/8
addison: #33, nothing interesting there
<addison> #7
<gb> [20]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[20] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [21]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
[21] https://github.com/w3c/i18n-actions/issues/4
Info Share
addison: #4, I pinged Sid
… he has a PR
… I'll be looking at that shortly
… UTW 2 has extended its deadline for accepting submissions
… they also have an early bird registration that runs out at
the end of the month
RADAR Review
<addison> [22]https://github.com/orgs/w3c/projects/91/views/1
[22] https://github.com/orgs/w3c/projects/91/views/1
addison: WebXR Device API
atsushi: I made that issue
… I believe there is no natural language
addison: I'll take it
Pending Issue Review
addison: Accessibility Conformance Testing (ACT) Rules Format
1.1?
Bert: not yet
I18N+CSS Follow up
[23]https://www.w3.org/2024/08/20-i18n-minutes.html
[23] https://www.w3.org/2024/08/20-i18n-minutes.html
[24]w3c/csswg-drafts#4154
[24] https://github.com/w3c/csswg-drafts/issues/4154
<gb> [25]Issue 4154 Consider Canonicalization of language tags
in :lang() selector maching (by frivoal) [selectors-4]
[i18n-tracker] [Needs Review of Proposed Text] [selectors-5]
[Agenda+ i18n]
[25] https://github.com/w3c/csswg-drafts/issues/4154
<addison> xfq: one thing that probably important to mention is
about this issue ^^
<addison> ... they have a PR to fix this
<addison> ... and it was merged, but they wanted a review first
before closing
[26]https://drafts.csswg.org/selectors-4/#the-lang-pseudo
The element’s content language matches a language range if its content l
anguage, as represented in BCP 47 syntax, matches the given language ran
ge in an extended filtering operation per [RFC4647] Matching of Language
Tags (section 3.3.2). Both the content language and the language range
must be canonicalized and converted to extlang form as per
section 4.5 of [RFC5646] prior to the extended filtering operation. The
matching is performed case-insensitively within the ASCII range.
[26] https://drafts.csswg.org/selectors-4/#the-lang-pseudo
ACTION: addison: review css 4154 :lang() selector
canonicalization
<gb> Created [27]action #117
[27] https://github.com/w3c/i18n-actions/issues/117
<addison> xfq: also had some discussion about characters to
skip for emphasis marks, who should maintain Unicode or CSS
addison: Unicode was not delighted by the idea of maintaining
something particularly if it might be specialized to something
like CSS
xfq: but it's not specific to CSS
addison: it seems to be specific to emphasis everywhere
input type=email discussion
[28]whatwg/html#10522
[28] https://github.com/whatwg/html/pull/10522
<gb> [29]Pull Request 10522 Add support for internationalized
email addresses (by aphillips) [i18n-tracker]
[29] https://github.com/whatwg/html/pull/10522
addison: Henri seems to be productively engaged with it
… so I need to go through his comments and make revisions
… it looks like progress
… @@1
string-search
[30]w3c/string-search#23
[30] https://github.com/w3c/string-search/pull/23
<gb> [31]Pull Request 23 Address I18N-ACTION-90 by adding text
from scroll-to-text-fragment#233 (by aphillips)
[31] https://github.com/w3c/string-search/pull/23
[32]https://deploy-preview-23--w3c-string-search.netlify.app/
[32] https://deploy-preview-23--w3c-string-search.netlify.app/
addison: a lot of the changes go into the top of section 2
… where I'm describing what substring match is
… and at the very bottom of the document, currently, which
should be an appendix, @@2
[33]https://
deploy-preview-23--w3c-string-search.netlify.app/#text-frag-lan
g
[33]
https://deploy-preview-23--w3c-string-search.netlify.app/#text-frag-lang
AOB?
[34]w3c/i18n-drafts#327
[34] https://github.com/w3c/i18n-drafts/pull/327
<gb> [35]Pull Request 327 Add info about HTML and JS new
features (by xfq)
[35] https://github.com/w3c/i18n-drafts/pull/327
[36]https://deploy-preview-327--i18n-drafts.netlify.app/
questions/qa-date-format.en
[36]
https://deploy-preview-327--i18n-drafts.netlify.app/questions/qa-date-format.en
xfq: please review this ^
addison: I don't see temporal mentioned in a scroll
xfq: I chose not to mention Temporal when I raised the PR,
because I wanted to wait until there are at least two shipping
implementations
addison: what you might want to mention is that there's work
coming
… or that this article doesn't talk about temporal
r12a: do we know which browser engines currently support
temporal?
[37]https://caniuse.com/mdn-javascript_builtins_temporal
[37] https://caniuse.com/mdn-javascript_builtins_temporal
<r12a> [38]https://caniuse.com/temporal
[38] https://caniuse.com/temporal
addison: it's 0%
r12a: Opera Mini supports it?
xfq: it's unknown
xfq: added a Preview link to the first comment
Summary of action items
1. [39]addison: review css 4154 :lang() selector
canonicalization
Received on Friday, 23 August 2024 06:21:08 UTC