See also: IRC log
https://www.w3.org/International/track/actions/open
action-504?
<trackbot> action-504 -- Addison Phillips to Forward remaining action 502 issues and ping dennis, leandro, and leslie about theirs -- due 2016-04-07 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/504
forwarded mine, did not ping the others
action-514?
<trackbot> action-514 -- Richard Ishida to Publish ruby markup article after pinging fantasai and koji -- due 2016-05-12 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/514
close action-514
<trackbot> Closed action-514.
<r12a> https://www.w3.org/blog/International/2016/06/13/new-article-ruby-markup/
action-516?
<trackbot> action-516 -- Addison Phillips to Triage wontfixed bugzilla items in case any action is needed? -- due 2016-05-12 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/516
https://lists.w3.org/Archives/Public/public-i18n-core/2016AprJun/0078.html
close action-516
<trackbot> Closed action-516.
richard: added a new status label
to tracker
... called "deferred"
... will make it appear in our list
... idea is that, for example, <q> was put off to
5.2
... dont' want to close but don't want to keep reviewing it
steven: updating instructions?
richard: yes, doing anyway
... started using our issues list
... reviewed in our lists
... copy the info into their github issues list
... and put a link back to the original
... but we've started now removing the initial comment
... certain circumstances were we've discussed before it goes
to the other group
steven: keep discussiong but remove initial comment?
richard: yes
... news about FindText
... asked Ivan about status
... work postponed for a period
... so don't worry about it
<r12a> https://www.w3.org/2016/09/TPAC/
addison: if they published as note, ask for big red box on it?
richard: please register for TPAC as soon as possible
zakimn, take up agendum 4
http://w3c.github.io/i18n-activity/radar/
<Steve_Atkin> https://github.com/w3c/html/issues/485
<r12a> https://w3c.github.io/uievents/#events-keyboardevents
<r12a> https://www.w3.org/International/reviews/1002-dom3-events/
<r12a> https://www.w3.org/International/reviews/0806-xhtml-access/
http://w3c.github.io/i18n-activity/projects/
richard: publication of ruby
markup article
... make more visible where implementation is needed
... increase implementaiton adoption
... start writing bugs against implementations
addison: have tests, right?
richard: we do
<r12a> https://www.w3.org/International/tests/repo/results/ruby-html
http://w3c.github.io/bp-i18n-specdev
https://github.com/w3c/bp-i18n-specdev/issues
steven: do we think they'll understand code points and code units and understand those things?
richard: "more" sections are
supposed to explain
... but in some cases like this might be a little bare
... for the sake of speed, just copied recommendations direct
form charmod
steven: logical vs. visual
order
... is that applicable to non-unicode encodings
richard: guidance to spec
writers
... don't want new specs in visual order
steven: my concern is some of our
legacy encoding heritage
... okay with that
... base direction and assuming dir from lang
... 7 and 8?
... should not require content author to use control characters
to get direction they want, right?
richard: could be a script or whatever, not just content author
steven: can indicate as metadata,
not use controls to get effect wanted
... want to change to be explicit "do not use lang to get
dir"
richard: may be certain
situations, if not information is available, as a
fallback
... doesn't always hold
... kind of left it
steven: last thing was #5
... default text processing language
... for resource as a whole *and* any inheritance models
richard: inheritance should be
the case at resource and block level
... had it there so spec authors would see it in context
... will have another look
steven: rest are commented on
(Steven exuent)
<r12a> http://r12a.github.io/apps/conversion/
<r12a> https://www.w3.org/TR/charmod/#C042
\u{1234}
\U
richard: would like to take a decision on publishing an update when we know what that involves
<r12a> https://www.w3.org/International/docs/encoding/encoding-cr-doc2
richard: first step is to publish
an updated CR
... some subsntative made, but mostly settling
move to publish a new CR of Encoding
+1
<r12a> +1
<JcK> +1 (with qualification for list objections)
<scribe> ACTION:addison: call for objections to publishing Encoding updated CR [recorded in http://www.w3.org/2016/06/16-i18n-minutes.html#action01]
richard: want to be more
proactive about closing issues in our lists
... marked our web-annotations ones
... ask www-international and then close if no objections
https://github.com/w3c/i18n-activity/labels/close%3F
<r12a> http://w3c.github.io/i18n-activity/reviews/
do by spec