See also: IRC log
https://www.w3.org/International/track/actions/open
action-499?
<trackbot> action-499 -- David Clarke to Review geofencing fpwd -- due 2016-03-24 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/499
david: not going to get to it, up to eyeballs
close action-499
<trackbot> Closed action-499.
action-555?
<trackbot> action-555 -- Addison Phillips to Provide implementer guidelines for how to obtain language from runtime environment, users, et al -- due 2016-09-29 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/555
close action-555
<trackbot> Closed action-555.
action-560?
<trackbot> action-560 -- Richard Ishida to Establish a process for auto-publishing updates to encoding on a regular basis -- due 2016-10-06 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/560
richard: coming along
... need a transreq
... if we get in soon, pub by 10 nov
action-564?
<trackbot> action-564 -- Addison Phillips to Provide csarven and ldn with text about language negotiation -- due 2016-10-20 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/564
close action-564
<trackbot> Closed action-564.
addison: next week is IUC40,
propose no call
... will present including status from this WG
<r12a> https://github.com/w3c/i18n-activity/projects/1
https://lists.w3.org/Archives/Public/www-international/2016OctDec/0045.html
richard: need to review UIevents
first
... created a label
addison: I created two
... just use the one?
... just use uievents
richard: xiaoqian's email wanted
like a month
... explained that we need more
... thing pushing this is a WAI doc
... want normative link
... going to REC in April
... so have some time
... dug up some stuff, pointed to last time we commented
... but they may not be valuable
... from 2010
... a few years before dealt with kbds...
do we want the same wall time or follow UTC
david: prefer same wall time
addison: prefer that too
<David> Keep wall time if possible
steve: +1
jck: prefer utc but okay with wall time
https://github.com/w3c/i18n-activity/labels/annotation-model
richard: want to know if we can meet tomorrow or 11 november
https://github.com/w3c/i18n-activity/issues/204
https://github.com/w3c/web-annotation/issues/348
<scribe> ACTION: addison: remind WG to review annotation-model issues for teleconference of 10 november and reply to their WG for a call on 11 november [recorded in http://www.w3.org/2016/10/27-i18n-minutes.html#action01]
<trackbot> Created ACTION-565 - Remind wg to review annotation-model issues for teleconference of 10 november and reply to their wg for a call on 11 november [on Addison Phillips - due 2016-11-03].
https://bugs.webkit.org/show_bug.cgi?id=159891
https://lists.w3.org/Archives/Member/member-i18n-core/2016Oct/0042.html
richard: sent bug reports to the
various browsers
... "here are your issues"
... one was to safari
... was picked up by Myles Maxfield
... another webkit person said the issue arises because they do NFC
on text
... example in comment 8
... don't think you should be normalizing this
... only safari has this problem, large number of characters
have this in this encoding
addison: but compatiiblity equiv isn't NFC??
richard: was going to say "may do
NFC on certain bits of text, but when encoding,
shouldn't"
... also example is a compat equiv
... suppose I listed both characters in a document
... on safari you get the same character
... goes back to charmod-norm
steve: different on ios?
richard: could try
... try replying one more time
https://www.w3.org/International/wiki/LanguageDetection
<scribe> ACTION: Addison: move language detection to i18n-discuss for further development and so that we can use issues [recorded in http://www.w3.org/2016/10/27-i18n-minutes.html#action02]
<trackbot> Created ACTION-566 - Move language detection to i18n-discuss for further development and so that we can use issues [on Addison Phillips - due 2016-11-03].
<r12a> https://github.com/w3c/i18n-discuss/tree/gh-pages/notes