W3C

- DRAFT -

Internationalization Working Group Teleconference

19 Jan 2017

Agenda

See also: IRC log

Attendees

Present
felix, JohnO, Addison, Steve, Richard, Felix
Regrets
David
Chair
Addison Phillips
Scribe
Addison Phillips

Contents


Agenda

Action Items

https://www.w3.org/International/track/actions/open

action-358?

<trackbot> action-358 -- Felix Sasaki to Retire requirements for its 2.0 -- due 2014-11-06 -- OPEN

<trackbot> http://www.w3.org/International/track/actions/358

action-412?

<trackbot> action-412 -- Felix Sasaki to Publish multilingual web usage scenarios -- due 2015-03-12 -- OPEN

<trackbot> http://www.w3.org/International/track/actions/412

felix: converted these to respec
... wondering about next step to publish
... one thing is that we should add something say "published as notes"
... won't be worked on further
... published by WG or by ITS-IG?
... currently say IG
... docs in my private github repo
... where do I put them?

<fsasaki> http://fsasaki.github.io/stuff/its2req/index-as-respec.html

<fsasaki> http://fsasaki.github.io/stuff/mlw-metadata-us-impl/index-as-respec.html

richard: are they pub ready?

felix: need to check

richard: normal pub req
... check valid, checklinks, pubrules
... will set up a separate repo for each
... can set up

<scribe> ACTION: richard: set up two repos for felix's documents from ITS for final publication as Note [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action01]

<trackbot> Created ACTION-580 - Set up two repos for felix's documents from its for final publication as note [on Richard Ishida - due 2017-01-26].

felix: which group? WG or IG?

richard: you'll see some text like this in LReq
... check ready for pub; I'll create repos; transfer them; then check pubrules; decide who to raise pub req

action-541?

<trackbot> action-541 -- Richard Ishida to Revise issue 159 about modifier keys and make appropriate revisions -- due 2016-07-28 -- OPEN

<trackbot> http://www.w3.org/International/track/actions/541

close action-451

<trackbot> Closed action-451.

close action-541

<trackbot> Closed action-541.

action-451?

<trackbot> action-451 -- Addison Phillips to Respond on csvw issue 617 officially explaining that the wg believes that cldr's values and data structures are needed -- due 2015-07-09 -- CLOSED

<trackbot> http://www.w3.org/International/track/actions/451

close action-573

<trackbot> Closed action-573.

Info Share

Radar and Active Work Review

https://github.com/w3c/i18n-activity/projects/1

http://w3c.github.io/i18n-activity/projects/

https://github.com/whatwg/url/pull/199

richard: meeting of ad hoc scripts cmte
... discussion of nnbsp in mongolian
... change mongolian so it doesn't use narrow non break space

<scribe> ... new char they'd use instead

richard: in part because nnbsp is used to separate suffixes
... mongolian is agglutinative
... not always but often separated by a very small space
... when you do selection/line break, should not be treated as space
... don't do these thing properly
... if fallback font is Arial, then fonts don't produce right behavior
... so asking for a new character, Unicode pushing back
... proposal doc to be written

richard: don't know if nnbsp is considered whitespace

For internal review: Styling vertical Chinese, Japanese, Korean and Mongolian text

http://w3c.github.io/i18n-drafts/articles/vertical-text.en

richard: is this ready for wide review?

steve: looked through it; greatly impressed; ready for wide review

<r12a> add an issue styling so that it's clear we're looking for feedback

<scribe> ACTION: richard: send vertical article for wide review after getting final feedback and fixing the issue styling [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action02]

<trackbot> Created ACTION-581 - Send vertical article for wide review after getting final feedback and fixing the issue styling [on Richard Ishida - due 2017-01-26].

Typography Document ready for wide review?

http://w3c.github.io/typography/

http://w3c.github.io/typography/checklist

richard: stuff that fantasai wrote about how justification works has a few issues that I need to address
... so probably not ready

<scribe> ACTION: richard: sort out justification text on typography document [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action03]

<trackbot> Created ACTION-582 - Sort out justification text on typography document [on Richard Ishida - due 2017-01-26].

any ideas for how to publicize issues we have? send to the group

Charmod-Norm ready for wide review?

http://w3c.github.io/charmod-norm/

<scribe> ACTION: addison: review charmod-norm issues list and propose closure [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action04]

<trackbot> Created ACTION-583 - Review charmod-norm issues list and propose closure [on Addison Phillips - due 2017-01-26].

AOB?

<Steve_Atkin> https://github.com/w3c/i18n-activity/issues/310

steve: get a list of remote devices for playback?
... can't specifically think of a case

https://github.com/whatwg/infra/issues/1#issuecomment-273485493

Summary of Action Items

[NEW] ACTION: addison: review charmod-norm issues list and propose closure [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action04]
[NEW] ACTION: richard: send vertical article for wide review after getting final feedback and fixing the issue styling [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action02]
[NEW] ACTION: richard: set up two repos for felix's documents from ITS for final publication as Note [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action01]
[NEW] ACTION: richard: sort out justification text on typography document [recorded in http://www.w3.org/2017/01/19-i18n-minutes.html#action03]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2017/01/19 17:04:13 $