This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Issue #36 of i18nCore comments http://www.w3.org/International/reviews/0606-its/ It is very poorly explained what the difference is between this and the situation described in the last para of 6.6.2. How about: "Where legacy formats do no contain ruby markup conformant to [Ruby-TR], it is still possible to associate ruby text with a specified range of document content using the rubyRule element." Note also s/and there one wants/and where one wants/
Action: working group to discuss and reply.
Resolution: working group agreed with the proposal at http://www.w3.org/2006/07/26-i18nits-minutes.html#item07 Action: editors to make the change.
Comment has been implemented
Action: Felix to integrate the change.
Wait: response sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0327.html
Closed. Commenters satisfied see: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0362.html
Summary: The Working Group decided to accept the proposal and to clarify the application of legacy ruby.