This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Comment 11 of i18nCore comments: http://www.w3.org/International/reviews/0606-its/ Section 6.3.2: The locInfo element cannot contain directional markup for bidi languages, nor language markup, nor ruby markup, nor spans - all things which this document makes out to be important for well internationalized content. Can we not come up with a model that allows for at least those things? Please allow for span elements to at least include other span elements, so that language or directionality values can be applied to ranges of text within a span. FS: the "model" you describe would be IMO just to allow for its:span within <locInfo>, and to allow nesting of <its:span> within <its:span>.
Discussed at http://www.w3.org/2006/07/19-i18nits-minutes.html#item08 . Action: working group to look at proposal at http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0157.html .
Discussed at http://www.w3.org/2006/07/28-i18nits-minutes.html#item01 Action: Working group to think through processing implications about applying ITS markup to other ITS markup.
Discussed at http://www.w3.org/2006/07/31-i18nits-minutes.html#item02 . Action: Yves to try in his implementation of ITS markup about ITS markup in the case of locNote works Action: Felix to draft a text how to work-around the problem of arbitrary nesting of its:span in ruby
Action: Felix to draft a text how to work-around the problem of arbitrary nesting of its:span in ruby (due to 13 September)
Wait: response sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0304.html
Closed. Commenters satisfied see: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0362.html
Summary: The Working Group has accepted the proposal and clarified the model of the locInfo element (now called "locNote", see comment http://www.w3.org/Bugs/Public/show_bug.cgi?id=3460 ) as desired.