- From: r12a <ishida@w3.org>
- Date: Mon, 27 Feb 2017 09:38:32 +0000
- To: www International <www-international@w3.org>
https://www.w3.org/2017/02/16-i18n-minutes.html
text version:
Internationalization Working Group Teleconference
16 Feb 2017
See also: [2]IRC log
[2] http://www.w3.org/2017/02/16-i18n-irc
Attendees
Present
Addison, Richard, Steve
Regrets
Felix, David
Chair
Addison Phillips
Scribe
Addison Phillips
Contents
* [3]Topics
1. [4]agenda
2. [5]Action Items
3. [6]Review open comments
* [7]Summary of Action Items
* [8]Summary of Resolutions
__________________________________________________________
trackbot, prepare teleconference
<scribe> ScribeNick: addison
<scribe> Scribe: Addison Phillips
urk... getting 401 on the member-i18n-core archive
agenda
Action Items
[9]https://www.w3.org/International/track/actions/open
[9] https://www.w3.org/International/track/actions/open
action-536?
close action-536
<trackbot> action-536 -- Richard Ishida to Publish
predefined-counter-styles as a wg note -- due 2016-06-30 --
OPEN
<trackbot>
[10]http://www.w3.org/International/track/actions/536
[10] http://www.w3.org/International/track/actions/536
<trackbot> Closed action-536.
action-588?
<trackbot> action-588 -- Addison Phillips to File additional
tickets for support of predefined counter styles against
remaining browsers -- due 2017-02-09 -- OPEN
<trackbot>
[11]http://www.w3.org/International/track/actions/588
[11] http://www.w3.org/International/track/actions/588
close action-588
<trackbot> Closed action-588.
action-593?
<trackbot> action-593 -- Addison Phillips to Add jck as point
man when adding slim to review radar -- due 2017-02-16 -- OPEN
<trackbot>
[12]http://www.w3.org/International/track/actions/593
[12] http://www.w3.org/International/track/actions/593
[13]https://github.com/w3c/i18n-activity/projects/1
[13] https://github.com/w3c/i18n-activity/projects/1
Review open comments
[14]http://w3c.github.io/i18n-activity/reviews/
[14] http://w3c.github.io/i18n-activity/reviews/
[15]https://github.com/w3c/i18n-activity/issues/324
[15] https://github.com/w3c/i18n-activity/issues/324
[16]https://github.com/w3c/i18n-activity/issues/311
[16] https://github.com/w3c/i18n-activity/issues/311
richard: answer is a little vague; a character or a grapheme
cluster
[17]https://github.com/w3c/i18n-activity/issues/313
[17] https://github.com/w3c/i18n-activity/issues/313
richard: slightly bigger thing
... using styling to do mapping of semantics, think you should
use markup for that
... model may be from xsl:fo, not designed for human
consumption
... really want to put semantics into inline markup
[18]https://github.com/w3c/i18n-activity/issues/315
[18] https://github.com/w3c/i18n-activity/issues/315
richard: they show two bits of complex ruby but it's just two
group rub
... better example would be mono for semantics and group for
pronunciation
... want to see if they support these cases
[19]https://github.com/w3c/i18n-activity/issues/316
[19] https://github.com/w3c/i18n-activity/issues/316
richard: no rules about how to handle mismatch in number of
elements
[20]https://github.com/w3c/i18n-activity/issues/314
[20] https://github.com/w3c/i18n-activity/issues/314
richard: thinking of not sending this
... they're using ruby annotation spec as their markup model
... rather than html model
... less clear cut than that
... hard to figure out what is in or out
... nto quite ruby annotation
... but actually, maybe ruby annotation isn't necessarily all
bad
... maybe we need a new version?
... we've had a bunch of folks like this trying to "invent"
ruby markup
... don't want to send now, but some significant work to do
there
[21]https://github.com/w3c/i18n-activity/issues/317
[21] https://github.com/w3c/i18n-activity/issues/317
[22]https://github.com/w3c/i18n-activity/issues/318
[22] https://github.com/w3c/i18n-activity/issues/318
[23]https://github.com/w3c/i18n-activity/issues/319
[23] https://github.com/w3c/i18n-activity/issues/319
[24]https://github.com/w3c/i18n-activity/issues/320
[24] https://github.com/w3c/i18n-activity/issues/320
[25]https://github.com/w3c/i18n-activity/issues/325
[25] https://github.com/w3c/i18n-activity/issues/325
richard: might want to stick on it the warning about ja or zh
so fonts can default well
addison: agreed
[26]https://github.com/w3c/i18n-activity/issues/326
[26] https://github.com/w3c/i18n-activity/issues/326
addison: may be obselete because tts:direciton
... but metadata?
richard: have a similar comment
... #345
[27]https://github.com/w3c/i18n-activity/issues/327
[27] https://github.com/w3c/i18n-activity/issues/327
[28]https://github.com/w3c/i18n-activity/issues/331
[28] https://github.com/w3c/i18n-activity/issues/331
[29]https://github.com/w3c/i18n-activity/issues/332
[29] https://github.com/w3c/i18n-activity/issues/332
what is the impact on line height
[30]https://github.com/w3c/i18n-activity/issues/333
[30] https://github.com/w3c/i18n-activity/issues/333
[31]https://github.com/w3c/i18n-activity/issues/334
[31] https://github.com/w3c/i18n-activity/issues/334
[32]https://github.com/w3c/i18n-activity/issues/335
[32] https://github.com/w3c/i18n-activity/issues/335
[33]https://github.com/w3c/i18n-activity/issues/337
[33] https://github.com/w3c/i18n-activity/issues/337
<addison_> [34]https://github.com/w3c/i18n-activity/issues/340
[34] https://github.com/w3c/i18n-activity/issues/340
<addison_> [35]https://github.com/w3c/i18n-activity/issues/341
[35] https://github.com/w3c/i18n-activity/issues/341
<addison_> [36]https://github.com/w3c/i18n-activity/issues/342
[36] https://github.com/w3c/i18n-activity/issues/342
<addison_> [37]https://github.com/w3c/i18n-activity/issues/343
[37] https://github.com/w3c/i18n-activity/issues/343
<addison_> [38]https://github.com/w3c/i18n-activity/issues/328
[38] https://github.com/w3c/i18n-activity/issues/328
<addison_> richard: in direction section point to unicodeBidi
<addison_> ... will change
<addison_> [39]https://github.com/w3c/i18n-activity/issues/344
[39] https://github.com/w3c/i18n-activity/issues/344
<addison_> [40]https://github.com/w3c/i18n-activity/issues/345
[40] https://github.com/w3c/i18n-activity/issues/345
<addison_> [41]https://github.com/w3c/i18n-activity/issues/330
[41] https://github.com/w3c/i18n-activity/issues/330
<addison_> should have a question about writing-mode coercing
direction: we think it should not do so but xsl might imply
that it does
<addison_> addison: you're right
<addison_> [42]https://github.com/w3c/i18n-activity/issues/346
[42] https://github.com/w3c/i18n-activity/issues/346
Summary of Action Items
Summary of Resolutions
[End of minutes]
Received on Monday, 27 February 2017 09:38:47 UTC