Last modification: Michel Suignard, Wed, February 06 2003
| # | source | origin | date | comment | answer |
|---|---|---|---|---|---|
| 1 | (Masayasu Ishikawa, on behalf of the HTML WG) mimasa@w3.org | www-style | 27-Nov |
http://lists.w3.org/Archives/Public/www-style/2002Nov/0151.html 2.2 What is ruby?, 2nd paragraph and note, clarify the use of 'group ruby' |
Document updated, as noted by Ishikawa-san, the term 'group-ruby' has been reversed during the evolution of the spec and now contradicts terms used in the XHTML Ruby Annotation spec. To avoid more confusion, it is probably better to completely remove the term 'group ruby' from this document. The sentence "This simple case is typically referred as a 'group' ruby" replaced by "In Japanese typography, this simple case is sometimes called "taigo ruby" (per-word ruby)" and 'group' is replace by 'simple annotation' in Note text. |
| 2 | 2.2 What is ruby?, third paragraph, explain term 'mono-ruby' | Document updated, term replaced by 'monoruby' and link to a glossary entry identical to the one in the Ruby XHTML module | |||
| 3 | 3.1 Ruby specific 'display' property values, replace 'HTML markup' by 'XHTML markup' | Document updated, the only reference to 'HTML markup' was found in 2.2, not 3.2, but is replaced as suggested. | |||
| 4 | 3.1 Ruby specific 'display' property values, remove clause about CSS3 user agents conformance | Document updated, clause removed | |||
| 5 | 3.2 Ruby box model, clarify usage of 'preceding' and 'following', replace usage of rtc, rbc elements by ruby text and ruby base | Document updated as suggested, this also includes the previous paragraph (after figure 3.2.2). Both paragraphs use the before/after terminology (with above/below annotation) and use the term 'ruby text(s)' and 'ruby bases'. A note is also added to clarify that visual order does not necessarily reflect logical order of elements | |||
| 6 | 3.2 Ruby box model, in the list of exceptions, 2nd bullet item, clarify 'This also means that a ruby element cannot be embedded into another ruby' | Document updated, restriction removed as not related to previous statement and uncalled for in the CSS3 ruby module. | |||
| 7 | 3.2 Ruby box model, last paragraph: "Finally, a conforming UA must not display the content of the rp element..." is outside the scope of this specification. | Document updated, agree in principle, especially concerning the 'must'. However, instead of removing the sentence entirely, it has been replaced by a note giving a styling hint for such an element. | |||
| 8 | 4.4 Ruby annotation spanning, this spec says too much about XHTML applications' behavior. | Document updated, 2nd sentence of 1st paragraph removed (This property allows non XHTML...) and 3rd sentence reworked to put less emphasis on XHTML and it becomes a separate note. Also removed the 1st paragraph after value description "Conforming CSS3 user agents may not implement...". | |||
| 9 | 4.4 Ruby annotation spanning, what happen if the attribute x is '0'? | Document updated, the Ruby markup spec is very explicit in forbidding the '0' value for the rbspan attribute. The simplest way to solve that in CSS is to say that '0' is equivalent to '1'. Also slightly updated the definition to say that the computed value of 'none' is 1 and that the computed value in general is a <length> value. | |||
| 10 | 4.4 Ruby annotation spanning, example is not correct, should add an explicit 'ruby-position' for each of the 'rtc' element | Document updated, added class 'before' and 'after' to the rtc rule with the appropriate 'ruby-position' | |||
| 11 | (Masayasu Ishikawa) mimasa@w3.org | www-style | Nov-27 | Typos in figure 3.2.2, 4.1.5, update reference to CSS3 text | Document updated, removed the '(see prose)' fragment. |