1.1 --- a/css-ruby/Overview.src.html Mon Jun 24 14:42:20 2013 -0700 1.2 +++ b/css-ruby/Overview.src.html Mon Jun 24 17:43:42 2013 -0700 1.3 @@ -5,6 +5,8 @@ 1.4 line breaking 1.5 bidi 1.6 1.7 +Redo all examples with consistent font. (M+ 2p?) 1.8 + 1.9 --> 1.10 1.11 <!DOCTYPE html> 1.12 @@ -381,6 +383,46 @@ 1.13 1.14 <p class="issue">This shouldn't belong in Level 1. But HTML5 allows it, so we have to handle it. Yay HTML5. 1.15 1.16 +<h3 id="autohide"> 1.17 +Autohiding Annotations</h3> 1.18 + 1.19 + <p>If a <i>ruby annotation</i> has the exact same content as its base, 1.20 + it is <dfn title="hidden ruby annotation | hidden annotation">hidden</dfn>. 1.21 + Hiding a <i>ruby annotation</i> does not affect annotation pairing 1.22 + or the block-axis positioning of boxes in other <i>levels</i>. 1.23 + However the <i>hidden annotation</i> is not visible, 1.24 + and it has no impact on layout 1.25 + other than to separate adjacent sequences of <i>ruby annotation boxes</i> within its level, 1.26 + as if they belonged to separate segments 1.27 + and the <i>hidden annotation</i>’s base were not a <i>ruby base</i> but an intervening inline. 1.28 + 1.29 + <div class="example"> 1.30 + <p>This is to allow correct inlined display of annotations 1.31 + for Japanese words that are a mix of kanji and hirangana. 1.32 + For example, the word <i>振り仮名</i> should be inlined as 1.33 + <p class="figure">振り仮名(ふりがな) 1.34 + <p>and therefore marked up as 1.35 + <pre> 1.36 +<!-- --><ruby> 1.37 +<!-- --> <rb>振</rb><rb>り</rb><rb>仮</rb><rb>名</rb> 1.38 +<!-- --> <rp>(</rp><rt>ふ</rt><rt>り</rt><rt>が</rt><rt>な</rt><rp>)</rp> 1.39 +<!-- --><ruby></pre> 1.40 + <p>However, when displayed as ruby, the “り” should be hidden 1.41 + <div class="figure"> 1.42 + <p><img src="images/furigana-separate.png" 1.43 + alt="Hiragana annotations for 振り仮名 appear, each above its base character."> 1.44 + <p class="caption">Hiragana ruby for 振り仮名 1.45 + </div> 1.46 + </div> 1.47 + 1.48 + <p class="note"> 1.49 + Future levels of CSS Ruby may add controls for this, 1.50 + however in this level it is always forced. 1.51 + 1.52 + <p>The content comparison for this auto-hiding behavior 1.53 + takes place prior to white space collapsing. 1.54 + <span class="issue">Is this easier? Or after collapsing is easier? We should do whatever is easier, as it really doesn't matter much which way to go. 1.55 + 1.56 <h3 id="white-space"> 1.57 White Space</h3> 1.58