- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 14 Mar 2025 16:48:59 +0800
- To: www-international@w3.org
https://www.w3.org/2025/03/13-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
13 March 2025
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/events/meetings/b7edae68-f52c-4aab-a1a6-3c37459e0786/20250313T150000/
[3] https://www.w3.org/2025/03/13-i18n-irc
Attendees
Present
addison, Atsushi, Bert, Fuqiao, Richard
Regrets
-
Chair
Addison Phillips
Scribe
atsushi, xfq
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]Review RADAR
5. [8]Pending Issue Review
6. [9]HTML dir=auto inheritance (i18n-activity 1819)
7. [10]Specdev PR about characters and truncation
Meeting minutes
<r12a> addison, meeting will start in 50 mins from now
<Bert> My regrets, I need to attend another meeting.
Agenda Review
Action Items
<addison> [11]https://github.com/w3c/i18n-actions/issues
[11] https://github.com/w3c/i18n-actions/issues
<addison> #160
<gb> [12]Action 160 review graphemes in specdev and add
balinese example and otherwise fix the text (on aphillips) due
2025-03-06
[12] https://github.com/w3c/i18n-actions/issues/160
addison: in agenda item
<addison> #159
<gb> [13]Action 159 write up proposal for specdev char-string
section, adding material that deals with the encoding interface
et al (on aphillips) due 2025-02-27
[13] https://github.com/w3c/i18n-actions/issues/159
<addison> #158
<gb> [14]Action 158 research activity 1971 (html 10896) about
ruby bidi isolation with jltf (on himorin) due 2025-02-27
[14] https://github.com/w3c/i18n-actions/issues/158
atsushi: sent a comment to the issue
<addison> close #158
<gb> Closed [15]issue #158
[15] https://github.com/w3c/i18n-actions/issues/158
<addison> #157
<gb> [16]Action 157 write glossary proposal identifying options
and next steps for those options (on aphillips) due 2025-02-20
[16] https://github.com/w3c/i18n-actions/issues/157
<addison> #142
<gb> [17]Action 142 check if we can publish the new version of
jlreq (on himorin) due 2024-11-21
[17] https://github.com/w3c/i18n-actions/issues/142
addison: did, review last week, and will come back
atsushi: kida-san will talk with r12a and xfq
r12a: can I ask what the issue is Kida-san is going to ask?
atsushi: What is the scope of editors
addison: Contributors will be a much longer list than the list
of editors
atsushi: yes, should be
<addison> close #142
<gb> Closed [18]issue #142
[18] https://github.com/w3c/i18n-actions/issues/142
<addison> #135
<gb> [19]Action 135 follow up on XR issue 1393 about locale in
session (on aphillips) due 2024-10-17
[19] https://github.com/w3c/i18n-actions/issues/135
<addison> #127
<gb> [20]Action 127 make a list of shared topics of interest
between TG2 and W3C-I18N (on aphillips) due 2024-09-30
[20] https://github.com/w3c/i18n-actions/issues/127
addison: 135, pending
addison: 127, also pending
<addison> #89
<gb> [21]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[21] https://github.com/w3c/i18n-actions/issues/89
<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
xfq: 89, no progress on dark mode
addison: 33, one item in agenda
<addison> #7
<gb> [23]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[23] https://github.com/w3c/i18n-actions/issues/7
addison, 7, see no item on this front
<addison> #4
<gb> [24]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on aphillips)
due 27 Jul 2023
[24] https://github.com/w3c/i18n-actions/issues/4
Info Share
<addison> [25]https://messageformat.unicode.org/
[25] https://messageformat.unicode.org/
addison: unicode now have site for message format
… nice web site, but some issues on text
Review RADAR
<addison> [26]https://github.com/orgs/w3c/projects/91/views/1
[26] https://github.com/orgs/w3c/projects/91/views/1
addison: no new incoming
addison: completed WebAuthn lv3
… and in agenda item
Pending Issue Review
<addison> [27]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue%20state%3Aopen%20label%3As%3Awebauthn%20
[27] https://github.com/w3c/i18n-activity/issues?q=is:issue state:open label:s:webauthn
<addison> [28]w3c/webauthn#1643 (comment)
[28] https://github.com/w3c/webauthn/issues/1643#issuecomment-2379550440
addison: web authentication lv 3, went through, see no new
issue but bunch of old issues still exist
<gb> [29]Issue 1643 Use of in-field metadata not preferred (by
aphillips) [type:technical] [i18n-needs-resolution] [@Risk]
[29] https://github.com/w3c/webauthn/issues/1643
addison: in TPAC we had some discussion and raised placeholder,
on what they should do, but haven't performed yet
… will go back and ask on this
addison: despite from our recommendation in string, they
developed their own way to deal with
… they have not performed alignment yet
<addison> [30]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[30] https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
addison: any other pending issue?
HTML dir=auto inheritance (i18n-activity 1819)
xfq: one item in INFRA for pending, without topic label
… will clean up
<addison> [31]i18n-activity#1819
[31] https://github.com/w3c/i18n-activity/issues/1819
<gb> [32]Issue 1819 Should dir=auto with no strong characters
inherit directionality from parent or be ltr? (by w3cbot)
[close?] [tracker] [s:html] [needs-attention] [i:bidi_text]
[spec-type-issue] [alreq] [hlreq] [t:bidi_markup]
[Agenda+I18N+WHATWG]
[32] https://github.com/w3c/i18n-activity/issues/1819
<gb> … [whatwg]
<addison> [33]whatwg/html#10097
[33] https://github.com/whatwg/html/issues/10097
<gb> [34]CLOSED Issue 10097 Should dir=auto with no strong
characters inherit directionality from parent or be ltr? (by
dbaron) [i18n-tracker] [i18n-alreq] [i18n-hlreq]
[34] https://github.com/whatwg/html/issues/10097
addison: last comment in the issue, I was pushing personally,
not to do that
… if the content of auto are all neutrals, make sense to meet
with
<addison> my comment: [35]whatwg/html#10097 (comment)
[35] https://github.com/whatwg/html/issues/10097#issuecomment-2371483752
r12a: I see comment from fantasai there
addison: my point is why we should do this way
r12a: fantasai seems to propose huristic based one
[checking browser behavior using bidi text demo tool]
r12a: one problem, difference between hebrew and arabic, in
terms of number ordering
addison: still expecting to be default to surrounding text
r12a: using not number but range like 10-20, change happends
between two
addison: if no strong character in sequence
addison: agreed on concern, and propose to reopen this with
statement on concern
r12a: suggest to provide simple example and explanation
Specdev PR about characters and truncation
<addison> [36]w3c/bp-i18n-specdev#153
[36] https://github.com/w3c/bp-i18n-specdev/pull/153
<gb> [37]Pull Request 153 Rewrite the character introduction
(by aphillips)
[37] https://github.com/w3c/bp-i18n-specdev/pull/153
<addison> [38]https://
deploy-preview-153--bp-i18n-specdev.netlify.app/#characters
[38] https://deploy-preview-153--bp-i18n-specdev.netlify.app/#characters
addison: kind of wanting to have more meta conversation
addison: making terminology consistent, and fix truncation
stuff
<r12a> [39]https://www.w3.org/International/articles/
definitions-characters/index.en.html#characters
[39] https://www.w3.org/International/articles/definitions-characters/index.en.html#characters
r12a: it's best to make sure people can understand mustard
stuff, mustard is the core of this document
addison: need to review mustards in character section coming
from charmod
<Bert> ("back of a napkin": isn't it "back of an envelop" or
just "napkin"?)
xfq: not all of description in non-mustard is essential
xfq: suggesting, going through non-mustard part
addison: I have thought about removing the example boxes and
just making all the text flat
r12a: that would be a bit heavy
addison: I would be totally happy not to have any of these
because I'm rewriting Essentials
r12a: and it may be that we need to improve Essentials
addison: A) I could commit this and then we can iterate
… B) I can push this to one side and we try it the other
direction
… I should merge this to the ED
… and we'll work on the truncating separately from the
characters section
r12a: sounds good
addison: I could revert the truncation part and put it in
another PR
r12a: thank you addison for doing all this stuff
Received on Friday, 14 March 2025 08:49:14 UTC