- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 21 Feb 2025 09:38:08 +0800
- To: www-international@w3.org
https://www.w3.org/2025/02/20-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
20 February 2025
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/events/meetings/b7edae68-f52c-4aab-a1a6-3c37459e0786/20250220T150000/
[3] https://www.w3.org/2025/02/20-i18n-irc
Attendees
Present
Addison, Atsushi, Bert, Fuqiao, JcK, Richard
Regrets
-
Chair
Addison Phillips
Scribe
atsushi, xfq
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]Pending Issues
6. [9]I18N+CSS Call
7. [10]Update qa-indic-graphemes.en.html (PR #634)
8. [11]Specdev changes related to ByteString
9. [12]AOB?
10. [13]Summary of action items
Meeting minutes
<gb> Issue 634 not found
Agenda Review
<gb> Issue 634 not found
Action Items
<addison> [14]https://github.com/w3c/i18n-actions/issues
[14] https://github.com/w3c/i18n-actions/issues
<addison> #157
<gb> [15]Action 157 write glossary proposal identifying options
and next steps for those options (on aphillips) due 2025-02-20
[15] https://github.com/w3c/i18n-actions/issues/157
<addison> #16
<gb> [16]Action 16 Keep track of line-breaking in Korean for
i18n-discuss#11 (on aphillips) due 1 Jan 2024
[16] https://github.com/w3c/i18n-actions/issues/16
addison: shipping final version of message format
<addison> #156
<gb> [17]Action 156 Figure out what is preferred for Fig 15 at
https://r12a.github.io/scripts/bopomofo/ontheweb#horhor (on
r12a) due 2025-01-28
[17] https://github.com/w3c/i18n-actions/issues/156
r12a: raised queation to influensers
<addison> close #156
<gb> Closed [18]issue #156
[18] https://github.com/w3c/i18n-actions/issues/156
<addison> #155
<gb> [19]Action 155 review glossary definitions for normativity
or candidates for normativity (on aphillips) due 2025-01-23
[19] https://github.com/w3c/i18n-actions/issues/155
r12a: and can close 156
<addison> close #155
<gb> Closed [20]issue #155
[20] https://github.com/w3c/i18n-actions/issues/155
addison: did for 155
<addison> #142
<gb> [21]Action 142 check if we can publish the new version of
jlreq (on himorin) due 2024-11-21
[21] https://github.com/w3c/i18n-actions/issues/142
<addison> #135
<gb> [22]Action 135 follow up on XR issue 1393 about locale in
session (on aphillips) due 2024-10-17
[22] https://github.com/w3c/i18n-actions/issues/135
<addison> #127
<gb> [23]Action 127 make a list of shared topics of interest
between TG2 and W3C-I18N (on aphillips) due 2024-09-30
[23] https://github.com/w3c/i18n-actions/issues/127
<addison> #89
<gb> [24]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[24] https://github.com/w3c/i18n-actions/issues/89
<addison> #33
<gb> [25]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[25] https://github.com/w3c/i18n-actions/issues/33
<addison> #7
<gb> [26]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[26] https://github.com/w3c/i18n-actions/issues/7
addison: 33, cleaned up this week
<addison> #4
<gb> [27]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on aphillips)
due 27 Jul 2023
[27] https://github.com/w3c/i18n-actions/issues/4
Info Share
[silent]
RADAR Review
<addison> [28]https://github.com/orgs/w3c/projects/91/views/1
[28] https://github.com/orgs/w3c/projects/91/views/1
addison: WebAuthn?
Pending Issues
<addison> [29]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[29] https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
<addison> [30]i18n-activity#1971
[30] https://github.com/w3c/i18n-activity/issues/1971
<gb> [31]Issue 1971 Clarification on `unicode-bidi` for `input
type text` and `ruby` (by w3cbot) [pending] [tracker] [s:html]
[whatwg] [Agenda+]
[31] https://github.com/w3c/i18n-activity/issues/1971
<addison> [32]whatwg/html#10896
[32] https://github.com/whatwg/html/issues/10896
<gb> [33]Issue 10896 Clarification on `unicode-bidi` for `input
type text` and `ruby` (by Ahmad-S792) [topic: rendering]
[topic: forms] [i18n-tracker]
[33] https://github.com/whatwg/html/issues/10896
addison: 1971, on html 10896, on ruby with bidi
… specific issue on isolate
atsushi: in JL-TF, this is considered as a sort of edge case,
similar to bidi in vertical writing
r12a: question is why you wouldn't want to isolate ruby
elements
ACTION: himorin: research activity 1971 (html 10896) about ruby
bidi isolation with jltf
<gb> Created [34]action #158
[34] https://github.com/w3c/i18n-actions/issues/158
<gb> Issue 634 not found
I18N+CSS Call
Update qa-indic-graphemes.en.html (PR #634)
<addison> [35]https://lists.w3.org/Archives/Public/
public-i18n-core/2025JanMar/0041.html
[35] https://lists.w3.org/Archives/Public/public-i18n-core/2025JanMar/0041.html
<addison> [36]https://www.w3.org/International/questions/
qa-indic-graphemes.en.html
[36] https://www.w3.org/International/questions/qa-indic-graphemes.en.html
<r12a> [37]https://deploy-preview-634--i18n-drafts.netlify.app/
questions/qa-indic-graphemes.en.html#partorder
[37] https://deploy-preview-634--i18n-drafts.netlify.app/questions/qa-indic-graphemes.en.html#partorder
<r12a> [38]https://deploy-preview-634--i18n-drafts.netlify.app/
questions/qa-indic-graphemes.en.html#multiplefamily
[38] https://deploy-preview-634--i18n-drafts.netlify.app/questions/qa-indic-graphemes.en.html#multiplefamily
r12a: material is url above
[introducing concerning points and updates]
r12a: this points to new version of article
addison: sounds good for me on this article, any objection?
<atsushi> +1
<r12a> [39]https://www.w3.org/TR/beng-gap/#issue87_segmentation
[39] https://www.w3.org/TR/beng-gap/#issue87_segmentation
r12a: above link, doing the same thing as gap analysis document
addison: continue to push into other gap documents?
<xfq> "The problem remains for several other scripts"
[discussion on differences around analyses:
Specdev changes related to ByteString
<addison> [40]w3c/bp-i18n-specdev#151
[40] https://github.com/w3c/bp-i18n-specdev/issues/151
<gb> [41]Issue 151 Mention `IsomorphicString` and update
`ByteString` guidance appropriately (by aphillips) [bug]
[Agenda+] [Best Practice]
[41] https://github.com/w3c/bp-i18n-specdev/issues/151
<addison> [42]bp-i18n-specdev#152
[42] https://github.com/w3c/bp-i18n-specdev/issues/152
<gb> [43]Issue 152 DOMString and protocols (by martinthomson)
[bug] [Agenda+] [Best Practice]
[43] https://github.com/w3c/bp-i18n-specdev/issues/152
addison: this is on section in spec-dev on DOMString
<addison> [44]https://w3c.github.io/
bp-i18n-specdev/#char_string
[44] https://w3c.github.io/bp-i18n-specdev/#char_string
<addison> [45]w3ctag/design-principles#454
[45] https://github.com/w3ctag/design-principles/issues/454
<gb> [46]Issue 454 I18N string best practices vs.
design-principles (by aphillips) [Status: In Progress] [Status:
Consensus to write] [Agenda+] [i18n-needs-resolution]
[46] https://github.com/w3ctag/design-principles/issues/454
addison: our bitestring text is slightly different from
commenter suggested
<addison> [47]w3c/bp-i18n-specdev#152
[47] https://github.com/w3c/bp-i18n-specdev/issues/152
<gb> [48]Issue 152 DOMString and protocols (by martinthomson)
[bug] [Agenda+] [Best Practice]
[48] https://github.com/w3c/bp-i18n-specdev/issues/152
addison: unclear point between what this points to, in
DOMString / ByteString
r12a: for representation of string, need to consider its
presentation
addison: talking about actual layout of protocol, it's could be
how encoded, not bytestring but sort of encoding
… might not write in detail in specification
JcK: more complexed point, for specification, how to composed
for transmission another transformation might be applied, in
underlayer protocol
r12a: meaning application protocol should not define details?
addison: binary data or sequence could be said as specific one,
but not for wire transfered data
r12a: something complex than current ones, needed?
addison: there is sequence of bytes, any other representations
could be over bytes
<addison> An isomorphic string is a string whose code points
are all in the range U+0000 NULL to U+00FF (ÿ), inclusive.
addison: as Unicode, above
addison: probably need to add some text here
… bytestring is distinct from other stuff,,, or something?
<addison> The ByteString type corresponds to byte sequences.
<addison> [49]https://webidl.spec.whatwg.org/#idl-ByteString
[49] https://webidl.spec.whatwg.org/#idl-ByteString
<xfq> "Specifications should only use ByteString for
interfacing with protocols that use bytes and strings
interchangeably, such as HTTP."
addison: need to work on proposal here, but wanted to talk
within group
<addison> [50]https://www.w3.org/TR/charmod/
[50] https://www.w3.org/TR/charmod/
addison: some separate document about byte and stuff...?
addison: I may write something, as wiki like document as
starter
ACTION: addison: write up proposal for specdev char-string
section, adding material that deals with the encoding interface
et al
<gb> Created [51]action #159
[51] https://github.com/w3c/i18n-actions/issues/159
<gb> Issue 634 not found
AOB?
r12a: looking in charmod fundamentals
<r12a> [52]https://www.w3.org/TR/charmod/#sec-Strings
[52] https://www.w3.org/TR/charmod/#sec-Strings
addison: maybe what we want to publlish is a new note that
supersedes fundamentals
… which just has the core terminology stuff
xfq: if the note is not long, we can just use specdev
JcK: I worry a little bit about pushing too much into specdev,
since nobody's going to look at specdev when developing a spec,
isn't it?
addison: seek to pull out and write as some text
Summary of action items
1. [53]himorin: research activity 1971 (html 10896) about ruby
bidi isolation with jltf
2. [54]addison: write up proposal for specdev char-string
section, adding material that deals with the encoding
interface et al
Received on Friday, 21 February 2025 01:38:24 UTC