See also: IRC log
<aphillip> close action-177
<trackbot> Closed ACTION-177 Establish scribing rotation.
<aphillip> close action-178
<trackbot> Closed ACTION-178 Coordinate proposing text for ITS directionality with richard.
<aphillip> close action-179
<trackbot> Closed ACTION-179 Publish BOM document.
<aphillip> close action-180
<trackbot> Closed ACTION-180 File individual comments on css3-text-decoration.
<aphillip> Tipic: Info Share
Addison: TPAC will be in Shenzhen in November
Addison: we have new members: John Klensin
<r12a> Aharon Lanin (rejoined)
<r12a> Ning Jin-Grisaffi (Microsoft)
<r12a> replaces Emile Tran
Richard: overhauled index to unify topics
Richard: easier to get to details, easier to maintain
Richard: needed for linking
... make it easier to publish to-do information
... and have people find it
Addison: need to assign shepherds and reviews
<r12a> CSS3-lists ishida
<r12a> CSS3-ruby ishida
<r12a> CSS3-text addison
<r12a> CSS3-text-decoration addison
<r12a> CSS3-writing-modes koji
<r12a> Encoding addison
<r12a> HTML5 addison
<r12a> Notifications norbert
<r12a> Polyglot felix
<r12a> UTR50 aharon
<r12a> xinclude felix
<r12a> Contacts addison
<r12a> CSS3-flexbox koji
<r12a> ITS-20 felix
<r12a> TURTLE addison
<r12a> UTR20 ishida
<r12a> WOFF oconner
<r12a> SysappAlarms norbert
Addison: new reviews: XInclude
... assigned XInclude tentatively to Felix
... not clear whether there's something to say about HTML+RDFa
Norbert: how are we going to track this?
Addison: will update review radar with shepherds
<aphillip> ACTION: addison: add shepherds list to review radar page [recorded in http://www.w3.org/2013/02/07-i18n-minutes.html#action01]
<trackbot> Created ACTION-181 - Add shepherds list to review radar page [on Addison Phillips - due 2013-02-14].
Richard: when adding items to
review radar, should send email to www-international
... also, when reviews pass without comments, move to last box
Richard: Norbert wrote draft and I added some tweaks:
<r12a> - Remove "This section is informative."
<r12a> - Replace the first Note with: "At the time of writing, enhancements are being discussed in the context of HTML that will change the approach to marking up directionality markup in HTML, especially to support content whose directionality needs to be isolated from the directionality of surrounding content. However, these enhancements are not finalized yet. This section therefore reflects directionality markup in HTML 4; enhancements in HTML5 will be reflected in a future revision."
<r12a> - In 8.5.2, add a Note to the description of LOCAL use: "HTML does not have the "lro" and "rlo" values for its dir attribute, so these values are not used for HTML documents. HTML uses an inline bdo element instead.
<r12a> - In the Note in 8.5.1, correct the value of the third bullet to "lro", and the description in the fourth bullet to "right-to-left override".
<r12a> - In Appendix A, add a normative reference to HTML 4.01.
<r12a> - Enhance example 46 with use of "rlo": Add to the description ", except that bdo elements with that attribute have right-to-left override content". Add a second rule: '<its:dirRule dir="rlo" selector="//bdo[@direction='rtlText']"/>'.
<r12a> also extend the example 45 to use bdo
<scribe> ACTION: Richard: send note with updated text for directionality to MLW-LT [recorded in http://www.w3.org/2013/02/07-i18n-minutes.html#action02]
<trackbot> Created ACTION-182 - Send note with updated text for directionality to MLW-LT [on Richard Ishida - due 2013-02-14].
Addison: tried to address discussion
on Unicode list
... it's time to fix charmod-norm
... current recommendations are not useful, but are misunderstood as W3C recommendations
... should put together shorter charmod-norm
<scribe> ACTION: Addison: write draft of new charmod-norm [recorded in http://www.w3.org/2013/02/07-i18n-minutes.html#action03]
<trackbot> Created ACTION-183 - Write draft of new charmod-norm [on Addison Phillips - due 2013-02-14].
Addison: sent some comments to CSS privately:
Addison: led to discussion,
especially about ruby and emphasis marks
... discussion within Amazon: emphasis marks should be in their own font to remain consistent
... emphasis marks should stay close to text, so may have to alter position around ruby
... other issue about underlining and white space
... don't know what correct handling is for all writing systems
<aphillip> chair: wg endorses?
Richard: mocked up some tests, features aren't implemented yet