See also: IRC log
joining information is here https://www.w3.org/2017/09/i18n-meeting-info.html
previous minutes: https://www.w3.org/2017/09/28-i18n-minutes.html
visually KA+VIRAMA+SHA = KA+ZWJ+AA
http://www.w3.org/International/track/actions/open
close action-656
<trackbot> Closed action-656.
was "Notify websub we are satisfied with 124"
De-pend all the css-text-decor issues
close action-659
<trackbot> Closed action-659.
none
http://www.unicode.org/reports/tr53/
https://github.com/w3c/i18n-activity/issues?q=is%3Aissue+is%3Aopen+label%3Autr53
https://github.com/w3c/i18n-activity/issues/492#issuecomment-334101665
[[
I'm beginning to suspect that the algorithm described is intended to just indicate how characters should be temporarily reordered prior to rendering, rather than describe the order in which code points should be stored. Since most fonts generally produce the behaviour described anyway, it would therefore amount to documenting expectations in terms of font behaviour, rather than specifying a new form of normalisation.
It's not at all clear from the document whether that is the case, however, so i think that has to be our first question, and perhaps we need to await an answer to that before sending in many of the other comments.
]]
JcK: I believe i concur
... it may describe new problems wrt confusables
... may be worth saying that if we correctly understood this,
the document needs to be updated to make it clear
<scribe> ACTION: Richard to raise comment against UTR53 asking for clarity about what they are trying to do [recorded in http://www.w3.org/2017/10/05-i18n-minutes.html#action01]
<trackbot> Created ACTION-660 - Raise comment against utr53 asking for clarity about what they are trying to do [on Richard Ishida - due 2017-10-12].
https://github.com/w3c/i18n-activity/issues/490
raise this as a personal comment
RESOLUTION: Richard send comment for which he has action, then await response before sending more
https://lists.w3.org/Archives/Public/www-international/2017OctDec/0002.html
intersection-observer
• rootMargin may need to be directionally sensitive
https://github.com/w3c/i18n-activity/issues/488
<scribe> ACTION: Richard to send https://github.com/w3c/i18n-activity/issues/488 to Intersection Observer group [recorded in http://www.w3.org/2017/10/05-i18n-minutes.html#action02]
<trackbot> Created ACTION-661 - Send https://github.com/w3c/i18n-activity/issues/488 to intersection observer group [on Richard Ishida - due 2017-10-12].
https://github.com/w3c/i18n-activity/issues/410
agree to close
https://github.com/w3c/i18n-activity/issues/334
added a note at https://github.com/w3c/ttml2/commit/f9e4a418819b8226d0ce5c828befc55042848c9d
agree to close
https://github.com/w3c/i18n-activity/projects/1
Any reaction for DNT would appreciated by the WG - so they can report status.
even if no review done
http://w3c.github.io/typography/gap-analysis/language-matrix.html
Meeting adjourned.
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: JcK r12a david andrew Bert No ScribeNick specified. Guessing ScribeNick: r12a Inferring Scribes: r12a WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 05 Oct 2017 Guessing minutes URL: http://www.w3.org/2017/10/05-i18n-minutes.html People with action items: richard[End of scribe.perl diagnostic output]