@@ -1210,6 +1210,9 @@ Ruby Text Distribution: the 'ruby-align' property</h3>
1210
1210
Note that space distributed by 'ruby-align' is unrelated to, and independent of,
1211
1211
any space distributed due to justification.
1212
1212
1213
+ Note: It is the content within the boxes that is aligned in the excess space,
1214
+ not the boxes themselves.
1215
+
1213
1216
Values have the following meanings:
1214
1217
<dl dfn-for=ruby-align dfn-type=value>
1215
1218
<dt> <dfn>start</dfn> </dt>
@@ -1292,16 +1295,26 @@ Ruby Text Distribution: the 'ruby-align' property</h3>
1292
1295
The distribution of space can be further controlled via 'text-justify' . [[CSS-TEXT-3]]
1293
1296
</div>
1294
1297
1295
- Issue: Add a paragraph explaining how to distribute space in situations with [=spanning annotations=] .
1296
-
1297
- <!--
1298
- For a complex ruby with spanning elements, one additional consideration is
1299
- required. If the spanning element spans multiple 'rows' (other rbc or rtc
1300
- elements), and the ruby alignment requires space distribution among the
1301
- 'spanned' elements, a ratio must be determined among the 'columns' of spanned
1302
- elements. This ratio is computed by taking into consideration the widest
1303
- element within each column.
1304
- -->
1298
+ Content in [=ruby bases=] and [=ruby annotations=] ,
1299
+ except those that span due to ''ruby-merge: merge'' ,
1300
+ is aligned within its box based on the value of 'ruby-align' on that box.
1301
+ Content in [=merged annotations=]
1302
+ is aligned within the [=ruby annotation container=]
1303
+ based on the value of 'ruby-align' on the [=annotations container=] ,
1304
+ ignoring the value of 'ruby-align' on the individual [=ruby annotations=] .
1305
+
1306
+ Issue: What if a [=merged annotation=] causes the [=ruby segment=] to be wider?
1307
+ Does it cause each base to grow as if it were spanning them, as currently specified?
1308
+ This does not allow e.g. centering the text in a multi-base base container
1309
+ when its merged annotation is longer.
1310
+ Instead, maybe we should allow ruby-merge to apply to base containers as well,
1311
+ but this would require us either to allow a single base to span multiple annotations
1312
+ (if the base is merged but some annotation levels are not),
1313
+ or to require that if the base is merged, then all annotation levels must be merged as well.
1314
+
1315
+ The way content is aligned when 'ruby-merge' is ''ruby-merge/auto'' is up to the User Agent,
1316
+ but must be identical to that of ''ruby-merge: separate''
1317
+ when all annotations fit over their respective bases.
1305
1318
1306
1319
<h3 id="ruby-text-decoration">
1307
1320
Ruby Text Decoration</h3>
0 commit comments