-
Notifications
You must be signed in to change notification settings - Fork 708
/
Copy pathOverview.src.html
2647 lines (2317 loc) · 111 KB
/
Overview.src.html
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 Text Module Level 3</title>
<link rel=contents href="#contents">
<!--<link rel=index href="#index">-->
<link rel="stylesheet" type="text/css" href="../default.css">
<style type="text/css">
.egbidiwsaA,.egbidiwsbB,.egbidiwsaB,.egbidiwsbC
{ white-space:pre;font-size:80%;font-family:monospace; vertical-align:2px; margin:1px }
.egbidiwsaA { background:lime;padding:2px; }
.egbidiwsbB { border:2px solid blue }
.egbidiwsaB { background:yellow;border:2px dotted white }
.egbidiwsbC { border:2px dotted red }
/* Start Letter-spacing Tutorial */
.ls-ex {
font-size: 200%;
margin-left: 1em;
margin-right: 1em;
}
.ls-fixed-width {
width: 10em;
}
.color-box { background: rgb(224, 203, 82); }
.bad { color: red; }
.good { color: green; }
/* End Letter-spacing Tutorial */
.char { border: 1px dotted gray; }
.quarter { font-size: 25%; }
tt[lang="ja"] { font-family: "MS Gothic", "Osaka", monospace }
div.figure table {
margin :auto;
}
.feedback {
background: #FFEECC;
border-color: orange;
}
.feedback:before {
content: "Info Needed";
color: #FF8800;
}
</style>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css">
<script src='http://test.csswg.org/harness/annotate.js#css-text-3_dev' type='text/javascript' defer></script>
</head>
<body>
<div class="head">
<!--logo-->
<h1>CSS Text Module Level 3</h1>
<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/[YEAR]/WD-css-text-3-[CDATE]/">http://www.w3.org/TR/[YEAR]/WD-css-text-3-[CDATE]/</a></dd>
<!--
<dd><a href="http://dev.w3.org/csswg/css3-text/">http://dev.w3.org/csswg/css3-text/</a>
-->
<dt>Latest version:</dt>
<dd><a href="http://www.w3.org/TR/css-text-3/">http://www.w3.org/TR/css-text-3/</a></dd>
<dt>Latest editor's draft:</dt>
<dd><a href="http://dev.w3.org/csswg/css-text-3/">http://dev.w3.org/csswg/css-text-3/</a></dd>
<dt>Previous version:</dt>
<dd><a
href="http://www.w3.org/TR/2012/WD-css3-text-20121113/">http://www.w3.org/TR/2012/WD-css3-text-20121113/</a>
<dt>Issues List:</dt>
<dd><a href="http://www.w3.org/Style/CSS/Tracker/products/10">http://www.w3.org/Style/CSS/Tracker/products/10</a>
<dt>Feedback:</dt>
<dd><a href="mailto:www-style@w3.org?subject=%5Bcss-text%5D%20feedback">www-style@w3.org</a>
with subject line “<kbd>[css-text] <var>… message topic …</var></kbd>”
(<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/">archives</a>)
<dt>Editors:</dt>
<dd><a href="http://fantasai.inkedblade.net/contact">Elika J. Etemad</a> (Mozilla)</dd>
<dd><a href="mailto:koji.a.ishii@mail.rakuten.com">Koji Ishii</a> (Rakuten, Inc.)</dd>
<dt>Test Suite:</dt>
<dd><a
href="http://test.csswg.org/suites/css3-text/nightly-unstable/">http://test.csswg.org/suites/css3-text/nightly-unstable/</a>
</dl>
<!--begin-copyright-->
<p>[Here will be included the file "../copyright.inc"]</p>
<!--end-copyright-->
<hr title="Separator for header">
</div>
<h2 class="no-num no-toc" id="abstract">Abstract</h2>
<p>This CSS3 module defines properties for text manipulation and
specifies their processing model. It covers line breaking, justification
and alignment, white space handling, and text
transformation.</p>
<h2 class="no-num no-toc" id="status">Status of This Document</h2>
<p><em>This section describes the status of this document at the time of
its publication. Other documents may supersede this document. A list of
current W3C publications and the latest revision of this technical report
can be found in the <a href="http://www.w3.org/TR/">W3C technical reports
index at http://www.w3.org/TR/.</a></em>
<p>Publication as a Last Call Working Draft does not imply endorsement by the W3C
Membership. This is a draft document and may be updated, replaced or
obsoleted by other documents at any time. It is inappropriate to cite this
document as other than work in progress.
<p>This CSS module has been produced as a combined effort of the <a
href="http://www.w3.org/International/Activity">W3C Internationalization Activity</a>,
and the <a href="http://www.w3.org/Style/Activity">Style Activity</a> and is maintained
by the <a href="http://www.w3.org/Style/CSS/members">CSS Working Group</a>. It also
includes contributions made by participants in the <a
href="http://www.w3.org/Style/XSL/Group/">XSL Working Group</a> (<a
href="http://cgi.w3.org/MemberAccess/AccessRequest">members
only</a>).
<p>This document was produced by a group operating under the <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
2004 W3C Patent Policy</a>. W3C maintains a <a
href="http://www.w3.org/2004/01/pp-impl/32061/status"
rel=disclosure>public list of any patent disclosures</a> made in
connection with the deliverables of the group; that page also includes
instructions for disclosing a patent. An individual who has actual
knowledge of a patent which the individual believes contains <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.</p>
<p>The following features are at risk and may be cut from the spec during
its CR period if there are no (correct) implementations:</p>
<ul>
<li>the ''full-width'' value of 'text-transform'
<li>the <length> values of the 'tab-size' property
<li>the ''start end'' value of 'text-align'
<li>the 'text-justify' property
<li>the percentage values of 'word-spacing'
<li>the 'hanging-punctuation' property
</ul>
<p>This specification is a <strong>Last Call Working Draft</strong>. All
persons are encouraged to review this document and <strong>send comments
to the <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a>
mailing list</strong> as described below. The <strong>deadline for
comments</strong> is <strong>7 November 2013</strong>.
<p><strong>Feedback on this draft should be posted to the
(<a href="http://lists.w3.org/Archives/Public/www-style/">archived</a>)
public mailing list <a href="mailto:www-style@w3.org">www-style@w3.org</a></strong>
(see <a href="http://www.w3.org/Mail/Request">instructions</a>) <strong>with
<kbd>[css-text]</kbd> in the subject line.</strong>
You are strongly encouraged to complain if you see something stupid
in this draft. The editors will do their best to respond to all feedback.</p>
<h2 class="no-num no-toc" id="contents">
Table of Contents</h2>
<!--toc-->
<h2 id="intro">
Introduction</h2>
<p>This module describes the typesetting controls of CSS;
that is, the features of CSS that control the translation of
source text to formatted, line-wrapped text.
Various CSS properties provide control over
<a href="#transforming">case transformation</a>,
<a href="#white-space">white space collapsing</a>,
<a href="#white-space">text wrapping</a>,
<a href="#line-breaking">line breaking rules</a>
and <a href="#hyphenation">hyphenation</a>,
<a href="#justification">alignment and justification</a>,
<a href="#spacing">spacing</a>,
and <a href="#edge-effects">indentation</a>.
<div class="note">
<p>Font selection is covered in <a href="http://www.w3.org/TR/css3-fonts/">CSS Fonts Level 3</a> [[CSS3-FONTS]].
<p>
<a name="decoration"></a>
<a name="text-decoration"></a>
<a name="line-decoration"></a>
<a name="text-decoration-line"></a>
<a name="text-decoration-color"></a>
<a name="text-decoration-style"></a>
<a name="text-decoration-skip"></a>
<a name="text-underline-position"></a>
<a name="emphasis-marks"></a>
<a name="text-emphasis-style"></a>
<a name="text-emphasis-color"></a>
<a name="text-emphasis"></a>
<a name="text-emphasis-position"></a>
<a name="text-shadow"></a>
Features for decorating text,
such as <a href="http://www.w3.org/TR/css-text-decor-3/#line-decoration">underlines</a>,
<a href="http://www.w3.org/TR/css-text-decor-3/#emphasis-marks">emphasis marks</a>,
and <a href="http://www.w3.org/TR/css-text-decor-3/#text-shadow-property">shadows</a>,
(previously part of this module)
are covered in
<a href="http://www.w3.org/TR/css-text-decor-3/">CSS Text Decoration Level 3</a> [[CSS3-TEXT-DECOR]].
<p><a href="http://www.w3.org/TR/css3-writing-modes/#text-direction">Bidirectional</a> and
<a href="http://www.w3.org/TR/css3-writing-modes/#vertical-intro">vertical</a> text
are addressed in
<a href="http://www.w3.org/TR/css3-writing-modes/">CSS Writing Modes Level 3</a> [[CSS3-WRITING-MODES]].
</div>
<h3 id="placement">
Module Interactions</h3>
<p>This module, together with [[CSS3-TEXT-DECOR]],
replaces and extends the text-level features defined in [[!CSS21]] chapter 16.
<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 [[CSS3VAL]], when combined with this module, expands the
definition of the <var><length></var> 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.
<h3 id="terms">
Terminology</h3>
<p id="grapheme-cluster">A <dfn>grapheme cluster</dfn> is what
a language user considers to be a character or a basic unit of the
script. The term is described in detail in the Unicode Technical
Report: Text Boundaries [[!UAX29]]. This specification uses the
<em>extended grapheme cluster</em> definition in [[!UAX29]] (not
the <em>legacy grapheme cluster</em> definition).
The UA may further tailor the definition as required by typographical tradition.
<div class="example">
<p>For example,
to properly letter-space the Thai word คำ (U+0E04 + U+0E33),
the U+0E33 needs to be decomposed into U+0E4D + U+0E32,
and then the extra letter-space inserted before the U+0E32: คํ า.
<p>A slightly more complex example is น้ำ (U+0E19 + U+0E49 + U+0E33).
In this case, normal Thai shaping will first decompose the U+0E33 into U+0E4D + U+0E32
and then swap the U+0E4D with the U+0E49, giving U+0E19 + U+0E4D + U+0E49 + U+0E32.
As before the extra letter-space is then inserted before the U+0E32: นํ้ า.
</div>
<p>Within this specification,
the ambiguous term <dfn>character</dfn> is used as a friendlier synonym
for <i>grapheme cluster</i>.
See <a href="http://www.w3.org/TR/css3-writing-modes/#character-properties">Characters and Properties</a>
for how to determine the Unicode properties of a character.
<p id="letter">A <dfn>letter</dfn> for the purpose of this specification
is a <i>character</i> belonging to one of the Letter or Number general
categories in Unicode. [[!UAX44]]
<p>The rendering characteristics of a <i>character</i> divided by an
element boundary is undefined: it may be rendered as belonging to
either side of the boundary, or as some approximation of belonging
to both. Authors are forewarned that dividing grapheme clusters by
element boundaries may give inconsistent or undesired results.
<p>The <dfn>content language</dfn> of an element is the (human) language
the element is declared to be in, according to the rules of the
<a href="http://www.w3.org/TR/CSS21/conform.html#doclanguage">document language</a>.
For example, the rules for determining the <i>content language</i> of an HTML
element use the <code>lang</code> attribute and are defined in [[HTML5]],
and the rules for determining the <i>content language</i> of an XML element use
the <code>xml:lang</code> attribute and are
<a href="http://www.w3.org/TR/REC-xml/#sec-lang-tag">defined</a> in [[XML10]].
Note that it is possible for the <i>content language</i> of an element
to be unknown.
<p>Other terminology and concepts used in this specification are defined
in [[!CSS21]] and [[!CSS3-WRITING-MODES]].
<h2 id="transforming">
Transforming Text</h2>
<h3 id="text-transform-property">
<a name="caps-prop"></a>
Case Transforms: the 'text-transform' property</h3>
<table class="propdef">
<tr>
<th>Name:</th>
<td><dfn>text-transform</dfn></td>
</tr>
<tr>
<th><a href="#values">Value</a>:
<td>none | capitalize | uppercase | lowercase | full-width
</td>
</tr>
<tr>
<th>Initial:</th>
<td>none</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>as specified</td>
</tr>
<tr>
<th>Animatable:
<td>no
<tr>
<th>Canonical order:
<td>N/A
</table>
<p>This property transforms text for styling purposes.
(It has no effect on the underlying content.)
Values have the following meanings:</p>
<dl>
<dt><dfn title="none!!text-transform">''none''</dfn></dt>
<dd>No effects.</dd>
<dt><dfn title="capitalize!!text-transform">''capitalize''</dfn></dt>
<dd>Puts the first <i>letter</i> of each word in titlecase; other characters
are unaffected.</dd>
<dt><dfn title="uppercase!!text-transform">''uppercase''</dfn></dt>
<dd>Puts all <i>letters</i> in uppercase.
<dt><dfn title="lowercase!!text-transform">''lowercase''</dfn></dt>
<dd>Puts all <i>letters</i> in lowercase.</dd>
<dt><dfn title="full-width!!text-transform">''full-width''</dfn></dt>
<dd>Puts all characters in fullwidth form.
If the character does not have a corresponding fullwidth form,
it is left as is.
This value is typically used to typeset Latin characters and digits
like ideographic characters.
</dl>
<p>The definition of “word“ used for ''capitalize'' is UA-dependent;
[[!UAX29]] is suggested (but not required) for determining such word
boundaries. Authors should not expect ''capitalize'' to follow
language-specific titlecasing conventions (such as skipping articles
in English).
<div class="example">
<p>The following example converts the ASCII characters
used in abbreviations in Japanese text to their fullwidth variants
so that they lay out and line break like ideographs:
<pre>abbr:lang(ja) { text-transform: full-width; }</pre>
</div>
<p>The case mapping rules for the character repertoire specified by the
Unicode Standard can be found on the Unicode Consortium Web site
[[!UNICODE]]. The UA must use the full case mappings for Unicode
characters, including any conditional casing rules, as defined in
Default Case Algorithm section. If (and only if) the <i>content language</i>
of the element is, according to the rules of the
<a href="http://www.w3.org/TR/CSS21/conform.html#doclanguage">document language</a>,
known,
then any appropriate language-specific rules must be applied as well.
These minimally include, but are not limited to, the language-specific
rules in Unicode's
<a href="http://www.unicode.org/Public/UNIDATA/SpecialCasing.txt">SpecialCasing.txt</a>.
<div class="example">
<p>For example, in Turkish there are two “i”s, one with
a dot—“İ” and “i”— and one
without—“I” and “ı”. Thus the usual
case mappings between “I” and “i” are
replaced with a different set of mappings to their respective
undotted/dotted counterparts, which do not exist in English. This
mapping must only take effect if the <i>content language</i> is Turkish
(or another Turkic language that uses Turkish casing rules);
in other languages, the usual mapping of “I”
and “i” is required. This rule is thus conditionally
defined in Unicode's SpecialCasing.txt file.
</div>
<p>The definition of fullwidth and halfwidth forms can be found on the
Unicode consortium web site at [[!UAX11]].
The mapping to fullwidth form is defined by taking code points with
the <code><wide></code> or the <code><narrow></code> tag
in their <code>Decomposition_Mapping</code> in [[!UAX44]].
For the <code><narrow></code> tag,
the mapping is from the code point to the decomposition (minus <code><narrow></code> tag),
and for the <code><wide></code> tag,
the mapping is from the decomposition (minus the <code><wide></code> tag)
back to the original code point.
<p>Text transformation happens after <a href="#white-space-rules">white
space processing</a>, which means that ''full-width'' only transforms
U+0020 spaces to U+3000 within preserved white spaces.
<p class="note">
A future level of CSS may introduce the ability to create custom mapping
tables for less common text transforms, such as by an ''@text-transform''
rule similar to ''@counter-style'' from [[CSS-COUNTER-STYLES-3]].
<h2 id="white-space-property"><a id="white-space-collapsing"></a><a id='text-wrap'></a>
White Space and Wrapping: the 'white-space' property</h2>
<table class="propdef">
<tr>
<th>Name:</th>
<td><dfn>white-space</dfn></td>
</tr>
<tr>
<th><a href="#values">Value</a>:
<td>normal | pre | nowrap | pre-wrap | pre-line</td>
</tr>
<tr>
<th>Initial:</th>
<td>normal
</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>as specified
</tr>
<tr>
<th>Animatable:
<td>no
<tr>
<th>Canonical order:
<td>N/A
</table>
<p>This property specifies two things:
<ul>
<li>whether and how <a href="#white-space-processing">white space</a> inside the element is collapsed
<li>whether lines may <i>wrap</i> at unforced <i>soft wrap opportunities</i>
</ul>
<p>Values have the following meanings, which must be interpreted
according to
the <a href="#white-space-rules">White Space Processing</a> and
<a href="#line-breaking">Line Breaking</a> rules:</p>
<dl>
<dt><dfn title="normal!!white-space">''normal''</dfn></dt>
<dd>This value directs user agents to collapse sequences of white space
into a single character (or <a href="#line-break-transform">in some
cases</a>, no character).
Lines may wrap at allowed <i>soft wrap opportunities</i>,
as determined by the line-breaking rules in effect,
in order to minimize inline-axis overflow.
<dt><dfn title="pre!!white-space">''pre''</dfn></dt>
<dd>This value prevents user agents from collapsing sequences of white space.
<i>Segment breaks</i> such as line feeds and carriage returns are preserved as <i>forced line breaks</i>.
Lines only break at <i>forced line breaks</i>;
content that does not fit within the block container overflows it.
<dt><dfn title="nowrap!!white-space">''nowrap''</dfn>
<dd>Like ''normal'', this value collapses white space;
but like ''pre'', it does not allow wrapping.
<dt><dfn title="pre-wrap!!white-space">''pre-wrap''</dfn></dt>
<dd>Like ''pre'', this value preserves white space;
but like ''normal'', it allows wrapping.
<dt><dfn title="pre-line!!white-space">''pre-line''</dfn></dt>
<dd>Like ''normal'', this value collapses consecutive spaces and allows wrapping,
but preserves <i>segment breaks</i> in the source as <i>forced line breaks</i>.
</dl>
<p>The following informative table summarizes the behavior of various
'white-space' values:</p>
<table class="data">
<colgroup class="header"></colgroup>
<colgroup span=3></colgroup>
<thead>
<tr>
<th></th>
<th>New Lines</th>
<th>Spaces and Tabs</th>
<th>Text Wrapping</th>
</tr>
</thead>
<tbody>
<tr>
<th>''normal''</th>
<td>Collapse</td>
<td>Collapse</td>
<td>Wrap</td>
</tr>
<tr>
<th>''pre''</th>
<td>Preserve</td>
<td>Preserve</td>
<td>No wrap</td>
</tr>
<tr>
<th>''nowrap''</th>
<td>Collapse</td>
<td>Collapse</td>
<td>No wrap</td>
</tr>
<tr>
<th>''pre-wrap''</th>
<td>Preserve</td>
<td>Preserve</td>
<td>Wrap</td>
</tr>
<tr>
<th>''pre-line''</th>
<td>Preserve</td>
<td>Collapse</td>
<td>Wrap</td>
</tbody>
</table>
<p>See <a href="#white-space-processing">White Space Processing Rules</a>
for details on how white space collapses. An informative summary of
collapsing (''normal'' and ''nowrap'') is presented below:
<ul>
<li>A sequence of segment breaks and other white space between two
Chinese, Japanese, or Yi characters collapses into nothing.
<li>A zero width space before or after a white space sequence
containing a segment break causes the entire sequence of white space
to collapse into a zero width space.
<li>Otherwise, consecutive white space collapses into a single space.
</ul>
<p>See <a href="#line-breaking">Line Breaking</a>
for details on wrapping behavior.
<h2 id="white-space-processing">
White Space Processing Details</h2>
<p>The source text of a document often contains formatting
that is not relevant to the final rendering: for example,
<a href="http://rhodesmill.org/brandon/2012/one-sentence-per-line/"
>breaking the source into segments</a> (lines) for ease of editing
or adding white space characters such as tabs and spaces to indent the source code.
CSS white space processing allows the author to control interpretation of such formatting,
to preserve or collapse it away when rendering the document.
White space processing in CSS interprets white space characters only for rendering:
it has no effect on the underlying document data.
<p>White space processing in CSS is controlled with the 'white-space' property.
<p id="segment-normalization">
CSS does not define document segmentation rules. Segments can be
separated by a particular newline seqence (such as a line feed or
CRLF pair), or delimited by some other mechanism, such as the SGML
<code>RECORD-START</code> and <code>RECORD-END</code> tokens.
For CSS processing, each document language–defined segment break,
CRLF sequence (U+000D U+000A), carriage return (U+000D), and line feed (U+000A)
in the text is treated as a <dfn>segment break</dfn>,
which is then interpreted for rendering as specified by the 'white-space' property.
<p class="note">Note that the document parser may have not only normalized
any segment breaks, but also collapsed other space characters or
otherwise processed white space according to markup rules. Because CSS
processing occurs <em>after</em> the parsing stage, it is not possible
to restore these characters for styling. Therefore, some of the
behavior specified below can be affected by these limitations and
may be user agent dependent.</p>
<p class="note">Note that anonymous inlines consisting entirely of
<i>collapsible</i> white space are removed from the rendering tree.
See [[CSS21]] section
<a href="http://www.w3.org/TR/CSS21/visuren.html#anonymous">9.2.2.1</a></p>
<p>Control characters (Unicode class Cc) other than tab (U+0009), line feed
(U+000A), and carriage return (U+000D)
are ignored for the purpose of rendering.
<h3 id="white-space-rules">
The White Space Processing Rules</h3>
<p>White space processing affects only spaces (U+0020), tabs (U+0009),
and <a href="#segment-normalization">segment breaks</a>.
<h4 id="white-space-phase-1">Phase I: Collapsing and Transformation</h4>
<p>For each inline (including anonymous inlines) within an inline
formatting context, white space characters are handled as follows,
ignoring bidi formatting characters as if they were not there:</p>
<ul>
<li id="collapse"><p>If 'white-space' is set to
''normal'', ''nowrap'', or ''pre-line'',
white space characters are considered <dfn>collapsible</dfn>
and are processed by performing the following steps:</p>
<ol>
<li>All spaces and tabs immediately preceding or following a segment
break are removed.</li>
<li>Segment breaks are transformed for
rendering according to the <a href="#line-break-transform">segment break transformation rules</a>.
</li>
<li>Every tab is converted to a space (U+0020).</li>
<li>Any space immediately following another collapsible space—even
one outside the boundary of the inline containing that space,
provided they are both within the same inline formatting
context—is collapsed to have zero advance width. (It is
invisible, but retains its <i>soft wrap opportunity</i>, if any.)</li>
</ol>
</li>
<li><p>If 'white-space' is set to ''pre-wrap'', any sequence of
spaces is treated as a sequence of non-breaking spaces. However,
a <i>soft wrap opportunity</i> exists at the end of the sequence.</p></li>
</ul>
<p>Then, the entire block is rendered. Inlines are laid out, taking bidi
reordering into account, and <i>wrapping</i> as specified by the
'white-space' property.</p>
<div class="example" id="egbidiwscollapse">
<p>The following example illustrates
the interaction of white-space collapsing and bidirectionality.
Consider the following markup fragment, taking special note of spaces
(with varied backgrounds and borders for emphasis and identification):
<pre><code><ltr>A<span class="egbidiwsaA"> </span><rtl><span class="egbidiwsbB"> </span>B<span class="egbidiwsaB"> </span></rtl><span class="egbidiwsbC"> </span>C</ltr></code></pre>
<p>where the <code><ltr></code> element represents a left-to-right embedding
and the <code><rtl></code> element represents a right-to-left embedding.
If the 'white-space' property is set to ''normal'',
the white-space processing model would result in the following:
<ul style="line-height:1.3">
<li>The space before the B (<span class="egbidiwsbB"> </span>)
would collapse with the space after the A (<span class="egbidiwsaA"> </span>).
<li>The space before the C (<span class="egbidiwsbC"> </span>)
would collapse with the space after the B (<span class="egbidiwsaB"> </span>).
</ul>
<p>This would leave two spaces,
one after the A in the left-to-right embedding level,
and one after the B in the right-to-left embedding level.
This is then ordered according to the Unicode bidirectional algorithm,
with the end result being:
<pre>A<span class="egbidiwsaA"> </span><span class="egbidiwsaB"> </span>BC</pre>
<p>Note that there are two spaces between A and B,
and none between B and C.
This is best avoided by putting spaces outside the element
instead of just inside the opening and closing tags and, where practical,
by relying on implicit bidirectionality instead of explicit embedding levels.
</div>
<h4 id="line-break-transform">
Segment Break Transformation Rules</h4>
<p>When 'white-space' is ''pre'', ''pre-wrap'', or ''pre-line'',
<i>segment breaks</i> are not <i>collapsible</i>
and are instead transformed into a preserved line feed (U+000A).
<p>For other values of 'white-space', <i>segment breaks</i> are <i>collapsible</i>,
and are either transformed into a space (U+0020) or removed
depending on the context before and after the break:</p>
<ul>
<li>If the character immediately before or immediately after the segment
break is the zero-width space character (U+200B), then the break
is removed, leaving behind the zero-width space.
<li>Otherwise, if the East Asian Width property [[!UAX11]] of both
the character before and after the line feed is F, W, or H (not A),
and neither side is Hangul, then the segment break is removed.
<li>Otherwise, the segment break is converted to a space (U+0020).
</ul>
<p class="note">Note that the white space processing rules have already
removed any tabs and spaces after the segment break before these checks
take place.</p>
<p class="feedback issue">Comments on how well this would work in practice would
be very much appreciated, particularly from people who work with
Thai and similar scripts.
Note that browser implementations do not currently follow these rules
(although IE does in some cases transform the break).</p>
<h4 id="white-space-phase-2">Phase II: Trimming and Positioning</h4>
<p>As each line is laid out,</p>
<ol>
<li>A sequence of collapsible spaces at the beginning of a line is
removed.
<li>Each tab is rendered as a horizontal shift
that lines up the start edge of the next glyph with the next <i>tab stop</i>.
<dfn title="tab stop">Tab stops</dfn> occur at points that are multiples of the tab size
from the block's starting content edge.
The tab size is given by the 'tab-size' property.
<li>A sequence of <i>collapsible</i> spaces at the end of a line is removed.
<li>If spaces or tabs at the end of a line are non-collapsible but
have 'white-space' set to 'pre-wrap' the UA may visually
collapse their character advance widths.
</ol>
<p>White space that was not removed or collapsed during the white space
processing steps is called <dfn>preserved</dfn> white space.</p>
<h3 id="tab-size-property">
Tab Character Size: the 'tab-size' property</h3>
<table class="propdef">
<tr>
<th>Name:</th>
<td><dfn>tab-size</dfn></td>
</tr>
<tr>
<th><a href="#values">Value</a>:
<td><integer> | <length></td>
</tr>
<tr>
<th>Initial:</th>
<td>8</td>
</tr>
<tr>
<th>Applies to:</th>
<td>block containers</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>the specified integer or length made absolute</td>
</tr>
<tr>
<th>Animatable:
<td>as <a href="http://www.w3.org/TR/css3-transitions/#animtype-length">length</a>
<tr>
<th>Canonical order:
<td>N/A
</table>
<p>This property determines the <i>tab size</i> used to render preserved tab characters (U+0009).
Integers represent the measure as multiples of the space character's advance width (U+0020).
Negative values are not allowed.
<h2 id="line-breaking">
Line Breaking and Word Boundaries</h2>
<p>When inline-level content is laid out into lines, it is broken across line boxes.
Such a break is called a <dfn>line break</dfn>.
When a line is broken due to explicit line-breaking controls,
or due to the start or end of a block,
it is a <dfn>forced line break</dfn>.
When a line is broken due to content <dfn title="wrapping|wrap">wrapping</dfn>
(i.e. when the UA creates unforced line breaks in order to fit the content within the measure),
it is a <dfn>soft wrap break</dfn>.
The process of breaking inline-level content into lines is called <dfn>line breaking</dfn>.
<p>Wrapping is only performed at an allowed break point, called a <dfn>soft wrap opportunity</dfn>.
<p>In most writing systems,
in the absence of hyphenation a <i>soft wrap opportunity</i> occurs only at word boundaries.
Many such systems use spaces or punctuation to explicitly separate words,
and <i>soft wrap opportunities</i> can be identified by these characters.
Scripts such as Thai, Lao, and Khmer, however,
do not use spaces or punctuation to separate words.
Although the zero width space (U+200B) can be used as an explicit word delimiter in these scripts,
this practice is not common.
As a result, a lexical resource is needed to correctly identify <i>soft wrap opportunities</i> in such texts.
<p>In several other writing systems, (including Chinese, Japanese, Yi, and sometimes also Korean)
a <i>soft wrap opportunity</i> is based on syllable boundaries, not word boundaries.
In these systems a line can break anywhere <em>except</em> between certain character combinations.
Additionally the level of strictness in these restrictions can vary with the typesetting style.</p>
<p>CSS does not fully define where <i>soft wrap opportunities</i> occur,
however some controls are provided to distinguish common variations.
<div class="note">
<p>Further information on line breaking conventions can be found in
[[JLREQ]] and [[JIS4051]] for Japanese,
[[ZHMARK]] for Chinese, and
in [[!UAX14]] for all scripts in Unicode.
<p class="feedback issue">Any guidance for appropriate references here would be
much appreciated.
</div>
<h3 id="line-break-details">
Line Breaking Details</h3>
<p>When determining <i>line breaks</i>:
<ul>
<li>Regardless of the 'white-space' value,
lines always break at each <i>preserved</i> forced break character:
for all values, line-breaking behavior defined for
the BK, CR, LF, CM, NL, and SG line breaking classes in [[!UAX14]]
must be honored.
<li>When 'white-space' allows wrapping,
line breaking behavior defined for the WJ, ZW, and GL line-breaking classes in [[!UAX14]]
must be honored.
<li>UAs that allow wrapping at punctuation other than spaces should prioritize breakpoints.
For example, if breaks after slashes are given a lower priority than spaces,
the sequence "check /etc" will never break between the '/' and the 'e'.
The UA may use the width of the containing block, the text's language,
and other factors in assigning priorities.
As long as care is taken to avoid such awkward breaks, allowing breaks at
appropriate punctuation other than spaces is recommended, as it results
in more even-looking margins, particularly in narrow measures.
<li>Out-of-flow elements do not introduce a <i>forced line break</i>
or <i>soft wrap opportunity</i> in the flow.
<li>The line breaking behavior of a replaced element or other atomic inline
is equivalent to that of the Object Replacement Character (U+FFFC).
<li>For <i>soft wrap opportunities</i> created by characters that disappear at the line break (e.g. U+0020 SPACE),
properties on the element containing that character control the line breaking at that opportunity.
For <i>soft wrap opportunities</i> defined by the boundary between two characters,
the properties on the element containing the boundary control breaking.
<!-- http://lists.w3.org/Archives/Public/www-style/2008Dec/0043.html -->
<li>For <i>soft wrap opportunities</i> before the first or after the last character of a box,
the break occurs immediately before/after the box (at its margin edge)
rather than breaking the box between its content edge and the content.
<li>For line breaking in/around <a href="http://www.w3.org/TR/css3-ruby/">ruby</a>,
the base text is considered part of the same inline formatting context as its surrounding content,
but the ruby text is not:
i.e. line breaking opportunities between the ruby element and its surrounding content
are determined as if the ruby base were inline and the ruby text were not there.
</ul>
<h3 id="line-break-property">
Breaking Rules for Punctuation: the 'line-break' property</h3>
<table class="propdef">
<tr>
<th>Name:</th>
<td><dfn>line-break</dfn></td>
</tr>
<tr>
<th><a href="#values">Value</a>:
<td>auto | loose | normal | strict</td>
</tr>
<tr>
<th>Initial:</th>
<td>auto</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>
<tr>
<th>Animatable:
<td>no
<tr>
<th>Canonical order:
<td>N/A
</table>
<p>This property specifies the strictness of line-breaking rules applied
within an element:
particularly how <i>wrapping</i> interacts with punctuation and symbols.
Values have the following meanings:</p>
<dl>
<dt><dfn title="auto!!line-break">''auto''</dfn></dt>
<dd>The UA determines the set of line-breaking restrictions to use,
and it may vary the restrictions based on the length of the line; e.g.,
use a less restrictive set of line-break rules for short lines.
<dt><dfn title="loose!!line-break">''loose''</dfn></dt>
<dd>Breaks text using the least restrictive set of line-breaking
rules. Typically used for short lines, such as in newspapers.</dd>
<dt><dfn title="normal!!line-break">''normal''</dfn></dt>
<dd>Breaks text using the most common set of line-breaking rules.</dd>
<dt><dfn title="strict!!line-break">''strict''</dfn></dt>
<dd>Breaks text using the most stringent set of line-breaking
rules.</dd>
</dl>
<p class="feedback issue">
The rules here are following guidelines from <a href="http://www.w3.org/TR/klreq/#line-break">KLREQ</a> for Korean,
which don't allow the Chinese/Japanese-specific breaks.
However, the resulting behavior could use some review and feedback to make sure they are correct,
particularly when “word basis” breaking is used (''word-break: keep-all'') in Korean.
<p>CSS distinguishes between three levels of strictness in the rules for
text wrapping.
The precise set of rules in effect for each level is up to the UA
and should follow language conventions.
However, this specification does require that:</p>
<ul>
<li>Following breaks be forbidden in ''strict'' line breaking and
allowed in ''normal'' and ''loose'':
<ul>
<li>breaks before Japanese small kana or the Katakana-Hiragana prolonged sound mark:
i.e. characters with the Unicode Line Break property <code>CJ</code>.
(See <a href="http://www.unicode.org/Public/UNIDATA/LineBreak.txt">LineBreak.txt</a> in [[!UNICODE]].)
</ul>
If the <i>content language</i> is Chinese or Japanese,
then additionally allow (but otherwise forbid) for ''normal'' and ''loose'':
<ul>
<li>breaks before hyphens:<br>
‐ U+2010, – U+2013, 〜 U+301C,
゠ U+30A0
</ul>
<li>Following breaks be forbidden in ''normal'' and ''strict'' line
breaking and allowed in ''loose'':
<ul>
<li>breaks before iteration marks:<br>
々 U+3005, 〻 U+303B, ゝ U+309D,
ゞ U+309E, ヽ U+30FD, ヾ U+30FE
<li>breaks between inseparable characters
such as ‥ U+2025, … U+2026
i.e. characters with the Unicode Line Break property <code>IN</code>.
(See <a href="http://www.unicode.org/Public/UNIDATA/LineBreak.txt">LineBreak.txt</a> in [[!UNICODE]].)
</ul>
If the <i>content language</i> is Chinese or Japanese,
then additionally allow (but otherwise forbid) for ''loose'':
<ul>
<li>breaks before certain centered punctuation marks:<br>
: U+003A, ; U+003B, ・ U+30FB,
： U+FF1A, ； U+FF1B, ･ U+FF65,
! U+0021, ? U+003F, ‼ U+203C,
⁇ U+2047, ⁈ U+2048, ⁉ U+2049,
！ U+FF01, ？ U+FF1F
<li>breaks before suffixes:<br>
% U+0025, ¢ U+00A2, ° U+00B0,
‰ U+2030, ′ U+2032, ″ U+2033,
℃ U+2103, ％ U+FF05, ￠ U+FFE0
<li>breaks after prefixes:<br>
№ U+2116
and all currency symbols (Unicode general category Sc) other than
¢ U+00A2 and ￠ U+FFE0
</ul>
</ul>
<p class="note">In the recommended list above, no distinction is made among the levels of
strictness in non-CJK text: only CJK codepoints are affected, unless
the text is marked as Chinese or Japanese, in which case some additional
common codepoints are affected. However a future level of CSS may add
behaviors affecting non-CJK text.
<p class="note">The CSSWG recognizes that in a future edition of the
specification finer control over line breaking may be necessary to
satisfy high-end publishing requirements.