Internationalization Working Group Teleconference

Meeting minutes

<addison> trackbot, prepare teleconference

Agenda Review

Action Items

<addison> https://www.w3.org/International/track/actions/open

<addison> action-1022?

<trackbot> Error querying: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

<addison> https://www.w3.org/International/track/actions/1022

<addison> close action-1022

<trackbot> Closed action-1022.

<addison> https://www.w3.org/International/track/actions/1024

<addison> https://www.w3.org/International/track/actions/1026

<addison> close action-1026

<trackbot> Closed action-1026.

Info Share

<r12a> https://github.com/w3c/i18n-activity/projects/3

richard: link above
… as told before, gap-analysis project is here
… consolidated items on this project
… exactly 100 issues listed, 63 need to be investigated
… once work done, moving to another column
… few additional idea on how issue is important, what relates

addison: documentation on what to do?

richard: you can open issue, following template
… template is written in pretty detail

addison: open to large community?

richard: need to be performed by TF participants
… if ones already in these groups, it's fantastic if they can take roles

richard: working on my application in personal site

<r12a> https://r12a.github.io/pickers/armn/

richard: lot of little tools here
… and making language tools into one bigger integrated tool
… left hand side, narrow box you can select type of input, and you can type characters/sentence with these

richard: you can share characters into other applications, like character use cases, or from uniview

RADAR Review

<addison> https://github.com/w3c/i18n-request/projects/1

addison: CSS multicolumn layout module level 1

CSS column layout

<xfq> https://github.com/w3c/i18n-request/issues/153

xfq: in the issue, I've commented

<r12a> https://www.w3.org/TR/css-multicol-1/

xfq: multicolumn layout can be adopted into writing mode

richard: implementers could be fully aware on vertical writing with this
… ones like short sentence could need some care
… the biggest issue for me is terminology
… it's been used for long time, one sentence in the spec mentions line with different direction

addison: to be action?

richard: whether asking to them for this?

xfq: yes, inline base direction for different writing mode could be mentioned, and it could be helpful for implementers

richard: agree. as editorial request

<r12a> https://r12a.github.io/scripts/mongolian/#generallayout

richard: have some example for mongolian, need some more from other language

atsushi: will work on for japanese

Action: richard: file issue on css multi-col to clarify columns in vertical

<trackbot> Created ACTION-1027 - File issue on css multi-col to clarify columns in vertical [on Richard Ishida - due 2021-05-27].

personalization semantics issue

<xfq> https://github.com/w3c/personalization-semantics/issues/144

xfq: team contact said to me on the issue above
… asked whether we are satisfied with this or not, for expected publicaiton of spec in near future

richard: addison reopened the issue, what was the reason?

xfq: still have some open issues
… this issue is for metadata, rely on lang and dir

addison: question is that symbology follows the same language and direction

richard: the first comment addison made could be clearer about the problem we are concerned about

addison: don't understand what there reply states...
… will comment with questions to this issue

Action: addison: update personalization-semantics issue with clarifying statements and questions

<trackbot> Created ACTION-1028 - Update personalization-semantics issue with clarifying statements and questions [on Addison Phillips - due 2021-05-27].