- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 02 Feb 2024 10:36:23 +0800
- To: www-international@w3.org
https://www.w3.org/2024/02/01-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
01 February 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/6d544156-352c-46f2-b6ec-383b4e2462fb/20240201T150000/
[3] https://www.w3.org/2024/02/01-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, JcK, Richard
Regrets
-
Chair
Addison Phillips
Scribe
atsushi
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]RADAR Review
6. [9]Pending Issue Review
7. [10]WG labels
8. [11][baggage] Keys don't permit non-ASCII
9. [12]String-Meta paragraph direction vs. base direction
10. [13]Working With Timezones
Meeting minutes
Agenda Review
Action Items
<addison> #70
<gb> [14]Action 70 Create pull request for autocap issue (on
aphillips)
[14] https://github.com/w3c/i18n-actions/issues/70
<addison> #68
<gb> [15]Action 68 follow up with florian about testing with
kindle (on aphillips) due 2024-01-25
[15] https://github.com/w3c/i18n-actions/issues/68
addison: PR to HTML, not done yet
<addison> #66
<gb> [16]Action 66 fix base direction vs. paragraph direction
in string-meta (on aphillips) due 2024-01-18
[16] https://github.com/w3c/i18n-actions/issues/66
addison: PR exist, wanted to talk about what direction to go
<addison> #65
<gb> [17]Action 65 contact Daniel and check the Ethiopic word
boundary situation (on r12a) due 2023-12-26
[17] https://github.com/w3c/i18n-actions/issues/65
<addison> close #65
<gb> Closed [18]action #65
[18] https://github.com/w3c/i18n-actions/issues/65
r12a: did that, continue conversation
<addison> #64
<gb> [19]Action 64 Make list of HTML issues for February 22
call with WHATWG (on aphillips, xfq)
[19] https://github.com/w3c/i18n-actions/issues/64
addison: continue to work on this
<addison> #53
<gb> [20]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
[20] https://github.com/w3c/i18n-actions/issues/53
<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> #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
Info Share
addison: 1. message format open house, 20 Feb
… 2. contacted by Igalia, on proposal for personalization for
i18n
RADAR Review
<addison> [27]https://github.com/w3c/i18n-request/projects/1
[27] https://github.com/w3c/i18n-request/projects/1
addison: two new items
bert: I will take WebNN
addison: bitstring status list, some more pending issues
… but almost bottom of the document
RADAR Review
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: #1823, comment on buggage, marked as tracker, will
give a PR
<gb> [29]Issue 1823 [not found]
[29] https://github.com/w3c/i18n-actions/issues/1823
addison: 1821 is bitstring-status one, and would like to raise
<addison> [30]i18n-activity#1821
[30] https://github.com/w3c/i18n-activity/issues/1821
<gb> [31]Issue 1821 `credentialSubject.statusMessage`
localizable (by aphillips) [pending] [needs-resolution]
[t:lang_negotiation] [t:lang_declaration] [t:loc_localization]
[s:vc-bitstring-status-list]
https://github.com/w3c/i18n-activity/issues/1821
+1
<xfq> +1
<addison> [32]w3c/i18n-activity#1820
[32] https://github.com/w3c/i18n-activity/issues/1820
<gb> [33]Issue 1820 `statusPurpose` type `message` unclear (by
aphillips) [pending] [needs-resolution]
[s:vc-bitstring-status-list]
[33] https://github.com/w3c/i18n-activity/issues/1820
addison: will submit this
addison: 1820 is on the same spec
<xfq> +1
+1
<addison> [34]i18n-activity#1819
[34] https://github.com/w3c/i18n-activity/issues/1819
<gb> [35]Issue 1819 Should dir=auto with no strong characters
inherit directionality from parent or be ltr? (by w3cbot)
[pending] [tracker] [s:html] [spec-type-issue] [alreq] [hlreq]
[Agenda+I18N+WHATWG]
[35] https://github.com/w3c/i18n-activity/issues/1819
addison: 1819 is HTML one, agenda+ for WHATWG call items
<addison> [36]html#10097
[36] https://github.com/w3c/html/issues/10097
<gb> [37]Issue 10097 [not found]
[37] https://github.com/w3c/html/issues/10097
<addison> [38]whatwg/html#10097
[38] https://github.com/whatwg/html/issues/10097
<gb> [39]Issue 10097 Should dir=auto with no strong characters
inherit directionality from parent or be ltr? (by dbaron)
[i18n-tracker] [i18n-alreq] [i18n-hlreq]
[39] https://github.com/whatwg/html/issues/10097
addison: spec have changed to say with strong character, but it
breaks something
… reverting could give more control to content authors
r12a: in my comment, complecated issue
… don't know answer, but providing information
addison: my concern is content/context dependent of this issue
addison: need to raise into needs-resolution? or keep?
… agenda for later this month, and have some time for research
<addison> [40]i18n-activity#1818
[40] https://github.com/w3c/i18n-activity/issues/1818
<gb> [41]Issue 1818 Internationalization Checklist (by w3cbot)
[pending] [close?] [tracker] [s:webnn] [self_review]
[41] https://github.com/w3c/i18n-activity/issues/1818
<addison> [42]i18n-activity#1816
[42] https://github.com/w3c/i18n-activity/issues/1816
<gb> [43]Issue 1816 [css-text-4] It should be possible to
remove spaces while using text-autospace:no-autospace (by
w3cbot) [pending] [tracker] [s:css-text] [spec-type-issue]
[jlreq] [clreq]
[43] https://github.com/w3c/i18n-activity/issues/1816
<addison> [44]i18n-activity#1815
[44] https://github.com/w3c/i18n-activity/issues/1815
<gb> [45]Issue 1815 Discuss i18n-glossary and Infra
harmonization (by aphillips) [pending] [Agenda+I18N+WHATWG]
[s:infra]
[45] https://github.com/w3c/i18n-activity/issues/1815
addison: 1816 is CSS, and seems as regular one
r12a: might want to raise to needs-resolution for 1816
r12a: consider a case that with spaces inserted and without
spaces inserted within one document, one could want to remove
all spaces while no-autospace specified
addison: seems resonable
<addison> [46]i18n-activity#1815
[46] https://github.com/w3c/i18n-activity/issues/1815
<addison> [47]i18n-activity#1815
[47] https://github.com/w3c/i18n-activity/issues/1815
addison [48]w3c/i18n-activity#1815 is between i18n-glossary and
infra
… one case to be used is some spec does not intend to use infra
[48] https://github.com/w3c/i18n-activity/issues/1815
<gb> [49]Issue 1815 Discuss i18n-glossary and Infra
harmonization (by aphillips) [pending] [Agenda+I18N+WHATWG]
[s:infra]
[49] https://github.com/w3c/i18n-activity/issues/1815
xfq: good if we can have harmonization
<addison> [50]w3c/i18n-activity#1368
[50] https://github.com/w3c/i18n-activity/issues/1368
<gb> [51]Issue 1368 Consider fully supporting RTL and Bidi URLs
(by w3cbot) [pending] [close?] [tracker] [s:urlpattern]
[t:resid_misc]
[51] https://github.com/w3c/i18n-activity/issues/1368
xfq: this has moved from WICG to WHATWG
WG labels
r12a: spoken with PLH on labels in i18n tracking repository
<xfq> Background: [52]whatwg/sg#215
[52] https://github.com/whatwg/sg/issues/215
<gb> [53]CLOSED Issue 215 New standard: URLPattern (by
sisidovski)
[53] https://github.com/whatwg/sg/issues/215
[baggage] Keys don't permit non-ASCII
<addison> [54]w3c/baggage#99 (comment)
[54]
https://github.com/w3c/baggage/issues/99#issuecomment-1917634255
<gb> [55]Issue 99 Keys don't permit non-ASCII? (by aphillips)
[i18n-needs-resolution]
[55] https://github.com/w3c/baggage/issues/99
addison: long ago, we had this one
… asked them several times to support UTF-8
… reply comes at github issue
… they don't want change.
… move forward without change, or keep pushing?
xfq: would want to add note, even if they really don't want to
change
addison: see no technical reason for non-changing
addison: three possibility, accept argument, don't accept and
throw to transition, not accept argument but not to stop
transition
xfq: how about pushing back without stopping transition?
addison: if we want more discussion, happy to arrange call...
String-Meta paragraph direction vs. base direction
addison: will write to issue
<addison> [56]w3c/string-meta#84
[56] https://github.com/w3c/string-meta/pull/84
addison: a PR opened, 84
addison: we refer 'base direction' for most of places.
string-meta has explicit term 'paragraph direction'
… we've created this term, to distinguish string and exteria
… there are much inconsistent use between two
addison: paragraph direction is the term used in Unicode
glossary
… base direction is not
<addison> [57]https://unicode.org/glossary/#P
[57] https://unicode.org/glossary/#P
r12a: need to say about string as a whole or not
<addison> [58]https://unicode.org/glossary/#P
[58] https://unicode.org/glossary/#P
<addison> [59]https://w3c.github.io/
i18n-glossary/#dfn-base-direction
[59] https://w3c.github.io/i18n-glossary/#dfn-base-direction
addison: I'm fine with base direction is used, but needs
clarification
addison: will finish this PR, and back to check the final
result
Working With Timezones
addison: pushed some changes to there
xfq: will skip next two meetings, back 22
Received on Friday, 2 February 2024 02:36:26 UTC