See also: IRC log
richard: time zone offsets?
https://www.w3.org/International/track/actions/open
action-534?
<trackbot> action-534 -- Addison Phillips to Ping martin about unicode in xml -- due 2016-06-30 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/534
close action-534
<trackbot> Closed action-534.
action-535?
<trackbot> action-535 -- Addison Phillips to Add note to issue 33 saying we don't agree before closing -- due 2016-06-30 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/535
close action-535
<trackbot> Closed action-535.
action-536?
<trackbot> action-536 -- Richard Ishida to Publish predefined-counter-styles as a wg note -- due 2016-06-30 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/536
action-538?
<trackbot> action-538 -- Addison Phillips to Work with richard and plh to establish procedure for bringing changes to encoding forward -- due 2016-06-30 -- OPEN
<trackbot> http://www.w3.org/International/track/actions/538
<scribe> pending for 2 weeks, due to plh etc. being away
<r12a> regrets Felix
sign up for TPAC
<r12a> https://www.w3.org/2002/09/wbs/34786/AV_TPAC2016/
<r12a> https://www.w3.org/2002/09/wbs/35125/TPAC2016/
a/v request: projector, flip chart, phone??
http://w3c.github.io/i18n-activity/radar/
<r12a> https://w3c.github.io/i18n-activity/reviews/
richard: another about to come
through
... with lots of calendars and dates
<r12a> http://w3c.github.io/sdw/time/
richard: not FPWD
http://w3c.github.io/i18n-activity/projects/
https://w3c.github.io/i18n-activity/reviews/
https://github.com/w3c/i18n-activity/issues/166
https://github.com/w3c/i18n-activity/issues/167
jck: text/plain is us-ascii if no
charset
... parameter should almost be required
forward this
https://github.com/w3c/i18n-activity/issues/168
is this thing multipart? how does it get localized? language negotiation via accept-language?
forward this
https://github.com/w3c/i18n-activity/issues/171
2016-07-09T13: 12:11+08:00
https://www.w3.org/TR/timezone/
2016-12-30T13: 12:11+07:00
America/Phoenix
health warning
https://github.com/w3c/i18n-activity/issues/172
https://github.com/w3c/i18n-activity/issues/173
https://github.com/w3c/i18n-activity/issues/174
https://github.com/w3c/i18n-activity/issues/176
(discussion of need for language and direction)
https://github.com/w3c/i18n-activity/issues/177
https://github.com/w3c/i18n-activity/issues/178
https://www.w3.org/TR/activitystreams-vocabulary/#dfn-name
https://github.com/w3c/i18n-activity/issues/179
This is not based on any of the formats in ISO 8601. It is intended to be a more human-readable alternative to the ISO 8601 duration format.
https://github.com/w3c/i18n-activity/issues/175
content-language? or document as a whole could have a field for the default?
"content": "foo"
"content": "foo"@en
<JcK> Re: 179 - yes, but there aer, again, multiple supposedly human-friendly formats in popular use and most of them are confusable with each other and inconsistent in edge cases, so this is not a happy situation either.
name: name; name-dir:rtl; name-lang=en
we have a wiki somewhere
<r12a> https://github.com/whatwg/encoding/issues
https://www.w3.org/International/tests/repo/results/encoding-dbl-byte.en