- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 01 Nov 2024 10:18:51 +0800
- To: www-international@w3.org
https://www.w3.org/2024/10/31-i18n-minutes.html
text version:
– DRAFT –
Internationalization Working Group Teleconference
31 October 2024
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/bc275b6e-6c38-4ed5-b324-6606a0c6cca7/20241031T150000/
[3] https://www.w3.org/2024/10/31-i18n-irc
Attendees
Present
addison, Atsushi, Ben Allen, Bert, Fuqiao, JcK, Richard,
xfq
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]Pending Issue Review
6. [9]Issue 599
7. [10]Working with Time and Timezones as DNOTE?
8. [11]Specdev PRs
9. [12]AOB?
10. [13]Summary of action items
Meeting minutes
Agenda Review
Action Items
<addison> #137
<gb> [14]Action 137 Create new meeting series in the W3C
calendar (on xfq)
[14] https://github.com/w3c/i18n-actions/issues/137
<addison> close #137
<gb> Closed [15]issue #137
[15] https://github.com/w3c/i18n-actions/issues/137
<addison> #135
addison: added action to xfq, and edited calendar event, so
done #137
<gb> [16]Action 135 follow up on XR issue 1393 about locale in
session (on aphillips) due 2024-10-17
[16] https://github.com/w3c/i18n-actions/issues/135
addison: will have chat next week for #135
<addison> #134
<gb> [17]Action 134 file an issue about making input respect
locale (on aphillips) due 2024-10-05
[17] https://github.com/w3c/i18n-actions/issues/134
<addison> #131
<gb> [18]Action 131 follow up on input-events action (on
aphillips)
[18] https://github.com/w3c/i18n-actions/issues/131
addison: #131 done
<addison> close #131
<gb> Closed [19]issue #131
[19] https://github.com/w3c/i18n-actions/issues/131
<addison> #128
<gb> [20]Action 128 perform review of issues for inclusion in
specdev (on xfq) due 2024-09-30
[20] https://github.com/w3c/i18n-actions/issues/128
xfq: #128 not yet
<addison> #127
<gb> [21]Action 127 make a list of shared topics of interest
between TG2 and W3C-I18N (on aphillips) due 2024-09-30
[21] https://github.com/w3c/i18n-actions/issues/127
<addison> #125
<gb> [22]Action 125 propose creating a UTR for text-emphasis
skip if we can get help with maintain (on aphillips) due
2024-09-30
[22] https://github.com/w3c/i18n-actions/issues/125
addison: #125 done, but wait for next CSS+i18n call for
confirmation
<addison> #114
<gb> [23]Action 114 read through i18n-activity#1659 and report
on whether we're satisfied (on r12a) due 2024-08-22
[23] https://github.com/w3c/i18n-actions/issues/114
<addison> #90
<gb> [24]Action 90 steal some of henri's text from
scroll-to-text-fragment for string-search (on aphillips) due
2024-04-18
[24] https://github.com/w3c/i18n-actions/issues/90
<addison> #89
<gb> [25]Action 89 update i18n specs to support dark mode (on
xfq) due 2024-04-18
[25] https://github.com/w3c/i18n-actions/issues/89
<addison> #33
<gb> [26]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[26] https://github.com/w3c/i18n-actions/issues/33
<addison> #8
<gb> [27]Action 8 Follow up on the status of Canvas and
formatted text (on aphillips) due 18 Jul 2023
[27] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [28]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github) due 18 Jul 2023
[28] https://github.com/w3c/i18n-actions/issues/7
<addison> #4
<gb> [29]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on aphillips,
r12a) due 27 Jul 2023
[29] https://github.com/w3c/i18n-actions/issues/4
addison: done some clean ups on repo, not see any other
Info Share
addison: did have unicode technical workshp, xfq was there
… presentation about string-meta, received good feedbacks
… linking with our groups
… also some conversation on message format there
xfq: good event, met with lots of people
… lightweight event, exchanged email with some for like joining
to WG
… will discuss with them
addison: good for recruting for our activities, also I've
chatted with several colleagues
xfq: chatted with credential colleagues on slack for review,
and requesting review on FPWD
… guided them for review
… they may try to use FPWD one
addison: did some review, also they marked self review with
tracker
… add some template to follow these?
ACTION: xfq: add text to the issue templates to clarify what to
use when
<gb> Created [30]action #138
[30] https://github.com/w3c/i18n-actions/issues/138
xfq: would do
RADAR Review
<addison> [31]https://github.com/orgs/w3c/projects/91/views/1
[31] https://github.com/orgs/w3c/projects/91/views/1
xfq: can take EPUB 3.3
bert: will take media capabilities
atsushi: take picture in picture
addison: will take Vision document
… also already working on FedCM
addison: any waiting comment resolution?
Pending Issue Review
<addison> [32]https://github.com/w3c/i18n-activity/
issues?q=is%3Aissue+is%3Aopen+label%3Apending
[32]
https://github.com/w3c/i18n-activity/issues?q=is:issue+is:open+label:pending
addison: some for FedCM spec
<addison> #1927
<gb> Issue 1927 not found
<addison> [33]i18n-activity#1927
[33] https://github.com/w3c/i18n-activity/issues/1927
<gb> [34]Issue 1927 Add a further explanation of `ltr` and
`rtl` (based on ePub). (by w3cbot) [pending] [tracker]
[s:rdf-concepts]
[34] https://github.com/w3c/i18n-activity/issues/1927
addison: this is PR from rdf colleagues, if no other comment,
will mark as tracker and close
<addison> [35]i18n-activity#1924
[35] https://github.com/w3c/i18n-activity/issues/1924
<gb> [36]Issue 1924 ContactAddress 'region' inconsistencies (by
w3cbot) [pending] [tracker] [s:contact-picker] [wg:das]
[wg:webapps]
[36] https://github.com/w3c/i18n-activity/issues/1924
addison: some from contact picker
Issue 599
<addison> [37]i18n-activity#599
[37] https://github.com/w3c/i18n-activity/issues/599
<gb> [38]Issue 599 highly detailed text in video content (by
stpeter) [pending] [tracker] [s:mst-content-hint] [wg:webrtc]
[Agenda+]
[38] https://github.com/w3c/i18n-activity/issues/599
<addison> [39]w3c/mst-content-hint#35
[39] https://github.com/w3c/mst-content-hint/issues/35
<gb> [40]Issue 35 highly detailed text in video content (by
aphillips) [Ready for PR] [i18n-tracker]
[40] https://github.com/w3c/mst-content-hint/issues/35
addison: propose to do as needs-resolution
xfq: +1
atsushi: +1
<r12a> +1
addison: will change label
Working with Time and Timezones as DNOTE?
<addison> [41]https://lists.w3.org/Archives/Public/
public-i18n-core/2024OctDec/0029.html
[41]
https://lists.w3.org/Archives/Public/public-i18n-core/2024OctDec/0029.html
<addison> The old doc: [42]https://www.w3.org/TR/timezone
[42] https://www.w3.org/TR/timezone
<addison> The new version: [43]https://w3c.github.io/timezone
[43] https://w3c.github.io/timezone
addison: timezone spec, find new version have large change
xfq: republish with note status?
r12a: draft or not
addison: do we want to publish v2 now, or draft?
r12a: state for no, long time elapsed
addison: republish with warning box in-line?
<Bert> (The Process doc says very little about (Draft) Notes,
but it says ‘Both Notes and Draft Notes can be updated by
republishing as a Note or Draft Note.’ without ‘respectively’,
so I think they can be republised with either status.)
r12a: add action to go through and see any issue
… for addison
ACTION: addison: review old timezone note to ensure all content
is present and accounted for
<gb> Created [44]action #139
[44] https://github.com/w3c/i18n-actions/issues/139
r12a: we should check before any publication
addison: will check for next week, and evaluate any missing
point or correction
Specdev PRs
<addison> [45]w3c/bp-i18n-specdev#145
[45] https://github.com/w3c/bp-i18n-specdev/pull/145
<gb> [46]Pull Request 145 Allow Ruby use in non-CJKM languages
(by jyasskin) [Agenda+] [Best Practice] [normative]
[46] https://github.com/w3c/bp-i18n-specdev/pull/145
addison: take a look at PRs
addison: #145, proposal to make text less CJKM restrictive on
ruby use case
<gb> Issue 145 not found
addison: discussed before,,,
r12a: use in these language are prioritized, but what mean by
this change?
xfq: prioritized part is not clear
<addison> Ruby markup in HTML is designed primarily for
Chinese, <a data-cite="jlreq#usage_of_ruby">Japanese</a>,
Korean, and Mongolian requirements. Note that ruby is also
sometimes used to associate annotations with text in other
languages. However, specifications should avoid proposing new
uses for it.
addison: proposal above
r12a: like last sentence
addison: like pulling out from mustard? or something else?
… for middle part
[ruby for phonetic or not, another mechanism or?]
<r12a> [47]https://r12a.github.io/blog/201708.html#20190304
[47] https://r12a.github.io/blog/201708.html#20190304
xfq: what jeffery means was ruby display style is different
from markup
<addison> Ruby markup in HTML is designed primarily for
Chinese, <a data-cite="jlreq#usage_of_ruby">Japanese</a>,
Korean, and Mongolian requirements. While sometimes used in
other languages, such annotation generally should use other
mechanisms. Specifications should avoid proposing new uses for
Ruby.
r12a: was no answer for what happens when it is use with
non-CJK
addison: how about proposal above again?
<addison> Annotation in other languages should use other
mechanisms.
addison: propose change to this PR?
[all agreed]
ACTION: addison: reply to specdev 145 including proposal
discussed in telecon
<gb> Created [48]action #140
[48] https://github.com/w3c/i18n-actions/issues/140
r12a: use word 'semantics'
<addison> [49]w3c/bp-i18n-specdev#146
[49] https://github.com/w3c/bp-i18n-specdev/pull/146
<gb> [50]Pull Request 146 Fix examples (by aphillips)
[50] https://github.com/w3c/bp-i18n-specdev/pull/146
<addison> [51]https://github.com/w3c/bp-i18n-specdev/pull/146/
files
[51] https://github.com/w3c/bp-i18n-specdev/pull/146/files
addison: resolves comment from i18n activity in hebrew
<addison> [52]https://
deploy-preview-146--bp-i18n-specdev.netlify.app/#sec_dir_defs
[52]
https://deploy-preview-146--bp-i18n-specdev.netlify.app/#sec_dir_defs
<addison> [53]https://
deploy-preview-146--bp-i18n-specdev.netlify.app/#rlmlrm
[53]
https://deploy-preview-146--bp-i18n-specdev.netlify.app/#rlmlrm
[on examples in non-English]
<addison> [54]https://
deploy-preview-146--bp-i18n-specdev.netlify.app/#example-1
[54]
https://deploy-preview-146--bp-i18n-specdev.netlify.app/#example-1
addison: add "you will be expected to show" but "...." or
something
<addison> [55]w3c/bp-i18n-specdev#142
[55] https://github.com/w3c/bp-i18n-specdev/pull/142
<gb> [56]Pull Request 142 Add a note about EGCs (by aphillips)
[56] https://github.com/w3c/bp-i18n-specdev/pull/142
addison: extending graphime cluster one
<xfq> [57]https://
deploy-preview-142--bp-i18n-specdev.netlify.app/#characters
[57]
https://deploy-preview-142--bp-i18n-specdev.netlify.app/#characters
addison: it's introducing front
r12a: example 4 caption should alter language
addison: here, trying to address comments without touching what
UTC doesn't touch
… will go back through original text for corner cases
<r12a> [58]https://www.w3.org/International/articles/
definitions-characters/index.en.html#characters
[58]
https://www.w3.org/International/articles/definitions-characters/index.en.html#characters
[about examples]
AOB?
Summary of action items
1. [59]xfq: add text to the issue templates to clarify what to
use when
2. [60]addison: review old timezone note to ensure all content
is present and accounted for
3. [61]addison: reply to specdev 145 including proposal
discussed in telecon
Received on Friday, 1 November 2024 02:18:56 UTC