- From: <ishida@w3.org>
- Date: Wed, 11 May 2016 13:36:45 +0100
- To: www International <www-international@w3.org>
https://www.w3.org/2016/05/05-i18n-minutes.html
text version follows:
Internationalization Working Group Teleconference
05 May 2016
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2016May/0005.html
See also: [3]IRC log
[3] http://www.w3.org/2016/05/05-i18n-irc
Attendees
Present
Addison, Richard, David, JcK
Regrets
Felix, Steve
Chair
Addison Phillips
Scribe
Addison Phillips
Contents
* [4]Topics
1. [5]Agenda
2. [6]Action Items
3. [7]Info Share
4. [8]RADAR and Active Work Review
5. [9]topic index findings and next steps
6. [10]Definition of whitespace
7. [11]HTML issues
8. [12]review comments on web annotation drafts
9. [13]AOB?
* [14]Summary of Action Items
* [15]Summary of Resolutions
__________________________________________________________
Action Items
[16]https://www.w3.org/International/track/actions/open
[16] https://www.w3.org/International/track/actions/open
action-511?
<trackbot> action-511 -- Richard Ishida to Check if discource
for wicg can add notifier for an i18n label -- due 2016-05-05
-- OPEN
<trackbot>
[17]http://www.w3.org/International/track/actions/511
[17] http://www.w3.org/International/track/actions/511
sent email, no reply yet
action-512?
<trackbot> action-512 -- Richard Ishida to Send
www-international an email about removing topic index and
prepare new home page and other page mods as needed to support
that -- due 2016-05-05 -- OPEN
<trackbot>
[18]http://www.w3.org/International/track/actions/512
[18] http://www.w3.org/International/track/actions/512
close action-512
<trackbot> Closed action-512.
action-513?
<trackbot> action-513 -- Richard Ishida to Raise an issue
against html about default q-styling -- due 2016-05-05 -- OPEN
<trackbot>
[19]http://www.w3.org/International/track/actions/513
[19] http://www.w3.org/International/track/actions/513
close action-513
<trackbot> Closed action-513.
<r12a> [20]https://github.com/w3c/i18n-activity/issues/124
[20] https://github.com/w3c/i18n-activity/issues/124
Info Share
richard: new version of unicode-xml with disclaimer published
RADAR and Active Work Review
[21]http://w3c.github.io/i18n-activity/radar/
[21] http://w3c.github.io/i18n-activity/radar/
richard: one issue raised
[22]http://w3c.github.io/i18n-activity/projects/
[22] http://w3c.github.io/i18n-activity/projects/
<r12a>
[23]https://github.com/w3c/browser-payment-api/issues/53#issuec
omment-215709951
[23]
https://github.com/w3c/browser-payment-api/issues/53#issuecomment-215709951
richard: info share
... have found a way to put i18n tags on other peoples repos
... and make it so that when the label is applied to an issue
we get notified
... and also when closed
<scribe> ... done for html wg
<scribe> ... done for some other wg
UNKNOWN_SPEAKER: might be payments
<scribe> ... in process of doing for annotation people
UNKNOWN_SPEAKER: negotiated with ivan an hour or so ago
... have a way for all groups going forward
requirements dev
richard: some talk with swaran
... trying to get more content/community involvement
... should watch summary of issues
... quite a lot of html issues now
... a lot from chaals
... also looked through issue list
<r12a> [24]http://w3c.github.io/i18n-activity/reviews/
[24] http://w3c.github.io/i18n-activity/reviews/
richard: vote on publishing ruby markup?
addison: any comments?
richard: a couple of very small things, easily fixed
... none from fantasai and koji
... ping before publising?
addison: all in favor of publishing "ruby markup" (link below)?
<r12a>
[25]http://w3c.github.io/i18n-drafts/articles/ruby/markup.en.ht
ml
[25] http://w3c.github.io/i18n-drafts/articles/ruby/markup.en.html
<David> +1
+1
<r12a> +1
<JcK> +1
addison: so approved
<scribe> ACTION: richard: publish ruby markup article after
pinging fantasai and koji [recorded in
[26]http://www.w3.org/2016/05/05-i18n-minutes.html#action01]
[26] http://www.w3.org/2016/05/05-i18n-minutes.html#action01]
<trackbot> Created ACTION-514 - Publish ruby markup article
after pinging fantasai and koji [on Richard Ishida - due
2016-05-12].
topic index findings and next steps
richard: spent time trying diff strategies for keeping by more
efficient
... like putting keywords in meta
... but search is much more useful
... finds stuff I can't keyword
... and stays up to date
... propose to replace with a big search box
addison: just searches International/
richard: yes
<scribe> ACTION: richard: replace topic index with a giant
search box [recorded in
[27]http://www.w3.org/2016/05/05-i18n-minutes.html#action02]
[27] http://www.w3.org/2016/05/05-i18n-minutes.html#action02]
<trackbot> Created ACTION-515 - Replace topic index with a
giant search box [on Richard Ishida - due 2016-05-12].
Definition of whitespace
richard: sent note to steven p asking what he intended to do
with it
[28]https://lists.w3.org/Archives/Member/member-i18n-core/2016A
pr/0027.html
[28]
https://lists.w3.org/Archives/Member/member-i18n-core/2016Apr/0027.html
talk about this next week
HTML issues
addison: triage wontfixed bugzilla items in case any action is
needed?
<scribe> ACTION: addison: triage wontfixed bugzilla items in
case any action is needed? [recorded in
[29]http://www.w3.org/2016/05/05-i18n-minutes.html#action03]
[29] http://www.w3.org/2016/05/05-i18n-minutes.html#action03]
<trackbot> Created ACTION-516 - Triage wontfixed bugzilla items
in case any action is needed? [on Addison Phillips - due
2016-05-12].
<scribe> ACTION: addison: remind working group to review HTML
items in [30]http://w3c.github.io/i18n-activity/reviews/ for
next call [recorded in
[31]http://www.w3.org/2016/05/05-i18n-minutes.html#action04]
[30] http://w3c.github.io/i18n-activity/reviews/
[31] http://www.w3.org/2016/05/05-i18n-minutes.html#action04]
<trackbot> Created ACTION-517 - Remind working group to review
html items in [32]http://w3c.github.io/i18n-activity/reviews/
for next call [on Addison Phillips - due 2016-05-12].
[32] http://w3c.github.io/i18n-activity/reviews/
<r12a> [33]http://w3c.github.io/i18n-activity/reviews/#html
[33] http://w3c.github.io/i18n-activity/reviews/#html
review comments on web annotation drafts
<r12a>
[34]https://lists.w3.org/Archives/Member/member-i18n-core/2016A
pr/0045.html
[34]
https://lists.w3.org/Archives/Member/member-i18n-core/2016Apr/0045.html
richard: first one is about reference to IRI
... they refer to URL or IRI
... what should be calling these? URL?
addison: and which spec
richard: no harm done?
investigate whether they spec needs to dirty its hands with
serializing to the wire
am-2) Reference to BCP47 See
[35]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#bo
dies-and-targets
<[36]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#b
odies-and-targets> "The Body or Target SHOULD have exactly 1
language associated with it, but MAY have 0 or more. The value
of the property SHOULD be a language code following the
[rfc5646
<[37]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#b
ib-rfc5646>] specifiction.“ Shouldn’t this [CUT]
[35]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#bodies-and-targets
[36]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#bodies-and-targets
[37]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#bib-rfc5646
yes, BCP47
potentially raise issue about 0 or more
0 or 1 unless they mean to have a language priority list
am-3) Definition of character See
[38]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#em
bedded-textual-body
<[39]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#e
mbedded-textual-body> "The character sequence of the content of
the Textual Body.“: this text and the whole document is missing
a definition of a character.
[38]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#embedded-textual-body
[39]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#embedded-textual-body
richard: word character used a lot
... charmod says to define
... one their issues
define character probably as code point
am-4) Counting of characters See
[40]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#fr
agment-selector
<[41]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#f
ragment-selector> A question is whether Is it possible for the
plain text selector to specify the normalization form, to
understand what is being counted. One resolution may be to say
in reference to comment 3) that a character is always a unicode
character in NFC. The same comment applies t[CUT]
[40]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#fragment-selector
[41]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#fragment-selector
want to count the code points in the *not* normalized file
probably related to our work with find text
want grapheme boundaries (for some def of grapheme??)
richard: want normalization for some other operations possibly
addison: for matching and such
am-5) Text quote selectors and mixed scripts See
[42]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#te
xt-quote-selector
<[43]https://www.w3.org/TR/2016/WD-annotation-model-20160331/#t
ext-quote-selector> Is there a need to specific what happens
with mixed scripts, or at least require testing of text quote
with mixed scripts?
[42]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#text-quote-selector
[43]
https://www.w3.org/TR/2016/WD-annotation-model-20160331/#text-quote-selector
not sure what this is
ap-1) General comment on annotation retrieval
[44]https://www.w3.org/TR/2016/WD-annotation-protocol-20160331/
#annotation-retrieval The section says „If more than one
representation of the Annotation is available, then the server
SHOULD support content negotiation." Creators of annotations
are missing guidance whether annotations in different languages
should be provided via content negotiation or whether it is
recommended to have variation in language speci[CUT]
[44]
https://www.w3.org/TR/2016/WD-annotation-protocol-20160331/#annotation-retrieval
needs further study
richard: one other think about normalization
... when they say it, they mean stripping html and other such
stuff
... we need to be careful to be explicit about what we mean
... when we use the "normalization" word
<scribe> ACTION: felix: submit approved issues to
web-annotations after speaking to richard about the discussion
[recorded in
[45]http://www.w3.org/2016/05/05-i18n-minutes.html#action05]
[45] http://www.w3.org/2016/05/05-i18n-minutes.html#action05]
<trackbot> Created ACTION-518 - Submit approved issues to
web-annotations after speaking to richard about the discussion
[on Felix Sasaki - due 2016-05-12].
AOB?
Summary of Action Items
[NEW] ACTION: addison: remind working group to review HTML
items in [46]http://w3c.github.io/i18n-activity/reviews/ for
next call [recorded in
[47]http://www.w3.org/2016/05/05-i18n-minutes.html#action04]
[NEW] ACTION: addison: triage wontfixed bugzilla items in case
any action is needed? [recorded in
[48]http://www.w3.org/2016/05/05-i18n-minutes.html#action03]
[NEW] ACTION: felix: submit approved issues to web-annotations
after speaking to richard about the discussion [recorded in
[49]http://www.w3.org/2016/05/05-i18n-minutes.html#action05]
[NEW] ACTION: richard: publish ruby markup article after
pinging fantasai and koji [recorded in
[50]http://www.w3.org/2016/05/05-i18n-minutes.html#action01]
[NEW] ACTION: richard: replace topic index with a giant search
box [recorded in
[51]http://www.w3.org/2016/05/05-i18n-minutes.html#action02]
[46] http://w3c.github.io/i18n-activity/reviews/
[47] http://www.w3.org/2016/05/05-i18n-minutes.html#action04
[48] http://www.w3.org/2016/05/05-i18n-minutes.html#action03
[49] http://www.w3.org/2016/05/05-i18n-minutes.html#action05
[50] http://www.w3.org/2016/05/05-i18n-minutes.html#action01
[51] http://www.w3.org/2016/05/05-i18n-minutes.html#action02
Summary of Resolutions
[End of minutes]
Received on Wednesday, 11 May 2016 12:38:54 UTC