- From: r12a <ishida@w3.org>
- Date: Fri, 21 May 2021 10:31:40 +0100
- To: www-international@w3.org
- Message-ID: <c4994bdd-786f-b3dd-f164-2a1b966c3ba2@w3.org>
https://www.w3.org/2021/05/20-i18n-minutes
– DRAFT –
Internationalization Working Group Teleconference
20 May 2021
[2]Agenda. [3]IRC log.
[2] https://lists.w3.org/Archives/Member/member-i18n-core/2021May/0009.html
[3] https://www.w3.org/2021/05/20-i18n-irc
Attendees
Present
Addison, atsushi, Bert, fsasaki, Fuqiao, JcK, r12a
Regrets
Felix
Chair
Addison Phillips
Scribe
atsushi
Contents
1. [4]Agenda Review
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR Review
5. [8]CSS column layout
6. [9]personalization semantics issue
7. [10]Charmod Edits, Publish to TR?
8. [11]Web payments status
9. [12]open tracker issues about personalization-semantics
10. [13]personalization semantics issue
11. [14]AOB?
12. [15]Summary of action items
Meeting minutes
<addison> trackbot, prepare teleconference
Agenda Review
Action Items
<addison> [16]https://www.w3.org/International/track/actions/
open
[16] https://www.w3.org/International/track/actions/open
<addison> action-1022?
<trackbot> Error querying: could not connect to Tracker. Please
mail <sysreq@w3.org> with details about what happened.
<addison> [17]https://www.w3.org/International/track/actions/
1022
[17] https://www.w3.org/International/track/actions/1022
<addison> close action-1022
<trackbot> Closed action-1022.
<addison> [18]https://www.w3.org/International/track/actions/
1024
[18] https://www.w3.org/International/track/actions/1024
<addison> [19]https://www.w3.org/International/track/actions/
1026
[19] https://www.w3.org/International/track/actions/1026
<addison> close action-1026
<trackbot> Closed action-1026.
Info Share
<r12a> [20]https://github.com/w3c/i18n-activity/projects/3
[20] https://github.com/w3c/i18n-activity/projects/3
richard: link above
… as told before, gap-analysis project is here
… consolidated items on this project
… exactly 100 issues listed, 63 need to be investigated
… once work done, moving to another column
… few additional idea on how issue is important, what relates
addison: documentation on what to do?
richard: you can open issue, following template
… template is written in pretty detail
addison: open to large community?
richard: need to be performed by TF participants
… if ones already in these groups, it's fantastic if they can
take roles
richard: working on my application in personal site
<r12a> [21]https://r12a.github.io/pickers/armn/
[21] https://r12a.github.io/pickers/armn/
richard: lot of little tools here
… and making language tools into one bigger integrated tool
… left hand side, narrow box you can select type of input, and
you can type characters/sentence with these
richard: you can share characters into other applications, like
character use cases, or from uniview
RADAR Review
<addison> [22]https://github.com/w3c/i18n-request/projects/1
[22] https://github.com/w3c/i18n-request/projects/1
addison: CSS multicolumn layout module level 1
CSS column layout
<xfq> [23]https://github.com/w3c/i18n-request/issues/153
[23] https://github.com/w3c/i18n-request/issues/153
xfq: in the issue, I've commented
<r12a> [24]https://www.w3.org/TR/css-multicol-1/
[24] https://www.w3.org/TR/css-multicol-1/
xfq: multicolumn layout can be adopted into writing mode
richard: implementers could be fully aware on vertical writing
with this
… ones like short sentence could need some care
… the biggest issue for me is terminology
… it's been used for long time, one sentence in the spec
mentions line with different direction
addison: to be action?
richard: whether asking to them for this?
xfq: yes, inline base direction for different writing mode
could be mentioned, and it could be helpful for implementers
richard: agree. as editorial request
<r12a> [25]https://r12a.github.io/scripts/
mongolian/#generallayout
[25] https://r12a.github.io/scripts/mongolian/#generallayout
richard: have some example for mongolian, need some more from
other language
atsushi: will work on for japanese
Action: richard: file issue on css multi-col to clarify columns
in vertical
<trackbot> Created ACTION-1027 - File issue on css multi-col to
clarify columns in vertical [on Richard Ishida - due
2021-05-27].
personalization semantics issue
<xfq> [26]https://github.com/w3c/personalization-semantics/
issues/144
[26] https://github.com/w3c/personalization-semantics/issues/144
xfq: team contact said to me on the issue above
… asked whether we are satisfied with this or not, for expected
publicaiton of spec in near future
richard: addison reopened the issue, what was the reason?
xfq: still have some open issues
… this issue is for metadata, rely on lang and dir
addison: question is that symbology follows the same language
and direction
richard: the first comment addison made could be clearer about
the problem we are concerned about
addison: don't understand what there reply states...
… will comment with questions to this issue
Action: addison: update personalization-semantics issue with
clarifying statements and questions
<trackbot> Created ACTION-1028 - Update
personalization-semantics issue with clarifying statements and
questions [on Addison Phillips - due 2021-05-27].
Charmod Edits, Publish to TR?
<addison> [27]http://aphillips.github.io/charmod-norm/
[27] http://aphillips.github.io/charmod-norm/
<addison> [28]https://github.com/w3c/charmod-norm/pull/215
[28] https://github.com/w3c/charmod-norm/pull/215
addison: based on my action items, PR opened here
<addison> [29]https://pr-preview.s3.amazonaws.com/w3c/
charmod-norm/215/21284b0...aphillips:5ea3dc9.html
[29] https://pr-preview.s3.amazonaws.com/w3c/charmod-norm/215/21284b0...aphillips:5ea3dc9.html
addison: this is to address, moving normalization before
casefold, and move optional to the last
… one is 2.4.1 and other is 3.2.2.4
addison: question is ready to go, and ready to be published
richard: this casefolding is working, if normalization taken?
… it should be clear, optional step 3, re-normalize to NFC,
have to be done again
addison: recommending NF as output
richard: like IPA, better to be in NFC than NFD
richard: making two points, step 3 before unicode normalization
… steps [..lost..]
bert: there is two case folding in the last sentence of the
first para in 2.4.1
addison: in result, couples of edits to do
richard: example 26 is ok?
Web payments status
<addison> [30]https://lists.w3.org/Archives/Member/
member-i18n-core/2021May/0010.html
[30] https://lists.w3.org/Archives/Member/member-i18n-core/2021May/0010.html
<addison> [31]https://github.com/w3c/payment-request/issues/948
[31] https://github.com/w3c/payment-request/issues/948
addison: web payments issues, two of not-filed review issues
are merged into one another issue
<addison> 1357, 1359 close
richard: haven't checked in detail, two - 1359 and 1357 should
be closed
addison: could add one tracker for the filed issue
open tracker issues about personalization-semantics
xfq: we can see some our open tracker issues on personalization
semantics
<xfq> [32]https://github.com/w3c/i18n-activity/
issues?q=is%3Aopen+is%3Aissue+label%3As%3Apersonalization-seman
tics-content
[32] https://github.com/w3c/i18n-activity/issues?q=is:open+is:issue+label:s:personalization-semantics-content
richard: we need to close trackers which could be closed
addison: check and review them, and take actions (to close) if
any
Action: addison: review payment-request issues and mark for
close as needed
<trackbot> Created ACTION-1029 - Review payment-request issues
and mark for close as needed [on Addison Phillips - due
2021-05-27].
richard: looking through html, will put a list together for
next week
personalization semantics issue
<xfq> [33]https://github.com/w3c/i18n-activity/issues/878
[33] https://github.com/w3c/i18n-activity/issues/878
xfq: have reviewed not all of these yet
<xfq> [34]https://github.com/w3c/personalization-semantics/
issues/141
[34] https://github.com/w3c/personalization-semantics/issues/141
xfq: tracker 878 is related to our previous ones for metadata
richard: we may need to point some reference
… still question, in arabic books, use their symbol or numerics
addison: its something like signed language, could be turned
into some characters
<addison> [35]https://w3c.github.io/personalization-semantics/
content/
[35] https://w3c.github.io/personalization-semantics/content/
[reading content module]
<addison> [36]https://w3c.github.io/personalization-semantics/
content/#symbol-example
[36] https://w3c.github.io/personalization-semantics/content/#symbol-example
richard: see example 12, as a sentence
addison: still replaced based on each word
richard: i could clear some time tomorrow to look in more
detail
AOB?
Summary of action items
1. [37]richard: file issue on css multi-col to clarify columns
in vertical
2. [38]addison: update personalization-semantics issue with
clarifying statements and questions
3. [39]addison: review payment-request issues and mark for
close as needed
Received on Friday, 21 May 2021 09:31:48 UTC