See also: IRC log
ES I18N API
<r12a> http://www.w3.org/International/track/actions/open
close ACTION-132
<trackbot> ACTION-132 (AND ALL GROUP MEMBERS) review Web Notifications for revew at 27 June WG teleconference closed
close ACTION-134
<trackbot> ACTION-134 Send Web Notifications comments closed
close ACTION-135
<trackbot> ACTION-135 Publish ruby approaches document as First Public Working Draft and announce closed
<Norbert> http://wiki.ecmascript.org/doku.php?id=globalization:specification_drafts
norbert: in last two weeks published new version (above link)
<Norbert> http://norbertlindenberg.com/2012/06/ecmascript-internationalization-api/index.html
<joconner> my headset may not be working properly. Adobe is interested in becoming more involved in Ecmascript, and encourages my participation here and with Ecma more. That's my infoshare….and now we're on that topic. Excellent.
norbert: and my "gentle intro" is
at above link
... there should be a public review, but not sure how that
works
... except maybe public-script-coord@
... hoping for feedback
richard: forwarded your email back to winter@ list because your message bounced
norbert: folks can start
reviewing
... can we agenda+ for next week
<scribe> chair: got it
norbert: hope for feedback by July 24-26 (next TC39 meeting)
<joconner> where is that TC39 meeting?
norbert: in redmond at MSFT campus
richard: also forwarded to w3c-team
addison: notes Alan W-B added Unicode support to ES6 draft
http://lists.w3.org/Archives/Public/public-iri/2012Jul/0030.html
http://lists.w3.org/Archives/Public/public-iri/2012Jul/0012.html
While the URI specification has been widely deployed, it has long been recognized that many valid URIs, especially those that contain extensive information in the "tail" are unsuitable for user presentation, especially for internationalized environments. IRIs have been proposed as a solution for that problem but inherit (and are constrained by) the complex and sometimes method-dependent syntax model of URIs as well as positional and orde
http://tools.ietf.org/html/draft-klensin-iri-sri-00
to read next week
http://www.w3.org/TR/2012/WD-css3-flexbox-20120612/
http://lists.w3.org/Archives/Public/www-international/2012JulSep/0019.html
richard: read norbert's
email
... can't think of anything to add/subtract
- Section 8.3 and 8.5 use a flex item's baseline, but don't say how that baseline is determined. CSS 2.1 defines baselines for inline tables and inline blocks, the first as the baseline of the first row of the table, the second as the baseline of its last line box in the normal flow. The latter doesn't seem likely to result in the layout shown in figure 10 in section 8.3, which seems to align based on first lines. Some clarification would be welcome.
all left-to-right examples
- The markup makes the mention of "hypothetical cross size" at the end of section 9.3 the definition of the term, but I don't see an actual definition there, or anywhere else.
koji: regarding baseline, there
was discussion around april of that
... need to lookup
<koji> http://lists.w3.org/Archives/Public/www-style/2012Apr/0414.html
koji: was resolved, but if it didn't get in the spec, we should make feedback
norbert: will read up on it and adjust accordingly
main comment: need different direction examples
<scribe> ACTION: Norbert: add CSS3 Flexbox comments to tracker and forward to CSS WG [recorded in http://www.w3.org/2012/07/11-i18n-minutes.html#action01]
<trackbot> Created ACTION-136 - Add CSS3 Flexbox comments to tracker and forward to CSS WG [on Norbert Lindenberg - due 2012-07-18].
<koji> http://lists.w3.org/Archives/Public/www-style/2012Jul/0179.html
what is the progression direction when you have both horizontal and vertical in the same book?
koji: is "right column first" the
better solution?
... if number of columns grow, then computation becomes
complex
... it becomes very theoretical because page-progression and
column progression become mixed
addison: PPD alteration happens
on a spread, but not over a larger sequence of pages
... will also ask my colleagues if they have additional
feedback
koji: wirting-modes next
week
... okay to review ED?
<scribe> chair: yes
UNKNOWN_SPEAKER: review the best document for feedback
richard: concerns about moving to
last call
... delaying because of our comments
addison: do they have plans to modify their document?
richard: two topics
... i. label fragments
... ii. whether multiple is allowed
... and (i) is the one we originally asked for
... separate directionality from language
... helpful to have guidelines to point to at earlier
stage
<scribe> ACTION: richard: make a wiki page with the basis for general guidelines for everyone to pile on [recorded in http://www.w3.org/2012/07/11-i18n-minutes.html#action02]
<trackbot> Created ACTION-137 - Make a wiki page with the basis for general guidelines for everyone to pile on [on Richard Ishida - due 2012-07-18].
norbert: withdraw localized fragments?
richard: second that
addison: agree
<scribe> ACTION: Addison: follow up on Web Notifications in three separate emails to separate threads, closing off localized fragments and direction and asking for resolution on language [recorded in http://www.w3.org/2012/07/11-i18n-minutes.html#action03]
<trackbot> Created ACTION-138 - Follow up on Web Notifications in three separate emails to separate threads, closing off localized fragments and direction and asking for resolution on language [on Addison Phillips - due 2012-07-18].