- From: r12a <ishida@w3.org>
- Date: Fri, 15 Dec 2017 13:35:35 +0000
- To: www International <www-international@w3.org>
https://www.w3.org/2017/12/14-i18n-minutes.html#item05 text extract follows: - DRAFT - Internationalization Working Group Teleconference 14 Dec 2017 [2]Agenda [2] https://lists.w3.org/Archives/Member/member-i18n-core/2017Dec/0015.html Attendees Present Addison, Richard, Fuqiao, Steve, Bert, JcK, Najib, (via, IRC) Regrets Chair Addison Phillips Scribe addison Contents * [3]Topics 1. [4]Agenda 2. [5]Action Items 3. [6]Info Share 4. [7]Radar 5. [8]Publish FPWD of ALREQ? 6. [9]UTR53 comments 7. [10]CSS text-decoration comment review 8. [11]Charmod and String-Meta 9. [12]AOB? * [13]Summary of Action Items * [14]Summary of Resolutions __________________________________________________________ trackbot, prepare teleconference <scribe> ScribeNick: addison Agenda Action Items [15]https://www.w3.org/International/track/actions/open [15] 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> [16]http://www.w3.org/International/track/actions/690 [16] 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> [17]https://github.com/w3c/wpub/issues?q=is:open+is:issue+label :topic:internationalization [17] https://github.com/w3c/wpub/issues?q=is:open+is:issue+label:topic:internationalization <xfq> [18]https://github.com/w3c/wpub/issues/1#issuecomment-315815699 [18] 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> [19]https://github.com/whatwg/html/pull/3091 [19] 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> [20]https://github.com/readium/readium-css/issues/26#issuecomme nt-351503354 [20] https://github.com/readium/readium-css/issues/26#issuecomment-351503354 <r12a> [21]https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Ana lysis-Project [21] 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 [22]https://github.com/w3c/i18n-activity/projects/1 [22] https://github.com/w3c/i18n-activity/projects/1 [23]http://w3c.github.io/i18n-activity/projects/ [23] 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> [24]https://w3c.github.io/alreq/ [24] 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? +1 <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> [25]http://w3c.github.io/i18n-activity/reviews/#utr53 [25] http://w3c.github.io/i18n-activity/reviews/#utr53 [26]https://github.com/w3c/i18n-activity/issues/517 [26] 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 [27]http://w3c.github.io/i18n-activity/reviews/#css-text-decor [27] http://w3c.github.io/i18n-activity/reviews/#css-text-decor close 21 [28]https://github.com/w3c/i18n-activity/issues/385 [28] 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 :-) [29]https://github.com/w3c/i18n-activity/issues/22 [29] https://github.com/w3c/i18n-activity/issues/22 <r12a> [30]https://github.com/w3c/jlreq/issues/8 [30] https://github.com/w3c/jlreq/issues/8 close 22 as a duplicate of 383? [31]https://www.w3.org/TR/css-text-decor-3/#text-emphasis-posit ion-property [31] 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) Summary of Action Items [NEW] ACTION: richard: put a foot in the door on UTR53 comments if needed Summary of Resolutions [End of minutes]
Received on Friday, 15 December 2017 13:35:49 UTC