- From: r12a <ishida@w3.org>
- Date: Thu, 5 Dec 2019 16:42:00 +0000
- To: www International <www-international@w3.org>
https://www.w3.org/2019/12/05-i18n-minutes.html
text version follows:
- DRAFT -
Internationalization Working Group Teleconference
05 Dec 2019
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2019Dec/0000.html
Attendees
Present
addison, Fuqiao, Bert, atsushi, David, r12a, JcK
Regrets
Chair
Addison
Scribe
addison
Contents
* [3]Topics
1. [4]Agenda and Minutes
2. [5]Action Items
3. [6]Info Share
4. [7]RADAR and Active Work Review
5. [8]DOM spec review
6. [9]handling review requests
7. [10]AOB?
* [11]Summary of Action Items
* [12]Summary of Resolutions
__________________________________________________________
trackbot, prepare teleconference
<agendabot> clear agenda
Agenda and Minutes
Action Items
[13]https://www.w3.org/International/track/actions/open
[13] 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>
[14]https://www.w3.org/International/track/actions/847
[14] 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> [15]https://r12a.github.io/scripts/tamil/
[15] 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>
[16]https://w3c.github.io/i18n-tests/css-text/line-breaking/exp
-generic-line-break-000.html
[16]
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
[17]https://github.com/w3c/i18n-tests/wiki/Test-script-for-line
-break-&-word-break (see below)
[17]
https://github.com/w3c/i18n-tests/wiki/Test-script-for-line-break-&-word-break
<r12a> [1]
[1] http://www.w3.org/
<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]
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2019Dec/0000.html
<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> [18]https://github.com/w3c/type-samples/issues
[18] https://github.com/w3c/type-samples/issues
<r12a> [19]https://w3c.github.io/i18n-activity/reviews/
[19] https://w3c.github.io/i18n-activity/reviews/
<r12a> [20]http://w3c.github.io/i18n-activity/textlayout/
[20] http://w3c.github.io/i18n-activity/textlayout/
RADAR and Active Work Review
[21]https://github.com/w3c/i18n-activity/projects/1
[21] https://github.com/w3c/i18n-activity/projects/1
<atsushi> TTML2 REC->WD diff:
[22]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
[22]
https://services.w3.org/htmldiff?doc1=https://www.w3.org/TR/2018/REC-ttml2-20181108/&doc2=https://w3c.github.io/ttml2/index.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>
[23]https://www.w3.org/International/wiki/Raise-a-review-reques
t#Proposed_process
[23]
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>
[24]https://w3c.github.io/i18n-tests/css-text/line-breaking/exp
-generic-line-break-000.html
[24]
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]
Received on Thursday, 5 December 2019 16:42:04 UTC