Internationalization Working Group Teleconference -- 14 Dec 2017

trackbot, prepare teleconference

<scribe> ScribeNick: addison

Agenda

Action Items

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

action-690?

<trackbot> action-690 -- Addison Phillips to Include comment resolution for text-decoration next week and remind all to review issues -- due 2017-12-14 -- OPEN

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

close action-690

<trackbot> Closed action-690.

Info Share

xfq: we have clreq meeting today
... plan to publish new WD
... saw previous one was published by richard
... haven't done a multi language doc before
... anything to pay attention to?

richard: there were some things, need to look tomorrow
... ask I18N WG if okay to publish

xfq: don't have formal resolution but rough consensus

<xfq> https://github.com/w3c/wpub/issues?q=is:open+is:issue+label:topic:internationalization

<xfq> https://github.com/w3c/wpub/issues/1#issuecomment-315815699

xfq: saw topics in above
... one mentioned our string-meta
... do we need to track?

richard, addison: yes

richard; couple of things

<r12a> https://github.com/whatwg/html/pull/3091

scribe: whatwg is looking at (iiuc) requiring HTML to be UTF-8

addison: what??

richard: another issue

<r12a> https://github.com/readium/readium-css/issues/26#issuecomment-351503354

<r12a> https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project

richard: set up a document about setting up to do a gap analysis
... welcome comments

Radar

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

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

richard: UTR53 v2, I reviewed it , topic later
... published inline bidi
... now published
... lots of retweets and likes :-)

Publish FPWD of ALREQ?

<r12a> https://w3c.github.io/alreq/

richard: the ALREQ folks are working on a gap analysis also for the new year
... also wish to publish a FPWD
... some images missing that need fixing
... some additional text by beignning of year
... any objection?

addison: do you support publication of ALREQ FPWD?

<r12a> +

<najib> +1

<Steve_Atkin> +1

<xfq> +1

<r12a> +1

<JcK> 0 (having not heard discussion)

addison: so resolved

UTR53 comments

richard: hopefully sent email that made clear

<r12a> http://w3c.github.io/i18n-activity/reviews/#utr53

https://github.com/w3c/i18n-activity/issues/517

sounds like a good comment

<scribe> ACTION: richard: put a foot in the door on UTR53 comments if needed

<trackbot> Created ACTION-691 - Put a foot in the door on utr53 comments if needed [on Richard Ishida - due 2017-12-21].

CSS text-decoration comment review

http://w3c.github.io/i18n-activity/reviews/#css-text-decor

close 21

https://github.com/w3c/i18n-activity/issues/385

richard: kind of fuzzy

jck: some informal comments
... "never seen this before"

addison: could conclude that it's unnecessary

jck: add an explicit placeholder?
... prevent head-scratching?

richard: might be useful to make them scratch their heads :-)

https://github.com/w3c/i18n-activity/issues/22

<r12a> https://github.com/w3c/jlreq/issues/8

close 22 as a duplicate of 383?

https://www.w3.org/TR/css-text-decor-3/#text-emphasis-position-property

Emphasis marks are drawn exactly as if each character was assigned the mark as its ruby annotation text with the ruby position given by ‘text-emphasis-position’ and the ruby alignment as centered.

If emphasis marks are applied to characters for which ruby is drawn in the same position as the emphasis mark, the emphasis marks are placed above the ruby.

addresses my comment

close #22

Charmod and String-Meta

AOB?

next teleconference on 11 January 2018

(and there was much rejoicing)

- DRAFT -

Internationalization Working Group Teleconference

14 Dec 2017

Attendees

Contents