W3C

- DRAFT -

Internationalization Working Group Teleconference

05 Dec 2019

Agenda

Attendees

Present
addison, Fuqiao, Bert, atsushi, David, r12a, JcK
Regrets
Chair
Addison
Scribe
addison

Contents


trackbot, prepare teleconference

<agendabot> clear agenda

Agenda and Minutes

Action Items

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

action-847?

<trackbot> action-847 -- Richard Ishida to Document proposed repo-based review request mechanism -- due 2019-11-28 -- OPEN

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

close action-847

<trackbot> Closed action-847.

Info Share

richard: been feeling guilty about work on language enablement
... doing process and backlog, etc.
... so last few days making concerted effort to learn about tamil
... and pull info from IIP together
... and updating gap analyis docs
... fallout is researching tamil in own time

<r12a> https://r12a.github.io/scripts/tamil/

richard: accumulating information here to put in layout requirements
... started writing doc on segmentation of text in south asian languages
... forget about orthographic syllables, don't work the way you think
... issue caused by grapheme clusters has nothing to do with code points
... has to do with what font does
... like consonent consonent vowel
... consonent virama consonent vowel segments after virama
... etc.
... what makes diff is making conjuncts
... those don't break when you wrap
... can't work ut from the code points
... some examples in tamil illustrate also that segmentation may not be grapheme cluster related at all, but glyph related
... in a single column in fully justified text
... short word but nothing else fits and they use intercharacter spacing
... does it on "certain glyphs"
... if the ink is not attanched then put space, but don't if there attachment
... again, nothing to do with code points; just glyph

addison: so this is like half forms don't break but non conjuncts do

richard: old indic doc had an ABNF
... didn't work for tamil
... or other south indian language
... and often not in north indian languages too!

<r12a> https://w3c.github.io/i18n-tests/css-text/line-breaking/exp-generic-line-break-000.html

<r12a> working on a new, very simple format for tests that can be used for gap-analysis or for spinning up the normal fixed tests: starts with a language-anonymous test page like that in the link above, plus a script which captures an assertion, test data, and results and is written as a simple editable file such as https://github.com/w3c/i18n-tests/wiki/Test-script-for-line-break-&-word-break (see below)

<r12a> [1]

<r12a> line-break:anywhere should break before U+0BC8: TAMIL VOWEL SIGN AI

<r12a> , not before the U+0BB1: TAMIL LETTER RRA that begins the consonant cluster. It should wrap the vowel-sign together with the preceding consonant.

<r12a> யாவற்றையும்

<r12a> FF ok

<r12a> Saf ok

<r12a> Ch anywhere not supported

<r12a> [2]

<r12a> same but with word-break: break-all

<r12a> FF ok

<r12a> Saf weird:

<r12a> Ch weird:

<r12a> weird = breaks word between யாவ and ற்றையும் only

<r12a> ]]

<r12a> https://github.com/w3c/type-samples/issues

<r12a> https://w3c.github.io/i18n-activity/reviews/

<r12a> http://w3c.github.io/i18n-activity/textlayout/

RADAR and Active Work Review

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

<atsushi> TTML2 REC->WD diff: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2F2018%2FREC-ttml2-20181108%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fttml2%2Findex.html

richard: css text might be on the move

addison: no eta?

richard: no, just rumor from florian

bert: no progress on intersection observer; will do before xmas

DOM spec review

think about how to handle snapshot reviews for next time

handling review requests

<r12a> https://www.w3.org/International/wiki/Raise-a-review-request#Proposed_process

<scribe> ACTION: addison: write to plh about automating review requests

<trackbot> Created ACTION-848 - Write to plh about automating review requests [on Addison Phillips - due 2019-12-12].

AOB?

<r12a> https://w3c.github.io/i18n-tests/css-text/line-breaking/exp-generic-line-break-000.html

richard: consider generic tests (see above example) for next week

Summary of Action Items

[NEW] ACTION: addison: write to plh about automating review requests
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/12/05 16:40:28 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/some examples in tamil/some examples in tamil illustrate also that segmentation may not be grapheme cluster related at all, but glyph related/
Succeeded: s/[[/working on a new, very simple format for tests that can be used for gap-analysis or for spinning up the normal fixed tests: starts with a language-anonymous test page like that in the link above, plus a script which captures an assertion, test data, and results and is written as a simple editable file (see below)/
Succeeded: s/simple editable file/simple editable file such as https://github.com/w3c/i18n-tests/wiki/Test-script-for-line-break-&-word-break/
Default Present: addison, Fuqiao, Bert, atsushi, David, r12a, JcK
Present: addison Fuqiao Bert atsushi David r12a JcK
No ScribeNick specified.  Guessing ScribeNick: addison
Inferring Scribes: addison
Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2019Dec/0000.html
Found Date: 05 Dec 2019
People with action items: addison write

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]