3466 2006-07-14 19:58:24 +0000 Existing ruby markup 2006-10-13 05:59:45 +0000 1 1 1 Unclassified ITS ITS tagset LastCall PC Windows XP CLOSED FIXED nonEditorialChange, proposalAccepted, reviewerSatisfied P2 normal AfterLC 1 ysavourel fsasaki fsasaki oldest_to_newest 10521 0 ysavourel 2006-07-14 19:58:24 +0000 Issue #35 of i18nCore comments: http://www.w3.org/International/reviews/0606-its/ Section 6.6.2: It's not abundantly clear from the text, but i think you mean to say, in the last para, that there are a set of global rules for associating markup that *conforms to Ruby-TR* with ruby concepts. Please make that clearer, and make it clearer that these global rules *do not apply* if the target markup is not identical to or a conformant subset of Ruby-TR. I'm also wondering whether XHTML 1.1 would need such global rules. If it does, it would be a good example to cite. 10735 1 fsasaki 2006-07-24 17:17:00 +0000 Discussed at http://www.w3.org/2006/07/21-i18nits-minutes.html#item02 . Action: working group to look at Felix mail at http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0120.html . 10869 2 fsasaki 2006-07-28 15:23:26 +0000 Discussed at http://www.w3.org/2006/07/28-i18nits-minutes.html#item02 . Action: working group to continue discussion. 10909 3 fsasaki 2006-08-01 00:54:57 +0000 Discussed at http://www.w3.org/2006/07/31-i18nits-minutes.html#item03 . ACTION: Felix to draft a text for the role of IRIs before and after ITS processing 11428 4 fsasaki 2006-09-06 18:37:19 +0000 resolution for IRI: we put we proposal at http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0125.html in a new section 3.5 , with the modifications described here, and change the wording of ref attributes to IRI resolution for ruby and XHTML 2.0: see http://lists.w3.org/Archives/Member/member-i18n-its/2006JulSep/0125.html . Action: editors to make the changes and go back to i18n core. 11988 5 fsasaki 2006-09-24 01:41:01 +0000 Discussed at http://www.w3.org/2006/09/20-i18nits-minutes.html#action01 . Changes in draft made, see http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0402.html. Action: WG to discuss. 12170 6 fsasaki 2006-09-28 12:10:39 +0000 Discussed at http://www.w3.org/2006/09/27-i18nits-minutes.html#action05 , Working Group agreed with the changes. Wait: reply to i18n core sent. See http://lists.w3.org/Archives/Public/www-i18n-comments/2006Sep/0088.html . 12413 7 fsasaki 2006-10-13 05:58:00 +0000 Closed. i18n core WG discussed the reply http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0427.html (see also http://lists.w3.org/Archives/Public/www-i18n-comments/2006Sep/0088.html) at http://localhost/2006/10/10-i18ncore-minutes.html#item02 . One request from i18n core: change reference from "RFC 3987" to "RFC 3987 or its successor". See also thread at http://lists.w3.org/Archives/Public/public-i18n-core/2006OctDec/0004.html . i18n ITS WG discussed i18n core request and agreed at http://www.w3.org/2006/10/11-i18nits-minutes.html#item02 . 12414 8 fsasaki 2006-10-13 05:59:45 +0000 Summary: The Working Group decided to accept the proposal and to clarify the relation of the specification to the W3C ruby specification, directionality as defined in CSS 2.1, and the usage of IRIs.