forked from w3c/csswg-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathOverview.src.html
More file actions
2774 lines (2427 loc) · 118 KB
/
Overview.src.html
File metadata and controls
2774 lines (2427 loc) · 118 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>CSS Writing Modes Module Level 3</title>
<link rel="stylesheet" type="text/css" href="default.css">
<style type="text/css">
object { vertical-align: middle; }
.sidebar { float: right; background: #eee; border: solid gray; margin: 1em; }
.sidebar .figure { margin: 1em; }
.sidebar object { margin: 0 auto; display: block; }
.figurepair { display: table; margin: 1em auto; }
.figurepair .figure { display: table-cell; }
h2, .example { clear: both; }
.figure img,
.figure object,
.example img,
dd img { max-width: 100%; display: block; margin: 1em auto; }
div.figure table {
margin:auto;
}
</style>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WD.css">
</head>
<body>
<div class="head">
<!--logo-->
<h1>CSS Writing Modes Module Level 3</h1>
<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://dev.w3.org/csswg/css3-writing-modes/">http://dev.w3.org/csswg/css3-writing-modes/</a>
<!--
<dd><a href="http://www.w3.org/TR/[YEAR]/WD-[SHORTNAME]-[CDATE]">[VERSION]</a>
-->
<dt>Latest version:</dt>
<dd><a
href="http://www.w3.org/TR/css3-writing-modes/">http://www.w3.org/TR/css3-writing-modes/</a></dd>
<dt>Previous version:</dt>
<dd><a href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110201/">http://www.w3.org/TR/2011/WD-css3-writing-modes-20110201/</a></dd>
<dt>Editors:</dt>
<dd><a href="http://fantasai.inkedblade.net/contact">Elika J. Etemad</a> (Invited Expert)</dd>
<dd><a href="mailto:kojiishi@gluesoft.co.jp">Koji Ishii</a> (Invited Expert)</dd>
<dd><a href="mailto:murakami@antenna.co.jp">Shinyu Murakami</a> (<a href="http://www.antenna.co.jp/">Antenna House</a>)</dd>
<dt>Previous Editors:</dt>
<dd><a href="mailto:paulnel@microsoft.com">Paul Nelson</a> (<a href="http://www.microsoft.com/">Microsoft</a>)</dd>
<dd><a href="mailto:michelsu@microsoft.com">Michel Suignard</a> (<a href="http://www.microsoft.com/">Microsoft</a>)</dd>
</dl>
<!--copyright-->
<hr title="Separator for header">
</div>
<h2 class="no-num no-toc" id="abstract">
Abstract</h2>
<p>CSS3 Writing Modes defines CSS features to support for various international
writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left
(e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and
vertical (e.g. Asian scripts).</p>
<p>Inherently bottom-to-top scripts are not handled in this version. See
[[UTN22]] for an explanation of relevant issues.</p>
<h2 class="no-num no-toc" id="status">
Status of this document</h2>
<!--status-->
<p>The following features are at-risk and may be dropped during CR:
<ul>
<li>The ''use-glyph-orientation'' of 'text-orientation'
<li>The ''ascii-digits'', ''digits'', ''alpha'', ''latin'', ''alphanumeric'',
''compress'', ''no-compress'', and ''use-glyphs'' values of 'text-combine-horizontal'.
</ul>
<h2 class="no-num no-toc" id="Contents">
Table of Contents</h2>
<!--toc-->
<h2 id="text-flow">
Introduction to Writing Modes</h2>
<p>CSS3 Writing Modes defines CSS features to support for various international
writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left
(e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and
vertical (e.g. Asian scripts).</p>
<p>A <dfn>writing mode</dfn> in CSS is determined by the 'writing-mode',
'direction', and 'text-orientation' properties. It is defined primarily
in terms of its <i>inline base direction</i> and <i>block flow
direction</i>:
<div class="sidebar">
<div class="figure right">
<a href="diagrams/text-flow-vectors-tb.svg" type="image/svg+xml">
<img src="diagrams/text-flow-vectors-tb.png" class="landscape"
alt="Latin-based writing mode"></a>
<p class="caption">Latin-based writing mode
</div>
<div class="figure left">
<a href="diagrams/text-flow-vectors-lr-reverse.svg" type="image/svg+xml">
<img src="diagrams/text-flow-vectors-lr-reverse.png" class="landscape"
alt="Mongolian-based writing mode"></a>
<p class="caption">Mongolian-based writing mode
</div>
<div class="figure right">
<a href="diagrams/text-flow-vectors-tb.svg" type="image/svg+xml">
<img src="diagrams/text-flow-vectors-tb.png" class="landscape"
alt="Han-based writing mode"></a>
<a href="diagrams/text-flow-vectors-rl.svg" type="image/svg+xml">
<img src="diagrams/text-flow-vectors-rl.png" class="landscape"
alt="Han-based writing mode"></a>
<p class="caption">Han-based writing mode
</div>
</div>
<p>The <dfn>inline base direction</dfn> is the primary direction in which
content is ordered on a line and defines on which sides the "start"
and "end" of a line are. The 'direction' property specifies the
inline base direction of an element and, together with the 'unicode-bidi'
property and the inherent directionality of any text content, determines
the ordering of inline-level content within a line.
<p>The <dfn>block flow direction</dfn> is the direction in which
block-level boxes stack and the direction in which line boxes stack
within a block container. The 'writing-mode' property determines the
block flow direction.</p>
<p>A <dfn>horizontal writing mode</dfn> is one with horizontal lines of
text, i.e. a downward or upward block flow. A <dfn>vertical writing
mode</dfn> is one with vertical lines of text, i.e. a leftward or
rightward block flow.
<p class="note">These terms should not be confused with
<dfn>vertical block flow</dfn> (which is a downward or
upward block flow) and <dfn>horizontal block flow</dfn> (which is
leftward or rightward block flow). To avoid confusion, CSS
specifications avoid this latter set of terms.</p>
<p>Writing systems typically have one or two native writing modes. Some
examples are:
<ul>
<li>Latin-based systems are typically written using a left-to-right inline
direction with a downward (top-to-bottom) block flow direction.
<li>Arabic-based systems are typically written using a right-to-left
inline direction with a downward (top-to-bottom) block flow direction.
<li>Mongolian-based systems are typically written using a top-to-bottom
inline direction with a rightward (left-to-right) block flow direction.
<li>Han-based systems are commonly written using a left-to-right inline direction
with a downward (top-to-bottom) block flow direction, <strong>or</strong>
a top-to-bottom inline direction with a leftward (right-to-left) block
flow direction. Many magazines and newspapers will mix these two writing
modes on the same page.
</ul>
<p>The 'text-orientation' component of the writing mode determines the
<i>line orientation</i> and the <i>typesetting mode</i>, and controls
details of text layout such as the <i>glyph orientation</i>.
<p class="note">See Unicode Technical Note #22 [[UTN22]]
(<a href="http://fantasai.inkedblade.net/style/discuss/vertical-text/paper">HTML version</a>)
for a more in-depth introduction to writing modes and vertical text.
<h3 id="placement">
Module Interactions</h3>
<p>This module replaces and extends the 'unicode-bidi' and 'direction'
features defined in [[!CSS21]] sections 8.6 and 9.10.
<h3 id="conventions">
Document Conventions</h3>
<p>Conformance requirements are expressed with a combination of
descriptive assertions and RFC 2119 terminology. The key words “MUST”,
“MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
“RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
document are to be interpreted as described in RFC 2119.
However, for readability, these words do not appear in all uppercase
letters in this specification.
<p>All of the text of this specification is normative except sections
explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
<p>Examples in this specification are introduced with the words “for example”
or are set apart from the normative text with <code>class="example"</code>,
like this:
<div class="example">
<p>This is an example of an informative example.</p>
</div>
<p>Informative notes begin with the word “Note” and are set apart from the
normative text with <code>class="note"</code>, like this:
<p class="note">Note, this is an informative note.</p>
<h3 id="values">
Values</h3>
<p>This specification follows the
<a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
definition conventions</a> from [[!CSS21]]. Value types not defined in
this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
Other CSS modules may expand the definitions of these value types: for
example [[CSS3COLOR]], when combined with this module, expands the
definition of the <color> value type as used in this specification.</p>
<p>In addition to the property-specific values listed in their definitions,
all properties defined in this specification also accept the
<a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
keyword as their property value. For readability it has not been repeated
explicitly.
<h2 id="text-direction">
Inline Direction and Bidirectionality</h2>
<p>While the characters in most scripts are written from left to right,
certain scripts are written from right to left. In some documents,
in particular those written with the Arabic or Hebrew script, and in
some mixed-language contexts, text in a single (visually displayed)
block may appear with mixed directionality. This phenomenon is called
<span class="index-def" title="bidirectionality (bidi)"><dfn>bidirectionality</dfn></span>, or
"bidi" for short.</p>
<div class="figure">
<p><img src="diagrams/bidi.png"
alt="An example of bidirectional text is a Latin name in an Arabic
sentence. The sentence overall is typeset right-to-left, but
the letters in the Latin word in the middle are typeset
left-to-right.">
<p class="caption">Bidirectionality</p>
</div>
<p>The Unicode standard (<a href="http://www.unicode.org/reports/tr9/">Unicode Standard Annex #9</a>) defines a complex
algorithm for determining the proper ordering of bidirectional text. The
algorithm consists of an implicit part based on character properties,
as well as explicit controls for embeddings and overrides. CSS relies
on this algorithm to achieve proper bidirectional rendering.
The 'direction' and 'unicode-bidi' properties allow
authors to specify how the elements and attributes of a document
language map to this algorithm.</p>
<p>User agents that support bidirectional text must apply the Unicode
bidirectional algorithm to every sequence of inline-level boxes uninterrupted
by a forced (<a href="http://www.unicode.org/reports/tr9/#Bidirectional_Character_Types">bidi class B</a>)
paragraph break or block boundary. This sequence forms the <dfn>paragraph</dfn>
unit in the bidirectional algorithm.
<p>Except when the ''plaintext'' value of 'unicode-bidi' is in effect,
the paragraph embedding level is set according to the value of the
'direction' property of the paragraph's element rather than by the
heuristic given in steps P2 and P3 of the Unicode algorithm. The
paragraph's element is usually the containing block, but in the case
of a paragraph contained by bidi <a href="#isolate">isolation</a> it
is the isolating inline element instead.
<p>Because the base directionality of a text depends on the structure and
semantics of the document, the 'direction' and 'unicode-bidi' properties
should in most cases be
used only to map bidi information in the markup to its corresponding
CSS styles. If a document language provides markup features to control
bidi, authors and users should use those features and not specify CSS
rules to override them.</p>
<p>The HTML 4 specification ([[HTML401]], section 8.2) defines
bidirectionality behavior for HTML elements. The HTML 4 specification
also contains more information on bidirectionality issues.</p>
<p class="note">Because HTML UAs can turn off CSS styling, we advise HTML
authors to use the HTML 'dir' attribute and <bdo> element to
ensure correct bidirectional layout in the absence of a style sheet.</p>
<h3 id="direction">
Specifying Directionality: the 'direction' property</h3>
<table class="propdef">
<tbody>
<tr>
<th>Name:</th>
<td><dfn>direction</dfn></td>
</tr>
<tr>
<th>Value:</th>
<td>ltr | rtl </td>
</tr>
<tr>
<th>Initial:</th>
<td>ltr</td>
</tr>
<tr>
<th>Applies to:</th>
<td>all elements</td>
</tr>
<tr>
<th>Inherited:</th>
<td>yes</td>
</tr>
<tr>
<th>Percentages:</th>
<td>N/A</td>
</tr>
<tr>
<th>Media:</th>
<td>visual</td>
</tr>
<tr>
<th>Computed value:</th>
<td>specified value</td>
</tr>
</tbody>
</table>
<p>This property specifies the base directionality of text and elements
on a line, and the directionality of embeddings and overrides (see
'unicode-bidi') for the Unicode
bidirectional algorithm. In addition, it affects the ordering of <a
href="http://www.w3.org/TR/CSS21/tables.html">table</a> column layout,
the direction of horizontal <a href="http://www.w3.org/TR/CSS21/visufx.html#overflow">overflow</a>,
and the default alignment of text within a line, and other things
that depend on the base inline base direction.</p>
<p>Values for this property have the following meanings:</p>
<dl>
<dt><dfn>ltr</dfn></dt>
<dd>Left-to-right directionality.</dd>
<dt><dfn>rtl</dfn></dt>
<dd>Right-to-left directionality.</dd>
</dl>
<p class="note">The 'direction' property has no effect on bidi reordering
when specified on inline elements whose 'unicode-bidi' property's
value is ''normal''.</p>
<p>The value of the 'direction' property on the root element is also
propagated to the initial containing block and, together with the
'writing-mode' property, determines the document's principal writing
mode. (See <a href="#principal-writing-mode">below</a>.)
<p class="note">Note that the 'direction' property of the HTML BODY
element is <em>not</em> propagated to the viewport. That special
behavior only applies to the background and overflow properties.
<p class="note">The 'direction'
property, when specified for table column elements, is not inherited by
cells in the column since columns are not the ancestors of the cells in
the document tree. Thus, CSS cannot easily capture the "dir" attribute
inheritance rules described in [[HTML401]], section 11.3.2.1.
<h3 id="unicode-bidi">
Embeddings and Overrides: the 'unicode-bidi' property</h3>
<table class="propdef">
<tbody>
<tr>
<th>Name:</th>
<td><dfn>unicode-bidi</dfn></td>
</tr>
<tr>
<th>Value:</th>
<td>normal | embed | [ isolate || bidi-override ] | plaintext
</tr>
<tr>
<th>Initial:</th>
<td>normal</td>
</tr>
<tr>
<th>Applies to:</th>
<td>all elements, but see prose</td>
</tr>
<tr>
<th>Inherited:</th>
<td>no</td>
</tr>
<tr>
<th>Percentages:</th>
<td>N/A</td>
</tr>
<tr>
<th>Media:</th>
<td>visual</td>
</tr>
<tr>
<th>Computed value:</th>
<td>specified value</td>
</tr>
</tbody>
</table>
<p>Values for this property have the following meanings:</p>
<dl>
<dt><dfn>normal</dfn></dt>
<dd>The element does not open an additional level of embedding with
respect to the bidirectional algorithm. For inline elements,
implicit reordering works across element boundaries.</dd>
<dt><dfn>embed</dfn></dt>
<dd>If the element is inline, this value opens an additional level
of embedding with respect to the bidirectional algorithm.
The direction of this embedding level is given by the 'direction'
property. Inside the element, reordering is done implicitly. This
corresponds to adding a LRE (U+202A), for 'direction: ltr', or RLE
(U+202B), for 'direction: rtl', at the start of the element and a PDF
(U+202C) at the end of the element.
<span class="note">This value has no effect on elements that are
not inline.</span></dd>
<dt><dfn>isolate</dfn></dt>
<dd>For the purposes of the Unicode bidirectional algorithm, the
contents of the element are considered to be inside a separate,
independent paragraph with a base directionality given by the
element's 'direction' property, and for the purpose of bidi resolution
in its containing bidi paragraph (if any), the element itself is
treated as if it were an Object Replacement Character (U+FFFC).
(If the element is broken across multiple lines, then each box
of the element is treated as an Object Replacement Character.)</dd>
<dt><dfn>bidi-override</dfn></dt>
<dd>For inline elements this creates an override. For block-container
elements this creates an override for inline-level descendants not
within another block container element. This means that inside the
element, reordering is strictly in sequence according to the
'direction' property; the implicit part of the bidirectional algorithm
is ignored. This corresponds to adding a LRO (U+202D), for ''direction:
ltr'', or RLO (U+202E), for ''direction: rtl'', at the start of the
element and a PDF (U+202C) at the end of the element.</dd>
<dt><dfn>plaintext</dfn></dt>
<dd><p>For the purposes of the Unicode bidirectional algorithm, the
base directionality of each bidi paragraph for which the element
forms the containing block is determined not by the element's
computed 'direction' as usual, but by following the heuristic in
rules P2 and P3 of the Unicode bidirectional algorithm.
For inline elements, this value behaves as for ''isolate'',
except, as with block containers, the base directionality is
determined by following the Unicode heuristic instead of by using
the 'direction' value.
</dl>
<p>The final order of characters within in each bidi paragraph is the
same as if the bidi control codes had been added as described above,
markup had been stripped, and the resulting character sequence had
been passed to an implementation of the Unicode bidirectional
algorithm for plain text that produced the same line-breaks as the
styled text.
<p>In this process, replaced elements with 'display: inline' are treated
as neutral characters, unless their 'unicode-bidi' property has a
value other than 'normal', in which case they are treated as strong
characters in the 'direction' specified for the element.
All other atomic inline-level boxes are treated as neutral characters
always.</p>
<p>If an inline element is broken around a bidi paragraph
boundary (e.g. if split by a block or forced paragraph break), then
the bidi control codes corresponding to the end of the element are
added before the interruption and the codes corresponding to the
start of the element are added after it. (In other words, any embedding
levels or overrides started by the element are closed at the paragraph
break and reopened on the other side of it.)
<p>Because the Unicode algorithm has a limit of
<em title="According to unicode 3.0, chapter 3, section 12, definition BD2.
Specifically, page 58 here: http://www.unicode.org/unicode/uni2book/ch03.pdf">
61 levels</em> of embedding, care should be taken not to use <span
class="propinst-unicode-bidi">'unicode-bidi'</span> with a value other
than 'normal' unless appropriate. In particular, a value of 'inherit'
should be used with extreme caution. However, for elements that are,
in general, intended to be displayed as blocks, a setting of
'unicode-bidi: isolate' is preferred to keep the element together in
case display is changed to inline (see example below).</p>
<h3 id="bidi-example">
Example of Bidirectional Text</h3>
<p>The following example shows an XML document with bidirectional
text. It illustrates an important design principle: document language
designers should take bidi into account both in the language proper
(elements and attributes) and in any accompanying style sheets. The
style sheets should be designed so that bidi rules are separate from
other style rules, and such rules should not be overridden by other
style sheets so that the document language's bidi behavior is preserved.</p>
<div class="example">
<p>In this example, lowercase letters stand for inherently left-to-right
characters and uppercase letters represent inherently right-to-left
characters. The text stream is shown in logical backing store order.</p>
<pre class="xml-example"><code class="xml">
<HEBREW>
<PAR>HEBREW1 HEBREW2 english3 HEBREW4 HEBREW5</PAR>
<PAR>HEBREW6 <EMPH>HEBREW7</EMPH> HEBREW8</PAR>
</HEBREW>
<ENGLISH>
<PAR>english9 english10 english11 HEBREW12 HEBREW13</PAR>
<PAR>english14 english15 english16</PAR>
<PAR>english17 <HE-QUO>HEBREW18 english19 HEBREW20</HE-QUO></PAR>
</ENGLISH>
</code></pre>
<p>Since this is arbitrary XML, the style sheet is responsible for
setting the writing direction. This is the style sheet:</p>
<pre>
/* Rules for bidi */
HEBREW, HE-QUO {direction: rtl; unicode-bidi: embed;}
ENGLISH {direction: ltr; unicode-bidi: embed;}
/* Rules for presentation */
HEBREW, ENGLISH, PAR {display: block;}
EMPH {font-weight: bold;}
</pre>
<p>The HEBREW element is a block with a right-to-left base direction,
the ENGLISH element is a block with a left-to-right base
direction. The PARs are blocks that inherit the base direction from
their parents. Thus, the first two PARs are read starting at the top
right, the final three are read starting at the top left. Please note
that HEBREW and ENGLISH are chosen as element names for explicitness
only; in general, element names should convey structure without
reference to language.</p>
<p>The EMPH element is inline-level, and since its value for <span
class="propinst-unicode-bidi">'unicode-bidi'</span> is 'normal' (the
initial value), it has no effect on the ordering of the text. The
HE-QUO element, on the other hand, creates an embedding.</p>
<p>The formatting of this text might look like this if the line length
is long:</p>
<pre class="ascii-art">
5WERBEH 4WERBEH english3 2WERBEH 1WERBEH
8WERBEH <b>7WERBEH</b> 6WERBEH
english9 english10 english11 13WERBEH 12WERBEH
english14 english15 english16
english17 20WERBEH english19 18WERBEH
</pre>
<p>Note that the HE-QUO embedding causes HEBREW18 to be to the right
of english19.</p>
<p>If lines have to be broken, it might be more like this:</p>
<pre class="ascii-art">
2WERBEH 1WERBEH
-EH 4WERBEH english3
5WERB
-EH <b>7WERBEH</b> 6WERBEH
8WERB
english9 english10 en-
glish11 12WERBEH
13WERBEH
english14 english15
english16
english17 18WERBEH
20WERBEH english19
</pre>
<p>Because HEBREW18 must be read before english19, it is on the line
above english19. Just breaking the long line from the earlier
formatting would not have worked. Note also that the first syllable
from english19 might have fit on the previous line, but hyphenation of
left-to-right words in a right-to-left context, and vice versa, is
usually suppressed to avoid having to display a hyphen in the middle
of a line.</p>
</div><!-- example -->
<h3 id="bidi-box-model">
Box model for inline elements in bidirectional context</h3>
<p>Since bidi reordering can split apart and reorder text that is
logically contiguous, bidirectional text can cause an inline boxes
to be split and reordered within a line.
<p class="note">Note that in order to be able to flow inline boxes in a
uniform direction (either entirely left-to-right or entirely
right-to-left), anonymous inline boxes may have to be created.</p>
<!-- CSS2.1 8.6 -->
<p>For each line box, UAs must take the inline boxes generated for each
element and render the margins, borders and padding in visual order
(not logical order). The <i>start</i>-most box on the first line box
in which the element appears has the <i>start</i> edge's margin, border,
and padding; and the end-most box on the last line box in which the
element appears has the <i>end</i> edge's margin, border, and padding.
For example, in the ''horizontal-tb'' writing mode:
<ul>
<li>When the parent's 'direction' property is ''ltr'', the left-most
generated box of the first line box in which the element appears
has the left margin, left border and left padding, and the right-most
generated box of the last line box in which the element appears has
the right padding, right border and right margin.
<li>When the parent's 'direction' property is ''rtl'', the right-most
generated box of the first line box in which the element appears has
the right padding, right border and right margin, and the left-most
generated box of the last line box in which the element appears has
the left margin, left border and left padding.
</ul>
<p>Analogous rules hold for vertical writing modes.</p>
<p class="note">The 'box-decoration-break' property can override this
behavior to draw box decorations on both sides of each box. [[!CSS3BG]] </p>
<h2 id="vertical-intro">
Introduction to Vertical Text</h2>
<p><em>This subsection is non-normative.</em></p>
<p>In addition to extensions to CSS2.1’s support for bidirectional text,
this module introduces the rules and properties needed to support vertical
text layout in CSS.
<p>Unlike languages that use the Latin script which are primarily laid out
horizontally, Asian languages such as Chinese and Japanese can be laid out
vertically. The Japanese example below shows the same text laid out
horizontally and vertically. In the horizontal case, text is read
from left to right, top to bottom. For the vertical case, the text is
read top to bottom, right to left.
Indentation from the left edge in the left-to-right horizontal case
translates to indentation from the top edge in the top-to-bottom vertical
case.
<div class="figure">
<p><img src="vert-horiz-comparison.png"
alt="A comparison of horizontal and vertical Japanese shows that
although the lines rotate, the characters remain upright.
Some glyphs, however change: a period mark shifts from the
bottom left of its glyph box to the top right. Running
headers, however, may remain
laid out horizontally across the top of the page."></p>
<p class="caption">Comparison of vertical and horizontal Japanese: iBunko application (iOS)</p>
</div>
<p class="note">For Chinese and Japanese lines are ordered either right
to left or top to bottom, while for Mongolian and Manchu lines are
ordered left to right.</p>
<p>The change from horizontal to vertical writing can affect not just the
layout, but also the typesetting. For example, the position of a punctuation
mark within its spacing box can change from the horizontal to the
vertical case, and in some cases alternate glyphs are used.
<p>Vertical text that includes Latin script text or text from other scripts
normally displayed horizontally can display that text in a number of
ways. For example, Latin words can be rotated sideways, or each letter
can be oriented upright:
<div class="figure">
<p><img src="vert-latin-layouts.png"
alt="A dictionary definition for ヴィルス
might write the English word 'virus' rotated 90° clockwise,
but stack the letters of the initialisms 'RNA' and 'DNA' upright."></p>
<p class="caption">Examples of Latin in vertical Japanese: Daijirin Viewer 1.4 (iOS)</</p>
</div>
<p>In some special cases such as two-digit numbers in dates, text is fit
compactly into a single vertical character box:
<div class="figure" id="fig-mac">
<p><img src="vert-number-layouts.png"
alt="An excerpt from MacFan shows several possible vertical layouts
for numbers: the two-digit month and day are written as
horizontal-in-vertical blocks; the years are written with
each character upright; except in the English phrase
“for Mac 2011”, where the date is rotated to
match the rotated Latin."></p>
<p class="caption">Mac Fan, December 2010, p.49</p>
</div>
<p>Layouts often involve a mixture of vertical and horizontal elements:
<div class="figure">
<p><img src="vert-horiz-combination.png"
alt="Magazines often mix horizontal and vertical layout; for
example, using one orientation for the main article text
and a different one for sidebar or illustrative content."></p>
<p class="caption">Mixture of vertical and horizontal elements</p>
</div>
<p>Vertical text layouts also need to handle bidirectional text layout;
clockwise-rotated Arabic, for example, is laid out bottom-to-top.
<h3 id="writing-mode">
Block Flow Direction: the 'writing-mode' property</h3>
<table class="propdef">
<tbody>
<tr>
<th>Name:</th>
<td><dfn>writing-mode</dfn></td>
</tr>
<tr>
<th>Value:</th>
<td>horizontal-tb | vertical-rl | vertical-lr</td>
</tr>
<tr>
<th>Initial:</th>
<td>horizontal-tb</td>
</tr>
<tr>
<th>Applies to:</th>
<td>All elements except table row groups, table column groups, table rows, and table columns</td>
</tr>
<tr>
<th>Inherited:</th>
<td>yes</td>
</tr>
<tr>
<th>Percentages:</th>
<td>N/A</td>
</tr>
<tr>
<th>Media:</th>
<td>visual</td>
</tr>
<tr>
<th>Computed value:</th>
<td>specified value</td>
</tr>
</tbody>
</table>
<p>This property sets the block flow direction. Possible values:</p>
<dl>
<dt><dfn>horizontal-tb</dfn></dt>
<dd>Top-to-bottom block flow. The writing mode is horizontal.</dd>
<dt><dfn>vertical-rl</dfn></dt>
<dd>Right-to-left block flow. The writing mode is vertical.</dd>
<dt><dfn>vertical-lr</dfn></dt>
<dd>Left-to-right block flow. The writing mode is vertical.</dd>
</dl>
<p>The 'writing-mode' property determines the direction of block flow.
This determines the progression of block-level boxes in a block formatting
context; the progression of line boxes in a block container that contains
inlines; and the progression of rows in a table. By virtue of determining
the stacking direction of line boxes, the 'writing-mode' property also
determines whether line boxes and thus the writing mode is horizontal or
vertical.
<p>When set on the root element, the 'writing-mode' property together
with the 'direction' property determines the
<dfn id="principal-writing-mode">principal writing mode</dfn>
of the document. This writing mode is used, for example,
to determine the default page progression direction. (See [[CSS3PAGE]].)
The 'writing-mode' value of the root element is also propagated to
the initial containing block and sets the block flow direction of the
initial block formatting context.
<p class="note">Note that the 'writing-mode' property of the HTML BODY
element is <em>not</em> propagated to the viewport. That special
behavior only applies to the background and overflow properties.
<p>If an element has a different block flow direction than its containing
block:
<ul>
<li>If the element has a specified 'display' of ''inline'', its 'display'
computes to 'inline-block'. [[!CSS21]]
<li>If the element has a specified 'display' of ''run-in'', its 'display'
computes to 'block'. [[!CSS21]]
</ul>
<p>If such an element is a block container, then it establishes a new
block formatting context.
<p>The content of replaced elements do not rotate due to the writing mode:
images, for example, remain upright. However replaced content
involving text (such as MathML content or form elements) should match
the replaced element's writing mode and line orientation if the UA
supports such a vertical writing mode for the replaced content.
<div class="example">
<p>In the following example, two block elements (1 and 3) separated
by an image (2) are presented in various flow writing modes.</p>
<p>Here is a diagram of horizontal writing mode (<code>writing-mode: horizontal-tb</code>):</p>
<p><img alt="Diagram of horizontal layout: blocks 1, 2, and 3 are stacked top-to-bottom"
src="horizontal.png" width="219" height="300" ></p>
<p>Here is a diagram for the right-to-left vertical writing mode commonly
used in East Asia (<code>writing-mode: vertical-rl</code>):</p>
<p><img alt="Diagram of a right-to-left vertical layout: blocks 1, 2,
and 3 are arranged side by side from right to left"
src="vertical-rl.png" height="191" width="297" ></p>
<p>And finally, here is a diagram for the left-to-right vertical
writing mode used for Manchu and Mongolian (<code>writing-mode: vertical-lr</code>):</p>
<p><img alt="Diagram of left-to-right vertical layout: blocks 1, 2,
and 3 are arranged side by side from left to right"
src="vertical-lr.png" height="191" width="300" ></p>
</div>
<div class="example">
<p>In the following example, some form controls are rendered inside
a block with ''vertical-rl'' writing mode. The form controls are
rendered to match the writing mode.
<pre>
<!-- --><style>
<!-- --> form { writing-mode: vertical-rl; }
<!-- --></style>
<!-- -->...
<!-- --><form>
<!-- --><p><label>姓名　<input value="艾俐俐"></label>
<!-- --><p><label>语文　<select><option>English
<!-- --> <option>français
<!-- --> <option>فارسی
<!-- --> <option>中文
<!-- --> <option>日本语</select></label>
<!-- --></form></pre>
<p><img alt="Screenshot of vertical layout: the input element is
laid lengthwise from top to bottom and its contents
rendered in a vertical typographic mode, matching the
labels outside it. The drop-down selection control
after it slides out to the side (towards the after
edge of the block) rather than downward as it would
in horizontal writing modes."
src="vertical-form.png"></p>
</div>
<div class="example">
<p>In this example, 'writing-mode' sets the list markers upright
using the ''::marker'' pseudo-element. Vertical alignment ensures
that longer numbers will still align with the right of the first
line of text. [[CSS3LIST]]
<pre>::marker { writing-mode: horizontal-tb;
<!-- --> vertical-align: text-top;
<!-- --> color: blue; }</pre>
<div class="figure">
<p><img alt="Diagram showing list markers of '1.', '2.', '3.' sitting
upright atop sideways vertical Latin list item text."
class="example" src="vertical-horizontal-list-markers.png">
<p class="caption">Example of horizontal list markers in a vertical list</p>
</div>
</div>
<h4 id="svg-writing-mode">
SVG1.1 'writing-mode' Values</h4>
<p>SVG1.1 [[!SVG11]] defines some additional values: ''lr'',
''lr-tb'', ''rl'', ''rl-tb'', ''tb'', and ''tb-rl''.
<p>These values are <em>deprecated</em> in any context except SVG1 documents.
Implementations that wish to support these values in the context of CSS
must treat them as follows:
<table class="data">
<thead>
<tr><th>SVG1/Obsolete</th> <th>CSS</th></tr>
</thead>
<tbody>
<tr><td>''lr''</td> <td rowspan=3>''horizontal-tb''</td></tr>
<tr><td>''lr-tb''</td></tr>
<tr><td>''rl''</td></tr>
<tr><td>''tb''</td> <td rowspan=2>''vertical-rl''</td></tr>
<tr><td>''tb-rl''</td></tr>
</tbody>
</table>
<p class="note">The SVG1.1 values were also present in an older revision
of the CSS 'writing-mode' specification, which is obsoleted by this
specification. The additional ''tb-lr'' value of that revision is
replaced by ''vertical-lr''.
<p>In SVG1.1, these values set the <dfn>inline progression
direction</dfn>, in other words, the direction the current text position
advances each time a glyph is added. This is a geometric process that
happens <em>after</em> bidi reordering, and thus has no effect on the
interpretation of the 'direction' property (which is independent of
'writing-mode'). (See <a href="http://www.w3.org/TR/SVG/text.html#RelationshipWithBiDirectionality">Relationship
with bidirectionality</a>. [[!SVG11]])
<p class="note">There are varying interpretations
on whether this process causes "writing-mode: rl" to merely shift the
text string or reverse the order of all glyphs in the text.</p>
<h2 id="inline-alignment">
Inline-level Alignment</h2>
<p>When different kinds of inline-level content are placed together on a
line, the baselines of the content and the settings of the 'vertical-align'
property control how they are aligned in the transverse direction of the
line box. This section discusses what baselines are, how to find them,
and how they are used together with the 'vertical-align' property to
determine the alignment of inline-level content.
<h3 id="intro-baselines">
Introduction to Baselines</h3>
<p><em>This section is non-normative.</em></p>
<p>A <dfn>baseline</dfn> is a line along the <i>inline axis</i> of a line box
along which individual glyphs of text are aligned. Baselines guide the
design of glyphs in a font (for example, the bottom of most alphabetic
glyphs typically align with the alphabetic baseline), and they guide
the alignment of glyphs from different fonts or font sizes when typesetting.
<div class="figure">
[Picture of alphabetic text in two font sizes with the baseline and
emboxes indicated.]
</div>
<p>Different writing systems prefer different baseline tables.</p>
<div class="figure">
<p><img alt="Latin prefers the alphabetic baseline, on top of which most
letters rest, though some have descenders that dangle below it.
Indic scripts are sometimes typeset with a hanging baseline,
since their glyph shapes appear to be hanging from a
horizontal line.
Han-based systems, whose glyphs are designed to fill a square,
tend to align on their bottoms."
src="script-preferred-baselines.gif"></p>
<p class="caption">Preferred baselines in various writing systems</p>
</div>
<p>A well-constructed font contains a <dfn>baseline table</dfn>, which
indicates the position of one or more baselines within the font's
design coordinate space. (The design coordinate space is scaled with
the font size.)
<div class="figure">
<p><img alt=""
src="baselines.gif"></p>
<p class="caption">In a well-designed mixed-script font, the glyphs are
positioned in the coordinate space to harmonize with one another
when typeset together. The baseline table is then constructed to
match the shape of the glyphs, each baseline positioned to match
the glyphs from its preferred scripts.</p>
</div>
<p>The baseline table is a property of the font, and the positions
of the various baselines apply to all glyphs in the font.
<p>Different baseline tables can be provided for alignment in
horizontal and vertical text. UAs should use the vertical
tables in vertical typesetting modes and the horizontal tables
otherwise.
<h3 id="text-baselines">
Text Baselines</h3>
<p>In this specification, only the following baselines are considered:
<dl>
<dt>alphabetic</dt>
<dd>The <dfn>alphabetic baseline</dfn>, which typically aligns with the
bottom of uppercase Latin glyphs. In horizontal typographic mode,
this is the dominant baseline.
</dd>
<dt>central</dt>
<dd>The <dfn>central baseline</dfn>, which typically crosses the center
of the em box. In vertical typographic mode, this is the
dominant baseline. If the font is missing this baseline,
it is assumed to be halfway between the ascender (<i>over</i>)
and descender (<i>under</i>) edges of the em box.
</dd>
</dl>
<p class="note">A future CSS module will deal with baselines in more
detail and allow the choice of other dominant baselines and alignment
options.</p>
<h3 id="replaced-baselines">
Atomic Inline Baselines</h3>
<p>If an <a href="http://www.w3.org/TR/CSS21/visuren.html#inline-boxes">atomic
inline</a> (such as an inline-block, inline-table, or replaced inline element)
is not capable of providing its own baseline information, then the
UA synthesizes a baseline table thus:
<dl>
<dt>alphabetic</dt>
<dd>The alphabetic baseline is assumed to be at the <i>under</i>
margin edge.</dd>
<dt>central</dt>
<dd>The central baseline is assumed to be halfway between the
<i>under</i> and <i>over</i> margin edges of the box.
</dl>