- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 22 Mar 2024 13:42:37 +0800
- To: www-international@w3.org
https://www.w3.org/2024/03/21-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
21 March 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20240321T150000/
[3] https://www.w3.org/2024/03/21-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, JcK, Richard
Regrets
-
Chair
Addison Phillips
Scribe
Bert
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issue Review
6. [9]Specdev Work
7. [10]UTS55, UAX31 and URLPattern -- taken up
8. [11]Changes in GB 18030-2022
9. [12]"global-inclusion" community group
10. [13][focusgroup] i18n: should arrow key navigation follow
text direction?
11. [14]AOB?
12. [15]Summary of action items
Meeting minutes
<gb> [16]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[16] https://github.com/w3c/i18n-actions/issues/43
Agenda Review
Action Items
<addison> #84
<gb> [17]Action 84 follow up on i18n-glossary#51 (on r12a) due
2024-03-21
[17] https://github.com/w3c/i18n-actions/issues/84
<addison> [18]w3c/i18n-glossary#51
[18] https://github.com/w3c/i18n-glossary/issues/51
<gb> [19]Issue 51 About Tashkil : long vowel marks are called
Madd. (by ntounsi) [enhancement]
[19] https://github.com/w3c/i18n-glossary/issues/51
<addison> #83
<gb> [20]Action 83 replace the old core/langtags document with
a redirect and some appropriate text blurb (on xfq) due
2024-03-21
[20] https://github.com/w3c/i18n-actions/issues/83
<addison> close #83
xfq: Done
<gb> Closed [21]issue #83
[21] https://github.com/w3c/i18n-actions/issues/83
<addison> #82
<gb> [22]Action 82 publish khmer lreq with new format (on r12a)
due 2024-03-21
[22] https://github.com/w3c/i18n-actions/issues/82
r12a: working on it.
<addison> #81
<gb> [23]Action 81 write to kida-san about publishing
simple-ruby as note with appropriate status text (on aphillips)
due 2024-03-21
[23] https://github.com/w3c/i18n-actions/issues/81
<addison> close #81
<gb> Closed [24]issue #81
[24] https://github.com/w3c/i18n-actions/issues/81
addison: I wrote to him
<addison> #80
<gb> [25]Action 80 reply to Lisa about A11Y-I18N CG proposal
(on aphillips) due 2024-03-14
[25] https://github.com/w3c/i18n-actions/issues/80
addison: I answered.
<addison> close #80
<gb> Closed [26]issue #80
[26] https://github.com/w3c/i18n-actions/issues/80
<addison> #79
<gb> [27]Action 79 schedule a follow-up call with WHATNOT in
~April (on aphillips) due 2024-03-07
[27] https://github.com/w3c/i18n-actions/issues/79
addison: Some messages back and forth, but April meeting was
cancelled.
<addison> #78
<gb> [28]Action 78 compare infra to i18n-glossary export list
and report back (on aphillips) due 2024-03-07
[28] https://github.com/w3c/i18n-actions/issues/78
<addison> #77
<gb> [29]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
[29] https://github.com/w3c/i18n-actions/issues/77
<addison> #76
<gb> [30]Action 76 propose best practices for producers and for
examples in specs in string-meta (on aphillips) due 2024-03-07
[30] https://github.com/w3c/i18n-actions/issues/76
addison: Half done.
<addison> #75
<gb> [31]Action 75 work on developing new specdev material
about IDNs/domain names/etc. (on xfq) due 2024-02-29
[31] https://github.com/w3c/i18n-actions/issues/75
xfq: I made a pull request.
<addison> #72
<gb> [32]Action 72 update specdev to match string-meta with
string/block direction as appropriate (on aphillips) due
2024-02-22
[32] https://github.com/w3c/i18n-actions/issues/72
addison: I made a pull request.
<addison> #43
<gb> [33]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[33] https://github.com/w3c/i18n-actions/issues/43
addison: They are now in the explainer.
<addison> #33
<gb> [34]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[34] https://github.com/w3c/i18n-actions/issues/33
addison: I closed another few.
<addison> #12
<gb> [35]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips) due 18 Jul 2023
[35] https://github.com/w3c/i18n-actions/issues/12
addison: Done.
<addison> #8
<gb> [36]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[36] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [37]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[37] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [38]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a) due
27 Jul 2023
[38] https://github.com/w3c/i18n-actions/issues/4
Info Share
JcK: There is an IETF meeting. Restructuring some areas.
RADAR Review
<addison> [39]https://github.com/w3c/i18n-request/projects/1
[39] https://github.com/w3c/i18n-request/projects/1
addison: New item, Ethical Web Principles
… I'll add a due date.
… I'll take it.
Bert: Not quite done with MatML Core, found some typos, and
some maybe issues. Discuss next week.
xfq: Propose we move Privacy Principles to Completed.
ACTION: addison: send a note to privacy folks saying we did a
review with notes about i18n
<gb> Created [40]action #85
[40] https://github.com/w3c/i18n-actions/issues/85
Pending Issue Review
<addison> [41]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[41]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
<addison> [42]w3c/i18n-activity#1834
[42] https://github.com/w3c/i18n-activity/issues/1834
<gb> [43]Issue 1834 Clarify note on single character of mi as
italic (by himorin) [pending] [s:mathml] [wg:math]
[43] https://github.com/w3c/i18n-activity/issues/1834
Specdev Work
<addison> [44]https://github.com/w3c/bp-i18n-specdev/pulls
[44] https://github.com/w3c/bp-i18n-specdev/pulls
Bert: I will look at [45]w3c/i18n-activity#1834 as part of my
review.
[45] https://github.com/w3c/i18n-activity/issues/1834
<gb> [46]Issue 1834 Clarify note on single character of mi as
italic (by himorin) [pending] [s:mathml] [wg:math]
[46] https://github.com/w3c/i18n-activity/issues/1834
<addison> [47]w3c/bp-i18n-specdev#128
[47] https://github.com/w3c/bp-i18n-specdev/issues/128
<gb> [48]Pull Request 128 New section about IDNs (by xfq)
[48] https://github.com/w3c/bp-i18n-specdev/pull/128
<addison> [49]https://
deploy-preview-128--bp-i18n-specdev.netlify.app/
[49] https://deploy-preview-128--bp-i18n-specdev.netlify.app/
<xfq> [50]https://
deploy-preview-128--bp-i18n-specdev.netlify.app/#idn
[50] https://deploy-preview-128--bp-i18n-specdev.netlify.app/#idn
xfq: I added a section on domain names and best practices.
… One recommends not to refer to IDNA2003.
… Another recommends not to refer to Punycode.
addison: We should probably invert it. Rather than "don't do
this but do this", say "do this rather then this".
JcK: Also if you say don't use idna2003 and punycode, you in
fact make a comment about @@.
addison: We have a section about resource identifiers. Is that
where you put this?
xfq: Yes, I made a subsection.
… A more specialized section about domain names might be
useful.
addison: No, I think this is useful.
<addison> [51]w3c/bp-i18n-specdev#127
[51] https://github.com/w3c/bp-i18n-specdev/issues/127
addison: A little more work is needed.
<gb> [52]Pull Request 127 Sync with string-meta and fix UTF-16
linking (by aphillips)
[52] https://github.com/w3c/bp-i18n-specdev/pull/127
<addison> [53]https://
deploy-preview-127--bp-i18n-specdev.netlify.app/
[53] https://deploy-preview-127--bp-i18n-specdev.netlify.app/
<JcK> The comment about Punycode is that it is really just an
encoding, able to encode almost any string of Unicode code
points, while IDNA (certainly 2008 but even 2003) imposes
additional constraints of the names/strings.
addison: This one is tricky. I makes the changes to "base
direction" terminology.
xfq: Some guidelines are repeated.
addison: They are very similar.
<xfq> For any string field containing natural language text, it
MUST be possible to determine the language and string direction
of that specific string. Such determination SHOULD use metadata
at the string or document level and SHOULD NOT depend on
heuristics.
r12a: It must appear whereever people jump into the document.
addison: Merge?
xfq: Looks good.
<addison> [54]w3c/bp-i18n-specdev#126
[54] https://github.com/w3c/bp-i18n-specdev/pull/126
<gb> [55]Pull Request 126 Mention combining characters in the
template (by xfq)
[55] https://github.com/w3c/bp-i18n-specdev/pull/126
addison: Any objection to merging this?
No objections
UTS55, UAX31 and URLPattern -- taken up
<addison> [56]whatwg/urlpattern#43
[56] https://github.com/whatwg/urlpattern/issues/43
<gb> [57]Issue 43 Consider fully supporting RTL and Bidi URLs
(by mohsen1) [i18n-needs-resolution] [decided]
[57] https://github.com/whatwg/urlpattern/issues/43
addison: A while ago, there was an issue about bidi and URL
patterns.
… URL patterns are URLs with variables in them that can be
replaced.
<addison> [58]https://lists.w3.org/Archives/Public/
public-i18n-core/2024JanMar/0104.html
[58]
https://lists.w3.org/Archives/Public/public-i18n-core/2024JanMar/0104.html
addison: I'm not sure what to propose.
… It is similar to Message Format in a way.
… Do we want to ask them to do something? ask them to add
notes?
… Maybe ask Mark Davis and Robin Leroy to a call and ask for
guidance.
xfq: HAven't read tjhe recent, long comments yet.
Changes in GB 18030-2022
addison: I'll see if I can get MArk and Robin.
<addison> [59]https://lists.w3.org/Archives/Public/
public-i18n-core/2024JanMar/0101.html
[59]
https://lists.w3.org/Archives/Public/public-i18n-core/2024JanMar/0101.html
xfq: There is a new, incompatibe version of GB 18030.
… It is in operation since August or so,
… But IANA still refers to the old version.
… Should we do something as a group?
… Some people already contacted WHATWG and IANA.
… WebKit made changes to support the new version.
addison: The name is still GB 18030.
xfq: IANA explicitly refers to the 2000 version.
JcK: Underlying difficulty is that assumption with the
registration document many years ago is that codes would not
change.
addison: Is this an isolated case?
… Several vendors very much don't want to change a charset
defintion without changing its name as well.
addison: What should *we* do? Order popcorn? :-)
<xfq> [60]whatwg/encoding#312
[60] https://github.com/whatwg/encoding/issues/312
<gb> [61]Issue 312 Reflect changes in GB 18030-2022 (by
achristensen07) [i18n-tracker] [i18n-clreq]
[61] https://github.com/whatwg/encoding/issues/312
xfq: OK for IANA. What do we do for WHATWG?
… We have already tagged an issue.
JcK: Maybe we can tell the people who are pushing for
registration of the new version that they are likely to get a
new identifier, maybe a name with a year attached.
<xfq> [62]https://blog.unicode.org/2023/06/
icu-732-cldr-431-released-gb18030.html
[62]
https://blog.unicode.org/2023/06/icu-732-cldr-431-released-gb18030.html
addison: Would be interesting to know what ICU did. Their
encoder is widely dsitributed.
xfq: I found this ^^ about ICU
addison: Looks like they adopted the changes and made those the
default for GB 18030.
"global-inclusion" community group
<addison> [63]https://lists.w3.org/Archives/Member/
member-i18n-core/2024Mar/0004.html
[63]
https://lists.w3.org/Archives/Member/member-i18n-core/2024Mar/0004.html
addison: We discussed last week about a a11y i18n community
group.
… The a11y people now scheduled a meeting.
… Who wants to be our liaison to this group?
JcK: Could we write them a note that this very different if you
go beyond English?
<addison> [64]https://www.w3.org/community/global-inclusion/
[64] https://www.w3.org/community/global-inclusion/
addison: This CG is I think in reaction to us telling them
that.
xfq: Interesting topic, but I have little time.
addison: I'll join the group at least, to observe. You can all
do that.
[focusgroup] i18n: should arrow key navigation follow text direction?
<addison> [65]https://lists.w3.org/Archives/Public/
public-i18n-core/2024JanMar/0099.html
[65]
https://lists.w3.org/Archives/Public/public-i18n-core/2024JanMar/0099.html
addison: It's about making the arrow keys move in logical
direction. Traditionally, there is a difference in moving vs
selecting text.
r12a: Can we find people like the alreq people and get them
interested in the discussion?
addison: Ask on the alreq list?
r12a: You wouln't reach all people we'd want to reach.
… Maybe alreq and also Unicode list.
… UnicoRe
addison: Can you find email addresses of people I can write to?
… Or forward my mail?
AOB?
Summary of action items
1. [66]addison: send a note to privacy folks saying we did a
review with notes about i18n
Received on Friday, 22 March 2024 05:42:39 UTC