See also: IRC log
next steps on time zone document
review review radar
(and pipeline document)
send comments to the archives
action 21 in progress
richard: watch out for the multilingual web workshop
felix: mini-report on markup
... attended last week
... gave report on JLReq
... they liked it a lot, in things like XSL-FO and also ePub and technologies applied in ePub like CSS3
... some good feedback
<fsasaki> here is the link about the event: http://www.markupforum.de/
kennyluck: launched chinese
interest group (html5)
... defined broadly
... want to do something similar to JLReq
<kennyluck> homepage: http://www.w3.org/html/ig/zh/
richard: there may be a workshop
in Tokyo related to JLReq later in the year
... if Chinese "CLReq" interest, may want to talk to those folks and/or possibly
... adapt the JLReq doc for specific Chinese needs
... LISA (localization industry standards org) gave up ghost
... they have shutdown, possibly temporarily, but if so they will likely reemerge in a different form
richard: changes to
... before we only put last calls here
... but started putting anything that needs review here
... so public can see
... same goes for WD reviews such as CSS materials
<kennyluck> Addison: Got serveral feedbacks. Not yet incorporated
<kennyluck> ... next step: clean that up. Bring that to the WG and advance it to a note.
<kennyluck> Richard: Who's gonna convert that into the Note format?
<scribe> ACTION: richard: send addison tools for conversion to HTML [recorded in http://www.w3.org/2011/03/09-i18n-minutes.html#action01]
<trackbot> Created ACTION-24 - Send addison tools for conversion to HTML [on Richard Ishida - due 2011-03-16].
<scribe> ACTION: addison: finish edits and convert time zones document to HTL [recorded in http://www.w3.org/2011/03/09-i18n-minutes.html#action02]
<trackbot> Created ACTION-25 - Finish edits and convert time zones document to HTML [on Addison Phillips - due 2011-03-16].
<kennyluck> ACTION-25 due this month
<trackbot> ACTION-25 Finish edits and convert time zones document to HTL due date now this month
1) In section 2, the example should use upper case for RTL and lower case for Latin.
addison: also a few real examples in the document
2) Section 2, "User agents that support bidirectional text must apply the Unicode bidirectional algorithm to every sequence of inline boxes uninterrupted by a forced (bidi class B) line break or block boundary." should be "User agents that support bidirectional text must apply the Unicode bidirectional algorithm to every sequence of inline boxes uninterrupted by a forced (bidi class B) paragraph break or block boundary."
boundary." Rationale: the status of line breaks, in particular the <br> tag, re bidi isolation is blurry. Paragraphs are unequivocal bidi isolators.
aharon: also agree
... doesn't need to talk about <br>
... plenty of cases without that
3) In section 2.1, the sentence "The ‘direction’ property has no reordering in inline-level elements whose ‘unicode-bidi’ property's value is ‘normal’." is not clear to me.
richard: not embedding, not
... 'direction' property could be used for "other things" like embed
... or override
aharon: direction property has no effect on inline-level elements whose unicode-bidi property value is normal
4) Section 2.2, in the paragraph explaining "embed": there is no need for a semicolon after Unicode values U+202A and U+202B. Rationale: they are not entities.
5) Ibidem: the description does not explain what "embed" would mean for block-level elements.
matial: various cases
... should have complete description
7) In section 2.2, the order of the explanations for the values should rather be: normal, embed, isolate, plaintext, bidi-override, like in the prototype. The current order does not seem to correspond to anything.
richard: there is a double vertical line at the top of it
<kennyluck> embed plaintext
<kennyluck> isolate plaintext
Value: normal | [ [ embed | isolate ] || [ plaintext | bidi-override ] ]
8) In section 2.2, the text says: "Because the Unicode algorithm has a limit of 61 levels of embedding, care should be taken not to use ‘ unicode-bidi’ with a value other than ‘normal’ unless appropriate. In particular, a value of ‘inherit’ should be used with extreme caution." The value "inherit" has not been mentioned above as valid for the unicode-bidi property.
inherit is not explained anywhere
matial: ... explain it
<scribe> chair: any objections to making these wg comments?
<scribe> ACTION: richard: prepare to make tracker-based WG comment tables [recorded in http://www.w3.org/2011/03/09-i18n-minutes.html#action03]
<trackbot> Created ACTION-26 - Prepare to make tracker-based WG comment tables [on Richard Ishida - due 2011-03-16].
<scribe> ACTION: matial: work with richard to draft bidi comments on writing-mode [recorded in http://www.w3.org/2011/03/09-i18n-minutes.html#action04]
<trackbot> Sorry, couldn't find user - matial
<scribe> ACTION: richard: work with matial to draft bidi comments on writing-mode [recorded in http://www.w3.org/2011/03/09-i18n-minutes.html#action05]
<trackbot> Created ACTION-27 - Work with matial to draft bidi comments on writing-mode [on Richard Ishida - due 2011-03-16].
<David> unmute me
david: optimal slot seems to be 1500 UTC Wednesday
<scribe> ACTION: addison: change time of teleconference to 1500 UTC [recorded in http://www.w3.org/2011/03/09-i18n-minutes.html#action06]
<trackbot> Created ACTION-28 - Change time of teleconference to 1500 UTC [on Addison Phillips - due 2011-03-16].
next week: USA callers will be an hour later
scribe: and the rest of the world changes over time
(if they change at all)
... I think Leif's note is completely irrelevant
here's the note:
Whenever the http-equiv="content-language" attribute on the <meta> element specifies the language of the root element, then it is required to specify the language mapping of the root element. According to Content language state in [HTML5], the http-equiv="content-language" attribute on the <meta> element specifices the language of the root element whenever its content attribute contains no more and no less than exactly one language tag.
richard: should be the
intersection of xml and html
... reopened bug and discussion
addison: I support your interpretation
richard: will go through
remaining comments and close the completed ones
... also closed some bidi comments
aharon: closed where?
richard: in our table