- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 28 Feb 2025 09:12:09 +0800
- To: www-international@w3.org
https://www.w3.org/2025/02/27-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
27 February 2025
[2]Agenda. [3]IRC log.
[2] https://www.w3.org/events/meetings/b7edae68-f52c-4aab-a1a6-3c37459e0786/20250227T150000/
[3] https://www.w3.org/2025/02/27-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][string-search] Sequences with variation selectors
7. [10]AOB?
8. [11]Summary of action items
Meeting minutes
Agenda Review
Action Items
<addison> [12]https://github.com/w3c/i18n-actions/issues
[12] https://github.com/w3c/i18n-actions/issues
<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: Started, not tready
<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: not discussed yet. But ruby should be isolated.
<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: Not finished
<addison> #142
<gb> [16]Action 142 check if we can publish the new version of
jlreq (on himorin) due 2024-11-21
[16] https://github.com/w3c/i18n-actions/issues/142
atsushi: Still discussing with r12a
… about changes section.
… Development of the Rec
… most of the history disappeared
… I worry about if we break the names of the orgs that
contributed.
… most of the active contributors in the editors list, but not
sure I have their @@
… Merge them into... may have missing items
… I would keep the affiliations, but not correct them.
r12a: I'm looking for the pull request...
<r12a> [17]w3c/jlreq#453
[17] https://github.com/w3c/jlreq/pull/453
<gb> [18]Pull Request 453 Turning editors into contributor
section (by himorin)
[18] https://github.com/w3c/jlreq/pull/453
r12a: I think you are over-complicating what I was thinking
about.
… Currently jlreq lists names and affiliations (or IE).
… In the new proposal the same list, but split in two.
… I proposed you put the affiliation s at the time in brackets
after the name.
atsushi: Let me revert to the original list then
r12a shows his screen.
r12a: I propose you put parentheses after the names with the
affiliations when they worked on the doc.
<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: not yet
<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: 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
addison: Did some clean up
<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> #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
Radar Review
<addison> [25]https://github.com/orgs/w3c/projects/91/views/1
[25] https://github.com/orgs/w3c/projects/91/views/1
Pending Issue Review
<addison> [26]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[26] https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
<addison> [27]i18n-activity#1990
[27] https://github.com/w3c/i18n-activity/issues/1990
<gb> [28]Issue 1990 Add localization support for
GPUCompilationMessage.message and GPUError.message (by w3cbot)
[pending] [tracker] [s:webgpu] [Agenda+]
[28] https://github.com/w3c/i18n-activity/issues/1990
addison: They put in a note. I'm going back in to see if any of
our strategies applies.
<atsushi> +1
addison: Do we need to chnage the label from tracker to
needs-resolutiion?
xfq: Yes, I think so
r12a: When we remove pending labels, we should add t: label
… and maybe language-specific labels as well.
addison: Agreed
r12a: Look through specdev and find the related section, The ID
of that section gives you the label
[string-search] Sequences with variation selectors
<xfq> [29]w3c/string-search#24
[29] https://github.com/w3c/string-search/pull/24
<gb> [30]Pull Request 24 Sequences with variation selectors (by
xfq)
[30] https://github.com/w3c/string-search/pull/24
<xfq> [31]https://
deploy-preview-24--w3c-string-search.netlify.app/#variation-sel
ectors
[31] https://deploy-preview-24--w3c-string-search.netlify.app/#variation-selectors
xfq: We discussed this once before and I made some chnages.
Added a table with examples. Changed the section name to
mention variation selectors.
… Not only applies to ideographs.
addison: Might want to include a search term in example 5 that
includes a variation selector
xfq: Add a new row?
addison: Yes
r12a: If you have more than one row, the contents need to tbe
aligned at the top
… To make it clearer
… Our default table style probably doesn't do that.
addison: Can also break up separate cells
… match/doesn't match checkbox-y thing
xfq: I'll try to tweak it
r12a: In that case merge the 3 cells on the left
addison: Otherwise looks good
… DO we want to say thing about other language variation
selectors?
r12a: May want to say that other languages have variation
selectors.
… Example is perhaps not explicit enough.
xfq: I'll add that.
r12a: Some change to specdev is needed for scripts that keep
conjuncts together.
… Not sure it is significant for this document.
<addison> [32]https://w3c.github.io/bp-i18n-specdev/#characters
[32] https://w3c.github.io/bp-i18n-specdev/#characters
addison: There is a note in section 4 in specdev
… green box
r12a: I have an example for Balinese
addison: I'll look it up.
<r12a> [33]https://r12a.github.io/scripts/bali/ban.html
[33] https://r12a.github.io/scripts/bali/ban.html
addison: Would you like to work on this section?
<r12a> [34]https://r12a.github.io/scripts/bali/ban_vocab.html
[34] https://r12a.github.io/scripts/bali/ban_vocab.html
addison: Or in a month?
<r12a> [35]https://r12a.github.io/scripts/bali/
ban_vocab.html?q=%E1%AD%84
[35] https://r12a.github.io/scripts/bali/ban_vocab.html?q=᭄
ACTION: addison: review graphemes in specdev and add balinese
example and otherwise fix the text
<gb> Created [36]action #160
[36] https://github.com/w3c/i18n-actions/issues/160
<r12a> [37]https://r12a.github.io/scripts/bali/
ban_vocab.html?q=%E1%AD%84%E2%92%B8
[37] https://r12a.github.io/scripts/bali/ban_vocab.html?q=᭄Ⓒ
r12a: If you clikc on the green term, you'll get a breakdown of
the combining character sequences. If you click on the green
button at the bottom of the list you'll get the grapheme
clusters.
addison: What is the issue with "user-perceived character" in
Unicode?
r12a: They are not necesarily perceived as a character by the
user.
… "Typographic unit" may be better.
AOB?
<xfq> [38]w3c/typography#88
[38] https://github.com/w3c/typography/issues/88
<gb> [39]Issue 88 Use title case? (by xfq)
[39] https://github.com/w3c/typography/issues/88
xfq: I propsoe we use title case for @@, too.
… I have a pull request for that
… I don't thing we have guidelines for that in W3C.
<addison> [40]https://www.w3.org/TR/typography/
[40] https://www.w3.org/TR/typography/
r12a: The docs that use titlecase use it only on H1, don't
they?
addison: In the doc ^^, the auto-generated titles use
titlecase.
… I'm used to seeing titlecase all the time. When I edit, I
usually use it.
r12a: I tend to use downcase section headings.
You can see whether addison or r12a edited by looking at the
uppercase. :-)
xfq: This issue is specifically about the document title, not
the section titles.
addison: Not sure it matters.
r12a: Happy to use titlecase on the document title.
No objections to titlecase for the document title. xfq will
merge the PR
Summary of action items
1. [41]addison: review graphemes in specdev and add balinese
example and otherwise fix the text
Received on Friday, 28 February 2025 01:12:25 UTC