- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 19 Jan 2024 14:56:07 +0800
- To: www-international@w3.org
https://www.w3.org/2024/01/18-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
18 January 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20240118T150000/
[3] https://www.w3.org/2024/01/18-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, Richard
Regrets
JcK
Chair
Addison Phillips
Scribe
addison, Bert
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Info Share
6. [9]RADAR Review
7. [10]Pending Issue Review
8. [11]I18N+CSS
9. [12]WHATWG + I18N Prep
10. [13]Summary of action items
Meeting minutes
Agenda Review
Action Items
gb, list open actions
<gb> Found actions in w3c/i18n-actions: #67, #66, #65, #64,
#53, #47, #43, #35, #33, #18, #16, #12, #11, #8, #7, #4
#67
<gb> [14]Action 67 add some comments to CSS #8511 (on r12a) due
2024-01-23
[14] https://github.com/w3c/i18n-actions/issues/67
#66
<gb> [15]Action 66 fix base direction vs. paragraph direction
in string-meta (on aphillips) due 2024-01-18
[15] https://github.com/w3c/i18n-actions/issues/66
#65
<gb> [16]Action 65 contact Daniel and check the Ethiopic word
boundary situation (on r12a) due 2023-12-26
[16] https://github.com/w3c/i18n-actions/issues/65
#64
<gb> [17]Action 64 Make list of HTML issues for February 22
call with WHATWG (on aphillips, xfq)
[17] https://github.com/w3c/i18n-actions/issues/64
addison: See agenda item later.
#53
<gb> [18]Action 53 come up with a set of information CSS want
the i18n group to provide support for generic font families (on
frivoal, fantasai) due 2023-11-01
[18] https://github.com/w3c/i18n-actions/issues/53
#47
<gb> [19]Action 47 make the CSSWG aware of Warichu (on frivoal)
due 2023-10-04
[19] https://github.com/w3c/i18n-actions/issues/47
#43
<gb> [20]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[20] https://github.com/w3c/i18n-actions/issues/43
addison: Done in the issue.
… Starting to put a Q&A together.
#33
<gb> [21]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[21] https://github.com/w3c/i18n-actions/issues/33
addison: Down to around 60
#12
<gb> [22]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips) due 18 Jul 2023
[22] https://github.com/w3c/i18n-actions/issues/12
#8
<gb> [23]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[23] https://github.com/w3c/i18n-actions/issues/8
#7
<gb> [24]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[24] https://github.com/w3c/i18n-actions/issues/7
#4
<gb> [25]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a) due
27 Jul 2023
[25] https://github.com/w3c/i18n-actions/issues/4
Info Share
RADAR Review
<r12a> [26]https://typo.social/@ri/111764452166307113
[26] https://typo.social/@ri/111764452166307113
Info Share
r12a: Made tool to search for characters or a regexp.
… This will find chars that browser search won't show.
[27]https://github.com/w3c/i18n-request/projects/1
[27] https://github.com/w3c/i18n-request/projects/1
RADAR Review
addison: No incoming requests and nothing in review.
Pending Issue Review
addison: We have no pending issues.
I18N+CSS
<xfq> [28]https://www.w3.org/2024/01/16-i18n-minutes.html
[28] https://www.w3.org/2024/01/16-i18n-minutes.html
addison: There was an i18n-CSS call. Anything that came up,
anything we need to do?
xfq: Nothing essential. Just some infoshare on HTML ruby
document, about <rb> and <rbc>
ACTION: addison: follow up with florian about testing with
kindle
<gb> Created [29]action #68
[29] https://github.com/w3c/i18n-actions/issues/68
<xfq> [30]w3c/csswg-drafts#8511
[30] https://github.com/w3c/csswg-drafts/issues/8511
<gb> [31]Issue 8511 [css-text-4] text-autospace: what gets
copied? (by fantasai) [css-text-4] [Agenda+] [i18n-tracker]
[i18n-jlreq] [i18n-clreq] [i18n-eurlreq] [Agenda+ i18n]
[31] https://github.com/w3c/csswg-drafts/issues/8511
xfq: Also discussed a few GitHib issues, on inserted spacing
and whether it should be copied by copy&paste
addison: That is the issue r12a has an action for.
WHATWG + I18N Prep
[32]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3AAgenda%2BI18N%2BWHATWG
[32]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:Agenda+I18N+WHATWG
addison: Has labels on issues for agenda+ for different
meetings.
[33]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3As%3Ahtml
[33]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:s:html
addison: First issue is whether to add a named entity to HTML
for narrow no-break space. HTML previously said no, but
discussion goes on.
… If you have things to add...
xfq: Thanks for compiling that list. I'll see if we need to add
more.
… Some issues like ruby could be labeled "needsresolution",
although WhatWG is a different organization.
r12a: Wait with <rb> and <rtc>.
r12a: On 22nd, will WhatWG come to our meeting?
<xfq> [34]w3c/vc-di-bbs#114
[34] https://github.com/w3c/vc-di-bbs/issues/114
<gb> [35]Issue 114 "XML Schema formatted date string" not
specific enough (by aphillips) [i18n-needs-resolution]
[35] https://github.com/w3c/vc-di-bbs/issues/114
addison: It's their regular meeting.
xfq: Reply I got on XML issue ^^ is that it is in a different
spec, Data Integrity.
… If they indeed remove the duplicated text, we can close the
issue.
addison: I will reply to the comment.
<xfq> [36]w3c/i18n-glossary#62
[36] https://github.com/w3c/i18n-glossary/pull/62
xfq: I added a pull request with target=_blank for external
links in the glossary.
r12a: addison's list with HTML issues is useful. Can we do the
same with CSS issues? Can you select by labels with a wildcard,
"css-*"?
[37]https://w3c.github.io/horizontal-issue-tracker/index#
[37] https://w3c.github.io/horizontal-issue-tracker/index
addison: In plh's comment tracker ^^, you can more easily see
all CSS issues.
… xfq, would you be interested in finding a way to more easily
group and sort all CSS issues?
xfq: I'll think about it.
[38]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+css
[38]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+css
<r12a> [39]https://docs.github.com/en/search-github/
searching-on-github/
searching-issues-and-pull-requests#search-by-label
[39]
https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests#search-by-label
xfq: Maybe we can ask plh to let his bot add a special "css"
label to all issues with css-* labels.
r12a: Or a label that identifies the WG. That could maybe be
added automatically by the bot.
addison: I will ask plh.
ACTION: addison: ask PLH to add a WG feature to the gh bot
<gb> Created [40]action #69
[40] https://github.com/w3c/i18n-actions/issues/69
Summary of action items
1. [41]addison: follow up with florian about testing with
kindle
2. [42]addison: ask PLH to add a WG feature to the gh bot
Received on Friday, 19 January 2024 06:56:10 UTC