This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3466 - Existing ruby markup
Summary: Existing ruby markup
Status: CLOSED FIXED
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS tagset (show other bugs)
Version: LastCall
Hardware: PC Windows XP
: P2 normal
Target Milestone: AfterLC
Assignee: Felix Sasaki
QA Contact: Felix Sasaki
URL:
Whiteboard:
Keywords: nonEditorialChange, proposalAccepted, reviewerSatisfied
Depends on:
Blocks:
 
Reported: 2006-07-14 19:58 UTC by Yves Savourel
Modified: 2006-10-13 05:59 UTC (History)
0 users

See Also:

Attachments

Description Yves Savourel 2006-07-14 19:58:24 UTC 
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.
Comment 1 Felix Sasaki 2006-07-24 17:17:00 UTC 
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 .
Comment 2 Felix Sasaki 2006-07-28 15:23:26 UTC 
Discussed at http://www.w3.org/2006/07/28-i18nits-minutes.html#item02 .
Action: working group to continue discussion.
Comment 3 Felix Sasaki 2006-08-01 00:54:57 UTC 
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
Comment 4 Felix Sasaki 2006-09-06 18:37:19 UTC 
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.
Comment 5 Felix Sasaki 2006-09-24 01:41:01 UTC 
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.
Comment 6 Felix Sasaki 2006-09-28 12:10:39 UTC 
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 .
Comment 7 Felix Sasaki 2006-10-13 05:58:00 UTC 
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 .
Comment 8 Felix Sasaki 2006-10-13 05:59:45 UTC 
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.