- From: r12a <ishida@w3.org>
- Date: Thu, 14 Nov 2019 16:18:15 +0000
- To: www International <www-international@w3.org>
https://www.w3.org/2019/11/14-i18n-minutes.html
text version follows:
- DRAFT -
Internationalization Working Group Teleconference
14 Nov 2019
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2019Nov/0015.html
Attendees
Present
Bert, Fuqiao, addison, Atsushi, r12a, JcK
Regrets
Chair
Addison Phillips
Scribe
addison
Contents
* [3]Topics
1. [4]Agenda and Minutes
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR and Active Work Review
5. [8]horizontal review labels again
6. [9]clearing cruft from our tracker
7. [10]East Asian Width
8. [11]clearing cruft from our tracker
9. [12]AOB?
* [13]Summary of Action Items
* [14]Summary of Resolutions
__________________________________________________________
trackbot, prepare teleconference
<scribe> Agenda:
<agendabot> clear agenda
<scribe> ScribeNick: addison
Agenda and Minutes
Action Items
[15]https://www.w3.org/International/track/actions/open
[15] https://www.w3.org/International/track/actions/open
action-832?
<trackbot> action-832 -- Addison Phillips to Check with Unicode
ESC and UTC on CSS 337: can emoji be EA Width of Ambiguous --
due 2019-09-26 -- OPEN
<trackbot>
[16]https://www.w3.org/International/track/actions/832
[16] https://www.w3.org/International/track/actions/832
action-840?
<trackbot> action-840 -- Atsushi Shimono to Find out about
potential schedule clash with ttwg and report back if we need
to consider a time change -- due 2019-10-31 -- OPEN
<trackbot>
[17]https://www.w3.org/International/track/actions/840
[17] https://www.w3.org/International/track/actions/840
close action-840
<trackbot> Closed action-840.
action-846?
<trackbot> action-846 -- Addison Phillips to File 2 issues
against whatwg infra about case-sensitive and update css
comment -- due 2019-11-14 -- OPEN
<trackbot>
[18]https://www.w3.org/International/track/actions/846
[18] https://www.w3.org/International/track/actions/846
close action-846
<trackbot> Closed action-846.
Info Share
RADAR and Active Work Review
[19]https://github.com/w3c/i18n-activity/projects/1
[19] https://github.com/w3c/i18n-activity/projects/1
bert: still reviewing intersection observer
horizontal review labels again
richard: talked to a number of people, got a lukewarm response
... want to call first part of label "privacy" vs. "ping" for
one group. nothing to do with us
... still an issue with i18n-comment label
... not sure i18n-tracking a big issue
<r12a>
richard: suggested in my email..
<r12a> *i18n-tracker*
<r12a> (was formerly i18n-tracking)
<r12a> The i18n WG may add this label to indicate that they are
following a discussion. Other WGs can also add the label to any
issue to automatically bring the discussion to the attention of
the i18n WG. Issues with this label don't need to be resolved
to the satisfaction of the i18n WG before a transition.
<r12a> *i18n-needs-response*
<r12a> (was formerly i18n-comment)
<r12a> The i18n WG has raised, or is following this issue, and
expects it to be resolved to their satisfaction before a
transition. This label is added/applied only by the i18n WG,
and should only be removed by them. It may replace an
i18n-tracker label.
<r12a> *i18n-satisfied*
<r12a> (new)
<r12a> Applied by the i18n WG only. Replaces
i18n-needs-response when the i18n WG is satisfied with the
resolution.
<r12a> ]]
<r12a> i18n-needs-response -> i18n-needs-resolution
richard: want to say instead of i18n-needs-response
... choosing names for two labels we have
... and then introducing a new label 'i18n-satisified'
... so when we're satisfied we would change the label from
i18n-needs-response to i18n-satisfied
... makes clear to others
... such as in CR transition
... if any tags needs-response not happy
sounds good to me
<JcK> Seems as reasonable as we are going to get, so no
objection.
clearing cruft from our tracker
East Asian Width
(addison introduces)
richard: wrote something on that thread, less EAW than line
reconstitution
... think we're overthinking
... I think most of the time, if you want SE Asian script
languages to combine properly
... you don't need to do anything because spaces in those
language
... people don't complain because they break on spaces
... emoji not really an issue, appear mostly in text with words
with spaces
addison: why do you assert that?
richard: if emoji in source text, then most of the time not
writing massive strings
... there'll be a space nearby
... other thing is that don't expect long strings of emoji in
source text
... in source ZWJ sequences look short
... not counting chars
... only place it's a problem with like chinese and japanese
... there need to decide where to break the text
clearing cruft from our tracker
<r12a>
[20]https://lists.w3.org/Archives/Member/member-i18n-core/2019N
ov/0019.html
[20]
https://lists.w3.org/Archives/Member/member-i18n-core/2019Nov/0019.html
<r12a>
[21]https://w3c.github.io/i18n-activity/reviews/#vehicle-inform
ation-access
[21]
https://w3c.github.io/i18n-activity/reviews/#vehicle-information-access
RESOLUTION: close vehiclde-information-access issues and mark
with 'recycle'
close the first dpub one since not really i18n
RESOLUTION: close three dpub issues as stale
RESOLUTION: close all linked-data-patch-format issues
RESOLUTION: close appmanifest issue
RESOLUTION: close tracking-compliance issue as stale
AOB?
Summary of Action Items
Summary of Resolutions
1. [22]close vehiclde-information-access issues and mark with
'recycle'
2. [23]close three dpub issues as stale
3. [24]close all linked-data-patch-format issues
4. [25]close appmanifest issue
5. [26]close tracking-compliance issue as stale
[End of minutes]
Received on Thursday, 14 November 2019 16:18:19 UTC