- From: r12a <ishida@w3.org>
- Date: Thu, 23 Jan 2020 17:01:46 +0000
- To: www International <www-international@w3.org>
https://www.w3.org/2020/01/23-i18n-minutes.html
text version:
- DRAFT -
Internationalization Working Group Teleconference
23 Jan 2020
[2]Agenda
[2]
https://lists.w3.org/Archives/Member/member-i18n-core/2020Jan/0018.html
Attendees
Present
Bert, JcK, addison, r12a, Atsushi
Regrets
Fuqiao
Chair
Addison Phillips
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]TTML2, Screencapture comments review
6. [9]TTML2 comments
* [10]Summary of Action Items
* [11]Summary of Resolutions
__________________________________________________________
trackbot, prepare teleconference
<agendabot> clear agenda
<scribe> scribenick: addison
Agenda and Minutes
Action Items
[12]https://www.w3.org/International/track/actions/open
[12] https://www.w3.org/International/track/actions/open
action-851?
<trackbot> action-851 -- Richard Ishida to Review ttml issues
found in request issue 86 and send findings by next week -- due
2020-01-23 -- OPEN
<trackbot>
[13]https://www.w3.org/International/track/actions/851
[13] https://www.w3.org/International/track/actions/851
close action-851
<trackbot> Closed action-851.
action-852: \
<trackbot> action-852 -- Addison Phillips to Send an email to
chairs announcing new review request process (pending richard's
ping) -- due 2020-01-23 -- OPEN
<trackbot>
[14]https://www.w3.org/International/track/actions/852
[14] https://www.w3.org/International/track/actions/852
close action-852
<trackbot> Closed action-852.
Info Share
richard: the 15th of january msft released the new Edge browser
using blink engine
... puts me in a quandry about test results
... have been working on interactive/exploratory tests
... changed a bit over last week
... bert mentioned not putting the info in the URL
... wanted to do it
<r12a>
[15]https://github.com/w3c/i18n-tests/wiki/Test-script-for-Text
-alignment-&-justification
[15]
https://github.com/w3c/i18n-tests/wiki/Test-script-for-Text-alignment-&-justification
<r12a>
[16]https://github.com/w3c/i18n-tests/wiki/Test-script-for-Styl
ing-initials
[16]
https://github.com/w3c/i18n-tests/wiki/Test-script-for-Styling-initials
richard: also script pages related to test pages
<r12a> [17]https://w3c.github.io/typography/
[17] https://w3c.github.io/typography/
richard: so scripts for each style
RADAR and Active Work Review
[18]https://github.com/w3c/i18n-request/projects/1
[18] https://github.com/w3c/i18n-request/projects/1
TTML2, Screencapture comments review
bert: (about screen capture)
... methods can return optionally a human readable string
<r12a> [19]https://github.com/w3c/i18n-activity/issues/842
[19] https://github.com/w3c/i18n-activity/issues/842
atsushi: it's part of a promise, so visible to user agent
addison: maybe not screencapture's fault but actually a limit
of promise and exception
<atsushi_> [20]https://tc39.es/ecma262/#sec-promise.reject
[20] https://tc39.es/ecma262/#sec-promise.reject
Bert: that's how exceptions work
addison: need larger meta comment?
RESOLUTION: accept issue 842
addison: moving screen capture to awaiting comment resolution
TTML2 comments
<r12a> [21]https://w3c.github.io/i18n-activity/reviews/#ttml
[21] https://w3c.github.io/i18n-activity/reviews/#ttml
[22]https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&
q=is%3Aissue+is%3Aopen+label%3As%3Attml
[22]
https://github.com/w3c/i18n-activity/issues?utf8=✓&q=is:issue+is:open+label:s:ttml
<atsushi_> yes!
richard: 2nd edition, very close to publishing (CR)
... if any serious issues, let's close them with recycle
<r12a> [23]https://github.com/w3c/i18n-activity/issues/839
[23] https://github.com/w3c/i18n-activity/issues/839
atsushi: there are plans for 3rd edition/ttml3, so can take it
then
<atsushi_> [24]https://github.com/w3c/ttml2/milestone/8
[24] https://github.com/w3c/ttml2/milestone/8
richard: proposal for 839 is to send with extra wording
addison: what does line-break-uax14 actually mean?
... why is uax14 in the name? it also seems underspecified
[25]https://github.com/w3c/i18n-activity/issues/838
[25] https://github.com/w3c/i18n-activity/issues/838
[26]https://github.com/w3c/i18n-activity/issues/837
[26] https://github.com/w3c/i18n-activity/issues/837
<r12a> ok to send
<r12a> [27]https://github.com/w3c/i18n-activity/issues/837
[27] https://github.com/w3c/i18n-activity/issues/837
<r12a> ok to send
[28]https://github.com/w3c/i18n-activity/issues/836
[28] https://github.com/w3c/i18n-activity/issues/836
When applied to a span element (or anonymous span), the
computed value of this property, in combination with the
computed value of the tts:unicodeBidi style property,
determines the directionality of a bidirectional embedding or
override as specified by [UAX9], §4.3, Higher Level Protocol
HL3.
If a computed value of the property associated with this
attribute is not supported, then a presentation processor must
use the value ltr.
addison: doesn't say it's the default, only if the value is
unsupported (e.g. misspelled); also doesn't say you can sniff
<r12a> "If a computed value of the property associated with
this attribute is not supported, then a presentation processor
must use the value ltr."
<r12a> addison: let's word this recommendation a little more
strongly
<r12a> [29]https://github.com/w3c/i18n-activity/issues/835
[29] https://github.com/w3c/i18n-activity/issues/835
richard: shows the example is embed rather than isolate
addison: should be a defualt direction; should allow sniffing;
and should <span> isolate by default?
Summary of Action Items
Summary of Resolutions
1. [30]accept issue 842
[End of minutes]
Received on Thursday, 23 January 2020 17:01:51 UTC