Internationalization Working Group Teleconference -- 28 Mar 2019

<addison> trackbot, prepare teleconference

<agendabot> clear agenda

<addison> Scribenick: addison

Agenda and Minutes

Action Items

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

action-724?

<trackbot> action-724 -- Addison Phillips to Review "awaiting comment resolution" items and follow up -- due 2018-06-07 -- OPEN

<trackbot> https://www.w3.org/International/track/actions/724

close action-724

<trackbot> Closed action-724.

close action-728

<trackbot> Closed action-728.

action-730?

<trackbot> action-730 -- Richard Ishida to Write an article about rtl usage for non-semitic text particularly historic scripts -- due 2018-06-28 -- OPEN

<trackbot> https://www.w3.org/International/track/actions/730

close action-730

<trackbot> Closed action-730.

action-784?

<trackbot> action-784 -- Richard Ishida to Announce short checklist on home page and via tweet, addison to send to chairs@ -- due 2019-03-07 -- OPEN

<trackbot> https://www.w3.org/International/track/actions/784

<scribe> done. Addison to announce

action-788?

<trackbot> action-788 -- Addison Phillips to Remind folks to review non-semitic text rtl document -- due 2019-03-28 -- OPEN

<trackbot> https://www.w3.org/International/track/actions/788

close action-788

<trackbot> Closed action-788.

action-789?

<trackbot> action-789 -- Richard Ishida to Revive issue 96 with css as a github issue -- due 2019-03-28 -- OPEN

<trackbot> https://www.w3.org/International/track/actions/789

close action-789

<trackbot> Closed action-789.

Info Share

richard: investigating greek this week
... had leapfrogged greek and georgian when dived into sea scripts
... but quite interesting things about these scripts

<r12a> https://w3c.github.io/i18n-tests/results/case-conversion.html

richard: rewriting some of the tests
... this one is freshly done
... case conversion for greek and georgian
... all caps in greek only work if text labeled as being in Greek!
... here's another reason to use lang correctly
... also changed how tests work
... bottom of page shows assertion, more notes about how test works and what it is testing
... wished we had for a long time
... went with TTWF model
... but starting to move away from minimal test surface they have
... ours are more useful, having explanation of what's going on
... often explained in source, but no one looks there
... have to do more work to get into WPT format

addison: like this

RADAR and Active Work Review

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

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

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

<atsushi> listening, but leave from desk for ~10min. sorry.

Retiring charmod-resid

<r12a> https://www.w3.org/TR/2004/CR-charmod-resid-20041122/

should we resolve to remove charmod resid from CR status, publish as a NOTE, and retire the document

please vote now

<r12a> +1

David: +1 (via voice)

<Katy> +1

<Bert> +1

<Jeff> +1

so resolved

RESOLVED: remove charmod-resid from CR status, publish as a NOTE, and retire the document

Non-Semitic text RTL document review

richard: document as written uses <bdo> everywhere
... which means direction is encoded in markup
... so direction remains even when CSS goes away
... what you want 99% of the time
... this is what it actually looks like
... document is okay for that.
... example of taiwanese; can be argued direction is a styling choice
... so should change minus styling to be LTR presented
... like taiwanese newpaper example
... in addition to markup
... plan to change doc to say 2 use cases
... continue to use markup, <span> with class

rechartering

richard: discussed with PLH this week
... when we take on ITS docs
... nothing changes until/unless we decide to work on them
... what will happen is not just disclosure, but also patent agreements
... could do now
... also our own recs
... charmod, ruby spec

<atsushi> back