- From: Fuqiao Xue <xfq@w3.org>
- Date: Fri, 22 Sep 2023 12:00:06 +0800
- To: www-international@w3.org
https://www.w3.org/2023/09/21-i18n-minutes.html
text version:
[1]W3C
[1] https://www.w3.org/
– DRAFT –
Internationalization Working Group Teleconference
21 September 2023
[2]Agenda. [3]IRC log.
[2]
https://www.w3.org/events/meetings/c5b143d1-0a5b-4adb-8d60-0f5f9bfe5a41/20230921T150000/
[3] https://www.w3.org/2023/09/21-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]TPAC Fallout
7. [10]w3c/adapt#240
8. [11]WCAG 2.2 PR# 3347: another look
9. [12]definition of string (w3c/bp-i18n-specdev#117)
10. [13]AOB?
11. [14]Summary of action items
Meeting minutes
<gb> [15]Issue 240 Could we build symbolic annotations with
existing Web standards? (by DuncanMacWeb) [i18n-tracker]
[15] https://github.com/w3c/adapt/issues/240
<gb> [16]Pull Request 117 Add additional definitions of
'string' (w3c/i18n-actions#41) (by aphillips)
[16] https://github.com/w3c/bp-i18n-specdev/issues/117
Agenda Review
<gb> [17]Issue 240 Could we build symbolic annotations with
existing Web standards? (by DuncanMacWeb) [i18n-tracker]
[17] https://github.com/w3c/adapt/issues/240
<gb> [18]Pull Request 117 Add additional definitions of
'string' (w3c/i18n-actions#41) (by aphillips)
[18] https://github.com/w3c/bp-i18n-specdev/issues/117
xfq: one item, PR against code point styling, for /TR/ design
Action Items
<gb> Found actions in w3c/i18n-actions: #44, #43, #42, #41,
#39, #36, #35, #33, #32, #18, #16, #15, #13, #12, #11, #10, #9,
#8, #7, #5, #4
<addison> #44
<gb> [19]Action 44 follow up on the bidi thread of rdf-star (on
r12a) due 2023-09-19
[19] https://github.com/w3c/i18n-actions/issues/44
addison: we had traffic on rdf-star issue
<addison> #43
<gb> [20]Action 43 pull together the list of win/mac/etc apis
for setting base direction and/or language (on aphillips) due
2023-09-18
[20] https://github.com/w3c/i18n-actions/issues/43
<addison> #42
addison: started making a list, and will insert into explainer
later
<gb> [21]Action 42 work on tc39 proposal (meet with addison and
eemeli to start) (on xfq) due 2023-09-18
[21] https://github.com/w3c/i18n-actions/issues/42
xfq: haven't chance to talk with them yet
r12a: relevant to that, in breakout, director general of ECMA
said that W3C colleagues could jump into talk with them more
… she contacted by email to me
… I've mentioned that individual contributor are working within
us
<addison> #41?
<gb> [22]Action 41 propose new specdev text on strings for xml
(on aphillips) due 2023-09-07
[22] https://github.com/w3c/i18n-actions/issues/41
addison: PR is filed and in agenda later
<addison> #39
<gb> [23]Action 39 develop best practice guidelines for
name-like fields (on aphillips) due 2023-08-31
[23] https://github.com/w3c/i18n-actions/issues/39
<addison> #36
<gb> [24]Action 36 follow up with murata-san about wcag status
(on aphillips) due 2023-08-31
[24] https://github.com/w3c/i18n-actions/issues/36
<r12a> Samina Husain is Director General at ECMA
<addison> close #36
addison: close that
<gb> Closed [25]action #36
[25] https://github.com/w3c/i18n-actions/issues/36
<addison> #35
<gb> [26]Action 35 make the edits of CSS #5478 (on fantasai)
due 2023-08-30
[26] https://github.com/w3c/i18n-actions/issues/35
<addison> #33
<gb> [27]Action 33 Close issues marked `close?` or bring to WG
for further review (on aphillips)
[27] https://github.com/w3c/i18n-actions/issues/33
addison: made more progress on this yesterday, and closed many
<gb> [28]Pull Request 117 Add additional definitions of
'string' (w3c/i18n-actions#41) (by aphillips)
[28] https://github.com/w3c/bp-i18n-specdev/issues/117
<gb> [29]Issue 240 Could we build symbolic annotations with
existing Web standards? (by DuncanMacWeb) [i18n-tracker]
[29] https://github.com/w3c/adapt/issues/240
addison: will talk a bit later
<addison> #32
<gb> [30]Action 32 Approve the character markup PR (on
fantasai) due 2023-08-17
[30] https://github.com/w3c/i18n-actions/issues/32
addison: close this
r12a: better to keep?
<gb> Found actions in w3c/i18n-actions: #44, #43, #42, #41,
#39, #35, #33, #32, #18, #16, #15, #13, #12, #11, #10, #9, #8,
#7, #5, #4
<addison> #18
<gb> [31]Action 18 Have informal explanation sessions about
counter style translations with csswg members (on frivoal,
fantasai)
[31] https://github.com/w3c/i18n-actions/issues/18
<addison> #16
<gb> [32]Action 16 Keep track of line-breaking in Korean for
i18n-discuss#11 (on aphillips)
[32] https://github.com/w3c/i18n-actions/issues/16
<addison> #15
<gb> [33]Action 15 Get character styling into w3c stylesheet
(on aphillips)
[33] https://github.com/w3c/i18n-actions/issues/15
<addison> #13
<gb> [34]Action 13 Make sure generics are comfortable to read
in the content language (on frivoal)
[34] https://github.com/w3c/i18n-actions/issues/13
addison: keep #15 for discussion
r12a: styling had been done?
<addison> close #15
<gb> Closed [35]action #15
[35] https://github.com/w3c/i18n-actions/issues/15
addison: fantassai took image thing, so could close this one
<addison> #12
<gb> [36]Action 12 Upgrade/edit the explainer to address issues
raised by google (on aphillips)
[36] https://github.com/w3c/i18n-actions/issues/12
addison: can close #13, CSS one has closed?
<addison> #11
<gb> [37]Action 11 Triage all css properties to determine which
are logical, physical, or na by default (on frivoal)
[37] https://github.com/w3c/i18n-actions/issues/11
addison: worked for explainer, for #12
<addison> #10
<gb> [38]Action 10 With florian triage richard's article into a
list of potential generics (on frivoal, fantasai)
[38] https://github.com/w3c/i18n-actions/issues/10
<addison> #9
<gb> [39]Action 9 Follow up with ecma-402 on next steps and
start tc39 discussion (on aphillips)
[39] https://github.com/w3c/i18n-actions/issues/9
<addison> #8
<gb> [40]Action 8 Create pr against canvas formatted text (on
aphillips)
[40] https://github.com/w3c/i18n-actions/issues/8
<addison> #7
<gb> [41]Action 7 Remind shepherds to tend to their awaiting
comment resolutions (Evergreen) (on aphillips, xfq, himorin,
r12a, bert-github)
[41] https://github.com/w3c/i18n-actions/issues/7
<addison> #5
<gb> [42]Action 5 Check into how to list questions at the top
of a digest and/or improve lang enablement communications (on
r12a)
[42] https://github.com/w3c/i18n-actions/issues/5
<addison> #4
<gb> [43]Action 4 Work with respec and bikeshed to provide the
character markup template as easy-to-use markup (on r12a)
[43] https://github.com/w3c/i18n-actions/issues/4
Info Share
<gb> [44]Issue 240 Could we build symbolic annotations with
existing Web standards? (by DuncanMacWeb) [i18n-tracker]
[44] https://github.com/w3c/adapt/issues/240
<gb> [45]Pull Request 117 Add additional definitions of
'string' (w3c/i18n-actions#41) (by aphillips)
[45] https://github.com/w3c/bp-i18n-specdev/issues/117
addison: had long chat with PLH about process
… chatted about WCAG, but found also similar on several other
specs
… PR filed against Guide, following discussion
… pushing on AC reps and/or several big companies for
participation
… on joining to activities
RADAR Review
<addison> [46]https://github.com/w3c/i18n-request/projects/1
[46] https://github.com/w3c/i18n-request/projects/1
addison: two new requests
xfq: I can take DAPT
addison: vc-jose-cose has internationalization consideration
section
bert: interested but quick review is required
… in october is desired
addison: assigned Bert, with one month
RADAR Review
<addison> [47]https://github.com/w3c/i18n-activity/issues
[47] https://github.com/w3c/i18n-activity/issues
addison: couple of incoming issues
addison: adequacy of base direction, and punycode reference
<addison> [48]w3c/i18n-activity#1758
[48] https://github.com/w3c/i18n-activity/issues/1758
<gb> [49]Issue 1758 Reference for punycode-encoding of IDN (by
w3cbot) [pending] [tracker] [needs-attention] [s:rdf-concepts]
[49] https://github.com/w3c/i18n-activity/issues/1758
<addison> [50]w3c/rdf-concepts#63
[50] https://github.com/w3c/rdf-concepts/issues/63
addison: RDF colleagues are happy to accept comment on issue
TPAC Fallout
addison: anything to bring up here?
[51]w3c/adapt#240
[51] https://github.com/w3c/adapt/issues/240
<gb> [52]Issue 240 Could we build symbolic annotations with
existing Web standards? (by DuncanMacWeb) [i18n-tracker]
[52] https://github.com/w3c/adapt/issues/240
addison: asking about existing standards
… could be related to COGA etc.
r12a: add comment on this
addison: we are interesting if they would want to go to Unicode
… characters something like emoji
r12a: a bit difficult to me, looking at Unicode block it is
quite well tighten to image for emoji
[situation around bliss symbols]
r12a: writing some to Unicode could be great
ACTION: addison to connect unicode sah to the adapt 240 thread
<gb> Created [53]action #45
[53] https://github.com/w3c/i18n-actions/issues/45
<gb> [54]Issue 240 Could we build symbolic annotations with
existing Web standards? (by DuncanMacWeb) [i18n-tracker]
[54] https://github.com/w3c/adapt/issues/240
<gb> [55]Pull Request 117 Add additional definitions of
'string' (w3c/i18n-actions#41) (by aphillips)
[55] https://github.com/w3c/bp-i18n-specdev/issues/117
WCAG 2.2 PR# 3347: another look
<addison> [56]w3c/wcag#3347
[56] https://github.com/w3c/wcag/issues/3347
<gb> [57]Pull Request 3347 Text-spacing note for I18n (by
alastc)
[57] https://github.com/w3c/wcag/issues/3347
addison: during TPAC, edited this suggestion
… I don't care how long it is compaired to the SC text
xfq: I'm kind of afraid that if we hide this text into
understanding document, this will be missed
addison: asking to move exception paragraph to first, and
remove the last?
addison: we want second paragraph for our purpose
r12a: yes
addison: so, could agree to remove some text, but keep second
sentence
<addison> <p>Exception: Human languages and scripts that do not
make use of one or more of these text style properties in
written text can conform using only the properties that exist
for that combination of language and script.</p>
<xfq> [58]https://www.w3.org/TR/WCAG21/#text-spacing
[58] https://www.w3.org/TR/WCAG21/#text-spacing
r12a: suppose they would keep? but exception should be there
addison: our sentence is to clarify explicit who to apply
xfq: last sentence says effectively the same as exception
definition of string ([59]w3c/bp-i18n-specdev#117)
[59] https://github.com/w3c/bp-i18n-specdev/issues/117
<gb> [60]Pull Request 117 Add additional definitions of
'string' (w3c/i18n-actions#41) (by aphillips)
[60] https://github.com/w3c/bp-i18n-specdev/issues/117
addison: action item to update our string desfinition
… current text only deals with web world
… and RDF-star is coming with XML world
… trying to incoorporate them into spec-dev
<addison> [61]https://
deploy-preview-117--bp-i18n-specdev.netlify.app/#char_string
[61]
https://deploy-preview-117--bp-i18n-specdev.netlify.app/#char_string
addison: see above PR preview
… provide definition of string, and provide useful links for
USVString/DOMString
xfq: no definition in glossary yet
addison: is good direction, but need some more text
… need to find definition of web platform
… html and JavaScript API
… not sure RDF colleagues are willing to be a part of web
platform
xfq: mentioned about XML based one, but SVG is based on XML but
in the Web
… or implemented in the browsers
<r12a> Wikipedia says: The Web platform includes
technologies—computer languages and APIs—that were originally
created in relation to the publication of Web pages. This
includes HTML,[4] CSS, SVG, MathML,[5] WAI-ARIA, ECMAScript,
WebGL, Web Storage, Indexed Database API, Web Components,
WebAssembly, WebGPU, Web Workers, WebSocket, Geolocation API,
Server-Sent Events, DOM Events, Media Fragments,
XMLHttpRequest, Cross-Origin Resource Sharing, File
<r12a> API, RDFa, WOFF, HTTP, TLS 1.2, and IRI.
addison: TAG document did not define the Web Platform
[62]https://www.w3.org/TR/ethical-web-principles/#intro
[62] https://www.w3.org/TR/ethical-web-principles/#intro
The web is made up of a number of technologies and technical
standards. HTML, CSS and JavaScript are often thought of as the
web's core set of technologies but there are a raft of other
technologies, standards, languages and APIs that come together
to form the "web platform."
r12a: DOM based technology?
addison: will take these to write some text here
… we could go to TAG and say you should say something here
<addison> [63]https://github.com/w3c/i18n-discuss/blob/
gh-pages/explainers/string-meta-explainer-updated.md
[63]
https://github.com/w3c/i18n-discuss/blob/gh-pages/explainers/string-meta-explainer-updated.md
addison: xfq worked for explainer above
<addison> [64]https://github.com/w3c/i18n-discuss/blob/
gh-pages/explainers/
string-meta-explainer-updated.md#is-there-a-better-approach
[64]
https://github.com/w3c/i18n-discuss/blob/gh-pages/explainers/string-meta-explainer-updated.md#is-there-a-better-approach
addison: worth giving time on this or not?
ACTION: xfq, r12a, and others to read the string-meta explainer
and consider the new approach addison proposed
<gb> Cannot create action. Validation failed. Maybe one of the
names is not a valid user for w3c/i18n-actions?
ACTION: xfq, r12a: read the string-meta explainer and consider
the new approach addison proposes
<gb> Created [65]action #46
[65] https://github.com/w3c/i18n-actions/issues/46
AOB?
bert: regret for next week
Summary of action items
1. [66]addison to connect unicode sah to the adapt 240 thread
2. [67]xfq, r12a, and others to read the string-meta explainer
and consider the new approach addison proposed
3. [68]xfq, r12a: read the string-meta explainer and consider
the new approach addison proposes
Received on Friday, 22 September 2023 04:00:09 UTC