-
Notifications
You must be signed in to change notification settings - Fork 708
/
Copy pathOverview.bs
6830 lines (6201 loc) · 287 KB
/
Overview.bs
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
<pre class='metadata'>
Title: CSS Text Module Level 3
Shortname: css-text
Level: 3
Status: ED
Work Status: Refining
Group: csswg
ED: https://drafts.csswg.org/css-text-3/
TR: https://www.w3.org/TR/css-text-3/
Previous version: https://www.w3.org/TR/2020/CR-css-text-3-20201222/
Previous version: https://www.w3.org/TR/2020/WD-css-text-3-20201119/
Previous version: https://www.w3.org/TR/2020/WD-css-text-3-20200429/
Previous version: https://www.w3.org/TR/2019/WD-css-text-3-20191113/
Previous Version: https://www.w3.org/TR/2018/WD-css-text-3-20181212/
Previous Version: https://www.w3.org/TR/2018/WD-css-text-3-20181206/
Previous Version: https://www.w3.org/TR/2018/WD-css-text-3-20180920/
Previous Version: https://www.w3.org/TR/2017/WD-css-text-3-20170822/
Previous Version: https://www.w3.org/TR/2013/WD-css-text-3-20131010/
Test Suite: http://test.csswg.org/suites/css3-text/nightly-unstable/
!Test Coverage Analysis: <a href="https://drafts.csswg.org/css-text-3/test-coverage">https://drafts.csswg.org/css-text-3/test-coverage</a>
Implementation Report: https://test.csswg.org/harness/results/css-text-3_dev/grouped/
Editor: Elika J. Etemad / fantasai, Invited Expert, http://fantasai.inkedblade.net/contact, w3cid 35400
Editor: Koji Ishii, Invited Expert, kojiishi@gluesoft.co.jp, w3cid 45369
Editor: Florian Rivoal, Invited Expert, https://florian.rivoal.net, w3cid 43241
Abstract: This CSS module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.
At Risk: the ''full-width'' value of 'text-transform'
At Risk: the ''full-size-kana'' value of 'text-transform'
At Risk: the <length> values of the 'tab-size' property
At Risk: the 'text-justify' property
At Risk: the 'hanging-punctuation' property
At Risk: Writing-system specific adjustments to line-breaking
At Risk: Trimming trailing Ogham space marks
Ignored Vars: letter-spacing
Status Text: This publication fully addresses the issues raised since the <a href="https://www.w3.org/TR/2013/WD-css-text-3-20131010/">October 2013 Last Call Working Draft</a>, which are documented in the <a href="https://drafts.csswg.org/css-text-3/issues-lc-2013">disposition of comments</a>.
WPT Path Prefix: /css/css-text/
</pre>
<pre class=link-defaults>
spec:css-display-3; type:property; text:display
spec:css-fonts-4; type:property; text:font-feature-settings
</pre>
<style type="text/css">
img { vertical-align: middle; }
span[lang] { font-size: 125%; line-height: 1; vertical-align: middle;}
/* Bidi & spaces example */
.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 }
.hyphens-ex {
border: thin solid black;
display: inline-block;
padding: 4pt;
}
/* 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;
}
.data .no { color: red; }
.data .ok { color: green; }
.data th em { display: block; font-size: smaller; font-weight: normal; font-style: italic; }
</style>
<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>Note: Font selection is covered in <a href="https://www.w3.org/TR/css-fonts-3/">CSS Fonts Level 3</a> [[CSS-FONTS-3]].
<p>
<span id="decoration"></span>
<span id="text-decoration"></span>
<span id="line-decoration"></span>
<span id="text-decoration-line"></span>
<span id="text-decoration-color"></span>
<span id="text-decoration-style"></span>
<span id="text-decoration-skip"></span>
<span id="text-underline-position"></span>
<span id="emphasis-marks"></span>
<span id="text-emphasis-style"></span>
<span id="text-emphasis-color"></span>
<span id="text-emphasis"></span>
<span id="text-emphasis-position"></span>
<span id="text-shadow"></span>
Features for decorating text,
such as <a href="https://www.w3.org/TR/css-text-decor-3/#line-decoration">underlines</a>,
<a href="https://www.w3.org/TR/css-text-decor-3/#emphasis-marks">emphasis marks</a>,
and <a href="https://www.w3.org/TR/css-text-decor-3/#text-shadow-property">shadows</a>,
(previously part of this module)
are covered in
<a href="https://www.w3.org/TR/css-text-decor-3/">CSS Text Decoration Level 3</a> [[CSS-TEXT-DECOR-3]].
<p><a href="https://www.w3.org/TR/css-writing-modes-3/#text-direction">Bidirectional</a> and
<a href="https://www.w3.org/TR/css-writing-modes-3/#vertical-intro">vertical</a> text
are addressed in
<a href="https://www.w3.org/TR/css-writing-modes-3/">CSS Writing Modes Level 3</a> [[CSS-WRITING-MODES-3]].
</div>
Further information about the typesetting requirements
of various languages and writing systems around the world
can be found in the <a href="https://www.w3.org/International/core/">Internationalization Working Group</a>’s
<a href="https://www.w3.org/TR/typography/">Typography Index</a>.
[[TYPOGRAPHY]]
<h3 id="placement">
Module Interactions</h3>
<p>This module, together with [[CSS-TEXT-DECOR-3]],
replaces and extends the text-level features defined in [[!CSS2]] chapter 16.
<p>In addition to the terms defined below,
other terminology and concepts used in this specification are defined
in [[!CSS2]] and [[!CSS-WRITING-MODES-3]].
<h3 id="values">
Value Definitions</h3>
This specification follows the <a href="https://www.w3.org/TR/CSS2/about.html#property-defs">CSS property definition conventions</a> from [[!CSS2]]
using the <a href="https://www.w3.org/TR/css-values-3/#value-defs">value definition syntax</a> from [[!CSS-VALUES-3]].
Value types not defined in this specification are defined in CSS Values & Units [[!CSS-VALUES-3]].
Combination with other CSS modules may expand the definitions of these value types.
In addition to the property-specific values listed in their definitions,
all properties defined in this specification
also accept the <a>CSS-wide keywords</a> as their property value.
For readability they have not been repeated explicitly.
<h3 id="languages">
Languages and Typesetting</h3>
<p class="advisement"><strong>
Authors should accurately language-tag their content for the best typographic behavior.
</strong>
Many typographic effects vary by linguistic context.
Language and writing system conventions can affect
line breaking, hyphenation, justification, glyph selection,
and many other typographic effects.
<strong>In CSS, language-specific typographic tailorings
are only applied when the <a>content language</a> is known (declared).</strong>
Therefore,
higher quality typography requires authors to communicate to the UA
the correct linguistic context of the text in the document.
The <dfn export>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="https://www.w3.org/TR/CSS2/conform.html#doclanguage">document language</a>.
Note that it is possible for the <a>content language</a> of an element
to be unknown--
e.g. untagged content,
or content in a <a>document language</a> that does not have a language-tagging facility
is considered to have an unknown <a>content language</a>.
Note: Authors can declare the [=content language=]
using the global <code>lang</code> attribute in HTML
or the universal <code>xml:lang</code> attribute in XML.
See the <a href="https://html.spec.whatwg.org/multipage/dom.html#language">rules
for determining the content language of an HTML element</a> in [[HTML]],
and the <a href="https://www.w3.org/TR/REC-xml/#sec-lang-tag">rules
for determining the content language of an XML element</a> in [[XML10]].
The [=content language=] an element is declared to be in
also identifies the specific written form of that language used in that element,
known as the <dfn export local-lt="writing system">content writing system</dfn>.
Depending on the [=document language=]'s facilities for identifying the [=content language=],
this information can be explicit or implied.
See the normative [[#script-tagging]].
Note: Some languages have more than one writing system tradition;
in other cases a language can be transliterated into a foreign writing system.
Authors should <a href="#script-tagging">subtag</a> such cases
so that the UA can adapt appropriately.
<!--
<div class=example>
For example, Korean (<code>ko</code>) can be written in
Hangul (<code>-Hang</code>),
Hanja (<code>-Hani</code>),
or a combination (<code>-Kore</code>).
Historical documents written solely in Hanja
do not use word spaces and
are formatted more like modern Chinese than modern Korean.
In other words, for typographic purposes <code>ko-Hani</code>
behaves more like <code>zh-Hant</code>
than <code>ko</code> (<code>ko-Kore</code>).
As another example Japanese (<code>ja</code>) is typically written
in a combination (<code>-Japn</code>) of Hiragana (<code>-Hira</code>),
Katakana (<code>-Kana</code>), and Kanji (<code>-Hani</code>).
However, it can also be ”romanized” into Latin (<code>-Latn</code>)
for special purposes like language-learning textbooks,
in which case it should be formatted more like English than Japanese.
As a third example contemporary Mongolian is written in two scripts:
Cyrillic (<code>-Cyrl</code>, officially used in Mongolia)
and Mongolian (<code>-Mong</code>, more common in Inner Mongolia, part of China).
These have very different formatting requirements,
with Cyrillic behaving similar to Latin and Greek,
and Mongolian deriving from both Arabic and Chinese writing conventions.
</div>
-->
<h3 id="characters">
Characters and Letters</h3>
<p>The basic unit of typesetting is the <dfn export>character</dfn>.
However, because writing systems are not always as simple as the basic English alphabet,
what a <a>character</a> actually is depends on the context in which the term is used.
For example, in Hangul (the Korean writing system),
each square representation of a syllable
(e.g. <span lang=ko-hang title="Hangul syllable HAN">한</span>=<span lang=ko-Latn>Han</span>)
can be considered a <a>character</a>.
However, the square symbol is really composed of multiple letters each representing a phoneme
(e.g. <span lang=ko-hang title="Hangul letter HIEUH">ㅎ</span>=<span lang=ko-Latn>h</span>,
<span lang=ko-hang title="Hangul letter HIEUH">ㅏ</span>=<span lang=ko-Latn>a</span>,
<span lang=ko-hang title="Hangul letter HIEUH">ㄴ</span>=<span lang=ko-Latn>n</span>)
and these also could each be considered a <a>character</a>.
<p>A basic unit of computer text encoding, for any given encoding,
is also called a <a>character</a>,
and depending on the encoding,
a single encoding <a>character</a> might correspond
to the entire pre-composed syllabic <a>character</a> (e.g. <span lang=ko-hang title="Hangul syllable HAN">한</span>),
to the individual phonemic <a>character</a> (e.g. <span lang=ko-hang title="Hangul letter HIEUH">ㅎ</span>),
or to smaller units such as
a base letterform (e.g. <span lang=ko-hang title="Hangul letter IEUNG">ㅇ</span>)
and any combining marks that vary it (e.g. extra strokes that represent aspiration).
<p>In turn, a single encoding <a>character</a> can be represented in the data stream as one or more bytes;
and in programming environments one byte is sometimes also called a <a>character</a>.
<p>Therefore the term <a>character</a> is fairly ambiguous where technical precision is required.
<p>For text layout, we will refer to the <dfn export lt="typographic character unit|typographic character">typographic character unit</dfn>
as the basic unit of text.
Even within the realm of text layout,
the relevant <a>character</a> unit depends on the operation.
For example, line-breaking and letter-spacing will segment
a sequence of Thai characters that include U+0E33 THAI CHARACTER SARA AM differently;
or the behaviour of a conjunct consonant in a script such as Devanagari
may depend on the font in use.
So the <a>typographic character</a> represents a unit of the writing system—<!--
-->such as a Latin alphabetic letter (including its diacritics),
Hangul syllable,
Chinese ideographic character,
Myanmar syllable cluster—<!--
-->that is indivisible with respect to a particular typographic operation
(line-breaking, first-letter effects, tracking, justification, vertical arrangement, etc.).
<wpt>
word-break/word-break-break-all-007.html
word-break/word-break-break-all-008.html
</wpt>
<a href="http://www.unicode.org/reports/tr29/">Unicode Standard Annex #29: Text Segmentation</a>
defines a unit called the <dfn>grapheme cluster</dfn>
which approximates the <a>typographic character</a>.
A UA must use the <em>extended grapheme cluster</em>
(not <em>legacy grapheme cluster</em>), as defined in [[!UAX29]],
as the basis for its <a>typographic character unit</a>.
However, the UA should tailor the definitions
as required by typographic tradition
since the default rules are not always appropriate or ideal--
and is expected to tailor them differently
depending on the operation as needed.
<wpt>
line-breaking/line-breaking-013.html
line-breaking/line-breaking-014.html
</wpt>
<p class="note">
Note: The rules for such tailorings are out of scope for CSS.
<!--
however W3C currently maintains a wiki page
where some known tailorings are collected.
-->
<div class="example">
The following are some examples of <a>typographic character unit</a> tailorings
required by standard typesetting practice:
<ul>
<li>
<p>In some scripts such as Myanmar or Devanagari,
the <a>typographic character unit</a> for both justification and line-breaking
is an entire syllable,
which can include more than one [[!UAX29]] <a>grapheme cluster</a>.
<li>
<p>In other scripts such as Thai or Lao,
even though for line-breaking the <a>typographic character</a>
matches Unicode’s default <a>grapheme clusters</a>,
for letter-spacing the relevant unit
is <em>less</em> than a [[!UAX29]] <a>grapheme cluster</a>,
and may require decomposition or other substitutions
before spacing can be inserted.
<p>For instance,
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: นํ้ า.
<li>
<p>Vertical typesetting [[!CSS-WRITING-MODES-3]] can also require tailoring.
For example, when typesetting ''text-orientation/upright'' text,
Tibetan tsek and shad marks are kept with the preceding grapheme cluster,
rather than treated as an independent <a>typographic character unit</a>.
</ul>
</div>
<p>A <dfn export>typographic letter unit</dfn> or <dfn>letter</dfn> for the purpose of this specification
is a <a>typographic character unit</a> belonging to one of the Letter or Number general
categories in Unicode. [[!UAX44]]
See <a href="#character-properties">Character Properties</a>
for how to determine the Unicode properties of a <a>typographic character unit</a>.
<p>The rendering characteristics of a <a>typographic character unit</a> divided
by an element boundary is undefined.
Ideally each component should be rendered
according to the formatting requirements of its respective element’s properties
while maintaining correct shaping and positioning
of the <a>typographic character unit</a> as a whole.
However, depending on the nature of the formatting differences between its parts
and the capabilities of the font technology in use,
this is not always possible.
Therefore such a <a>typographic character unit</a>
may be rendered as belonging to either side of the boundary,
or as some approximation of belonging to both.
Authors are forewarned that dividing <a>grapheme clusters</a>
or ligatures
by element boundaries may give inconsistent or undesired results.
<h3 id="text-encoding">
Text Processing</h3>
CSS is built on [[UNICODE]].
UAs that support Unicode must adhere to all normative requirements
of the Unicode Core Standard,
except where explicitly overridden by CSS.
UAs that use a different encoding are not explicitly supported by the CSS specifications;
they are, however, expected to fulfill the same text handling requirements
by assuming an appropriate mapping between that encoding and Unicode.
<wpt>
text-encoding/shaping-join-001.html
text-encoding/shaping-join-002.html
text-encoding/shaping-join-003.html
text-encoding/shaping-no-join-001.html
text-encoding/shaping-no-join-002.html
text-encoding/shaping-no-join-003.html
text-encoding/shaping-tatweel-001.html
text-encoding/shaping-tatweel-002.html
text-encoding/shaping-tatweel-003.html
shaping/shaping-arabic-diacritics-001.html
shaping/shaping-arabic-diacritics-002.html
white-space/full-width-leading-spaces-005.html
</wpt>
For the purpose of determining adjacency for text processing
(such as white space processing, text transformation, line-breaking, etc.),
and thus in general within this specification,
intervening [=inline box=] boundaries and [=out-of-flow=] elements
must be ignored.
With respect to text shaping, however, see [[#boundary-shaping]].
<wpt>
line-breaking/line-breaking-002.html
line-breaking/line-breaking-003.html
line-breaking/line-breaking-004.html
line-breaking/line-breaking-005.html
line-breaking/line-breaking-006.html
line-breaking/line-breaking-007.html
line-breaking/line-breaking-008.html
<!-- to be moved/removed together with the segment break transformation text
white-space/seg-break-transformation-018.html
white-space/seg-break-transformation-019.html
-->
word-break/word-break-min-content-002.html
word-break/word-break-min-content-003.html
word-break/word-break-min-content-004.html
word-break/word-break-min-content-005.html
overflow-wrap/overflow-wrap-anywhere-010.html
</wpt>
<wpt pathprefix="css/CSS2/text"/>
white-space-processing-048.xht
white-space-processing-049.xht
</wpt>
<h2 id="transforming">
Transforming Text</h2>
<h3 id="text-transform-property" oldids="text-transform,caps-prop">
Case Transforms: the 'text-transform' property</h3>
<pre class="propdef">
Name: text-transform
Value: none | [capitalize | uppercase | lowercase ] || full-width || full-size-kana
Initial: none
Applies to: text
Inherited: yes
Canonical order: n/a
Computed value: specified keyword
Animation type: discrete
</pre>
<wpt>
inheritance.html
parsing/text-transform-valid.html
parsing/text-transform-invalid.html
parsing/text-transform-computed.html
text-transform/text-transform-multiple-001.html
</wpt>
<wpt pathprefix="/css/CSS2/css1">
c545-txttrans-000.xht
</wpt>
<wpt pathprefix="/css/CSS2/text/">
text-transform-005.xht
text-transform-applies-to-001.xht
text-transform-applies-to-002.xht
text-transform-applies-to-003.xht
text-transform-applies-to-005.xht
text-transform-applies-to-006.xht
text-transform-applies-to-007.xht
text-transform-applies-to-008.xht
text-transform-applies-to-009.xht
text-transform-applies-to-010.xht
text-transform-applies-to-011.xht
text-transform-applies-to-012.xht
text-transform-applies-to-013.xht
text-transform-applies-to-014.xht
text-transform-applies-to-015.xht
</wpt>
<p>This property transforms text for styling purposes.
It has no effect on the underlying content,
and must not affect the content of a plain text copy & paste operation.
Note: The 'text-transform' property only affects the presentation layer;
correct casing for semantic purposes is expected to be represented
in the source document.
<wpt>
text-transform/text-transform-copy-paste-001-manual.html
</wpt>
<p>Values have the following meanings:
<dl dfn-for=text-transform dfn-type=value>
<dt><dfn>none</dfn></dt>
<dd>No effects.
<wpt>
text-transform/text-transform-none-001.xht
</wpt>
<wpt pathprefix="/css/CSS2/text/">
text-transform-004.xht
</wpt>
</dd>
<dt><dfn>capitalize</dfn></dt>
<dd>Puts the first <a>typographic letter unit</a> of each word, if lowercase, in titlecase;
other characters are unaffected.
<wpt>
text-transform/text-transform-capitalize-001.html
text-transform/text-transform-capitalize-003.html
text-transform/text-transform-capitalize-005.html
text-transform/text-transform-capitalize-007.html
text-transform/text-transform-capitalize-009.html
text-transform/text-transform-capitalize-010.html
text-transform/text-transform-capitalize-011.html
text-transform/text-transform-capitalize-014.html
text-transform/text-transform-capitalize-016.html
text-transform/text-transform-capitalize-018.html
text-transform/text-transform-capitalize-020.html
text-transform/text-transform-capitalize-022.html
text-transform/text-transform-capitalize-024.html
text-transform/text-transform-capitalize-026.html
text-transform/text-transform-capitalize-028.html
text-transform/text-transform-capitalize-030.html
text-transform/text-transform-capitalize-031.html
text-transform/text-transform-capitalize-032.xht
</wpt>
<wpt pathprefix="/css/CSS2/text/">
text-transform-001.xht
text-transform-cap-001.xht
text-transform-cap-002.xht
text-transform-cap-003.xht
</wpt>
</dd>
<dt><dfn>uppercase</dfn></dt>
<dd>Puts all <a>letters</a> in uppercase.
<wpt>
text-transform/text-transform-uppercase-101.xht
text-transform/text-transform-upperlower-001.html
text-transform/text-transform-upperlower-003.html
text-transform/text-transform-upperlower-005.html
text-transform/text-transform-upperlower-007.html
text-transform/text-transform-upperlower-009.html
text-transform/text-transform-upperlower-011.html
text-transform/text-transform-upperlower-015.html
text-transform/text-transform-upperlower-017.html
text-transform/text-transform-upperlower-019.html
text-transform/text-transform-upperlower-021.html
text-transform/text-transform-upperlower-023.html
text-transform/text-transform-upperlower-025.html
text-transform/text-transform-upperlower-027.html
text-transform/text-transform-upperlower-029.html
text-transform/text-transform-upperlower-031.html
text-transform/text-transform-upperlower-044.html
text-transform/text-transform-upperlower-101.html
text-transform/text-transform-upperlower-103.html
</wpt>
<wpt pathprefix="/css/CSS2/text/">
text-transform-003.xht
text-transform-bicameral-001.xht
text-transform-bicameral-003.xht
text-transform-bicameral-005.xht
text-transform-bicameral-007.xht
text-transform-bicameral-009.xht
text-transform-bicameral-011.xht
text-transform-bicameral-013.xht
text-transform-bicameral-015.xht
text-transform-bicameral-017.xht
text-transform-bicameral-019.xht
text-transform-bicameral-021.xht
text-transform-unicase-001.xht
text-transform-uppercase-001.xht
text-transform-uppercase-002.xht
</wpt>
<dt><dfn>lowercase</dfn></dt>
<dd>Puts all <a>letters</a> in lowercase.
<wpt>
text-transform/text-transform-lowercase-101.xht
text-transform/text-transform-lowercase-102.xht
text-transform/text-transform-upperlower-002.html
text-transform/text-transform-upperlower-004.html
text-transform/text-transform-upperlower-006.html
text-transform/text-transform-upperlower-008.html
text-transform/text-transform-upperlower-010.html
text-transform/text-transform-upperlower-012.html
text-transform/text-transform-upperlower-014.html
text-transform/text-transform-upperlower-016.html
text-transform/text-transform-upperlower-018.html
text-transform/text-transform-upperlower-020.html
text-transform/text-transform-upperlower-022.html
text-transform/text-transform-upperlower-024.html
text-transform/text-transform-upperlower-026.html
text-transform/text-transform-upperlower-028.html
text-transform/text-transform-upperlower-030.html
text-transform/text-transform-upperlower-102.html
text-transform/text-transform-upperlower-104.html
</wpt>
<wpt pathprefix="/css/CSS2/text/">
text-transform-002.xht
text-transform-bicameral-002.xht
text-transform-bicameral-004.xht
text-transform-bicameral-006.xht
text-transform-bicameral-008.xht
text-transform-bicameral-010.xht
text-transform-bicameral-012.xht
text-transform-bicameral-014.xht
text-transform-bicameral-016.xht
text-transform-bicameral-018.xht
text-transform-bicameral-020.xht
text-transform-bicameral-022.xht
text-transform-lowercase-001.xht
</wpt>
</dd>
<dt><dfn>full-width</dfn></dt>
<dd>Puts all <a>typographic character units</a> in fullwidth form.
If a character does not have a corresponding fullwidth form,
it is left as is.
This value is typically used to typeset Latin letters and digits
as if they were ideographic characters.
<wpt>
text-transform/text-transform-fullwidth-001.xht
text-transform/text-transform-fullwidth-002.xht
text-transform/text-transform-fullwidth-004.xht
text-transform/text-transform-fullwidth-005.xht
</wpt>
<dt><dfn>full-size-kana</dfn></dt>
<dd>Converts all [=small Kana=] characters to the equivalent [=full-size Kana=].
This value is typically used for ruby annotation text,
where authors may want all small Kana to be drawn as large Kana
to compensate for legibility issues at the small font sizes typically used in ruby.
<wpt>
text-transform/text-transform-full-size-kana-001.html
text-transform/text-transform-full-size-kana-002.html
text-transform/text-transform-full-size-kana-003.html
text-transform/text-transform-full-size-kana-004.html
text-transform/text-transform-full-size-kana-005.html
text-transform/text-transform-full-size-kana-006.html
text-transform/text-transform-full-size-kana-007.html
</wpt>
</dl>
<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>
Note: The purpose of 'text-transform' is
to allow for presentational casing transformations
without affecting the semantics of the document.
Note in particular that 'text-transform' casing operations are lossy,
and can distort the meaning of a text.
While accessiblity interfaces may wish to convey
the apparent casing of the rendered text to the user,
the transformed text cannot be relied on to accurately represent
the underlying meaning of the document.
<div class="example">
In this example,
the first line of text is capitalized as a visual effect.
<pre highlight=css>
section > p:first-of-type::first-line {
text-transform: uppercase;
}
</pre>
This effect cannot be written into the source document
because the position of the line break depends on layout.
But also, the capitalization is not reflecting a semantic distinction
and is not intended to affect the paragraph’s reading;
therefore it belongs in the presentation layer.
</div>
<div class="example">
In this example,
the [=ruby=] annotations,
which are half the size of the main paragraph text,
are transformed to use regular-size kana
in place of [=small kana=].
<pre highlight=css>
rt { font-size: 50%; text-transform: full-size-kana; }
:is(h1, h2, h3, h4) rt { text-transform: none; /* unset for large text*/ }
</pre>
Note that while this makes such letters easier to see at small type sizes,
the transformation distorts the text:
the reader needs to mentally substitute [=small kana=]
in the appropriate places--
not unlike reading a text in English
with all “s” characters substituted by “f”.
</div>
<h4 id="text-transform-mapping">
Mapping Rules</h4>
<p>For ''capitalize'', what constitutes a “word“ 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).
Out-of-flow elements and inline element boundaries
must not introduce a 'text-transform' word boundary
and must be ignored when determining such word boundaries.
<wpt>
text-transform/text-transform-capitalize-033.html
</wpt>
<p>
The UA must use the full case mappings for Unicode
characters, including any conditional casing rules, as defined in
Default Case Algorithm section of The Unicode Standard [[!UNICODE]].
If (and only if) the <a>content language</a>
of the element is, according to the rules of the
<a href="https://www.w3.org/TR/CSS2/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>.
<wpt>
writing-system/writing-system-text-transform-001.html
text-transform/text-transform-tailoring-001.html
text-transform/text-transform-tailoring-002.html
text-transform/text-transform-tailoring-002a.html
text-transform/text-transform-tailoring-003.html
text-transform/text-transform-tailoring-004.html
text-transform/text-transform-tailoring-005.html
text-transform/text-transform-upperlower-032.html
text-transform/text-transform-upperlower-033.html
text-transform/text-transform-upperlower-034.html
text-transform/text-transform-upperlower-035.html
text-transform/text-transform-upperlower-038.html
text-transform/text-transform-upperlower-039.html
text-transform/text-transform-upperlower-040.html
text-transform/text-transform-upperlower-041.html
text-transform/text-transform-upperlower-042.html
text-transform/text-transform-upperlower-043.html
</wpt>
<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 <a>content language</a> is Turkish
written in its modern Latin-based <a>writing system</a>
(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>
<wpt pathprefix="/css/CSS2/text/">
text-transform-bicameral-005.xht
text-transform-bicameral-006.xht
</wpt>
<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.
<wpt>
text-transform/text-transform-fullwidth-001.xht
text-transform/text-transform-fullwidth-002.xht
text-transform/text-transform-fullwidth-004.xht
text-transform/text-transform-fullwidth-005.xht
text-transform/text-transform-fullwidth-006.html
text-transform/text-transform-fullwidth-007.html
</wpt>
<p>The mappings for small Kana to full-size Kana are defined in [[#small-kana]].
<h4 id="text-transform-order">
Order of Operations</h4>
<p>When multiple values are specified and therefore multiple transformations need to be applied,
they are applied in the following order:
<ol>
<li>''capitalize'', ''uppercase'', and ''lowercase''
<li>''full-width''
<li>''full-size-kana''
</ol>
<wpt>
text-transform/text-transform-multiple-001.html
</wpt>
<p>Text transformation happens after [[#white-space-phase-1]]
but before [[#white-space-phase-2]].
This means that ''full-width'' only transforms
U+0020 spaces to U+3000 within <a>preserved</a> [=white space=].
<wpt>
text-transform/text-transform-fullwidth-006.html
text-transform/text-transform-fullwidth-007.html
text-transform/text-transform-fullwidth-008.html
text-transform/text-transform-fullwidth-009.html
</wpt>
<p class="note">
Note: As defined in <a href="#order">Text Processing Order of Operations</a>,
transforming text affects line-breaking and other formatting operations.
<h2 id="white-space-property" oldids="white-space-collapsing,text-wrap">
White Space and Wrapping: the 'white-space' property</h2>
<pre class="propdef">
Name: white-space
Value: normal | pre | nowrap | pre-wrap | break-spaces | pre-line
Initial: normal
Applies to: text
Inherited: yes
Canonical order: n/a
Computed value: specified keyword
Animation type: discrete
</pre>
<wpt>
inheritance.html
parsing/white-space-valid.html
parsing/white-space-invalid.html
parsing/white-space-computed.html
white-space/ws-break-spaces-applies-to-001.html
white-space/ws-break-spaces-applies-to-002.html
white-space/ws-break-spaces-applies-to-003.html
white-space/ws-break-spaces-applies-to-005.html
white-space/ws-break-spaces-applies-to-006.html
white-space/ws-break-spaces-applies-to-007.html
white-space/ws-break-spaces-applies-to-008.html
white-space/ws-break-spaces-applies-to-009.html
white-space/ws-break-spaces-applies-to-010.html
white-space/ws-break-spaces-applies-to-011.html
white-space/ws-break-spaces-applies-to-012.html
white-space/ws-break-spaces-applies-to-013.html
white-space/ws-break-spaces-applies-to-014.html
white-space/ws-break-spaces-applies-to-015.html
white-space/white-space-pre-031.html
white-space/white-space-pre-032.html
white-space/white-space-pre-034.html
white-space/white-space-pre-035.html
</wpt>
<wpt pathprefix="/css/CSS2/css1/">
c562-white-sp-000.xht
</wpt>
<wpt pathprefix="/css/CSS2/text/">
white-space-006.xht
white-space-007.xht
white-space-applies-to-001.xht
white-space-applies-to-002.xht
white-space-applies-to-002.xht
white-space-applies-to-003.xht
white-space-applies-to-005.xht
white-space-applies-to-006.xht
white-space-applies-to-007.xht
white-space-applies-to-008.xht
white-space-applies-to-009.xht
white-space-applies-to-010.xht
white-space-applies-to-011.xht
white-space-applies-to-012.xht
white-space-applies-to-013.xht
white-space-applies-to-014.xht
white-space-applies-to-015.xht
white-space-mixed-001.xht
white-space-mixed-002.xht
white-space-mixed-003.xht
white-space-mixed-004.xht
</wpt>
<p>This property specifies two things:
<ul>
<li>whether and how <a>white space</a> is collapsed
<li>whether lines may <a>wrap</a> at unforced <a>soft wrap opportunities</a>
</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 dfn-for=white-space dfn-type=value>
<dt><dfn>normal</dfn></dt>
<dd>This value directs user agents to collapse sequences of <a>white space</a>
into a single character (or <a href="#line-break-transform">in some
cases</a>, no character).
Lines may wrap at allowed <a>soft wrap opportunities</a>,
as determined by the line-breaking rules in effect,
in order to minimize inline-axis overflow.
<wpt>
white-space/white-space-normal-011.html
white-space/white-space-pre-031.html
white-space/white-space-wrap-after-nowrap-001.html
line-break/line-break-anywhere-and-white-space-004.html
line-break/line-break-anywhere-and-white-space-005.html
</wpt>
<wpt pathprefix="/css/CSS2/text/">
white-space-normal-001.xht
white-space-normal-002.xht
white-space-normal-003.xht
white-space-normal-004.xht
white-space-normal-005.xht
white-space-normal-006.xht
white-space-normal-007.xht
white-space-normal-008.xht
white-space-normal-009.xht
white-space-p-element-001.xht
</wpt>
<dt><dfn>pre</dfn></dt>
<dd>This value prevents user agents from collapsing sequences of <a>white space</a>.
<a>Segment breaks</a> such as line feeds
are preserved as <a>forced line breaks</a>.
Lines only break at <a>forced line breaks</a>;
content that does not fit within the block container overflows it.
<wpt pathprefix="/css/CSS2/text/">
white-space-pre-001.xht
white-space-pre-002.xht
white-space-pre-005.xht
white-space-pre-006.xht
white-space-pre-007.xht
white-space-pre-element-001.xht
</wpt>
<wpt>
white-space/white-space-pre-031.html
white-space/white-space-pre-032.html
white-space/white-space-pre-034.html
white-space/white-space-pre-035.html
white-space/white-space-pre-011.html
white-space/white-space-pre-051.html
white-space/white-space-pre-052.html
line-break/line-break-anywhere-and-white-space-001.html
line-break/line-break-anywhere-and-white-space-003.html
white-space/white-space-zero-fontsize-001.html
white-space/white-space-zero-fontsize-002.html
white-space/white-space-intrinsic-size-015.html
white-space/white-space-intrinsic-size-016.html
white-space/white-space-intrinsic-size-018.html
white-space/pre-with-whitespace-crash.html
</wpt>
<dt><dfn>nowrap</dfn>
<dd>Like ''white-space/normal'', this value collapses <a>white space</a>;
but like ''pre'', it does not allow wrapping.
<wpt>
white-space/white-space-nowrap-011.html
white-space/white-space-wrap-after-nowrap-001.html
line-break/line-break-anywhere-and-white-space-002.html
overflow-wrap/overflow-wrap-anywhere-008.html
white-space/nowrap-wbr-and-space-crash.html
</wpt>
<wpt pathprefix="/css/CSS2/text/">
white-space-nowrap-001.xht
white-space-nowrap-005.xht
white-space-nowrap-006.xht
text-align-white-space-004.xht
text-align-white-space-008.xht
white-space-nowrap-attribute-001.xht
white-space-processing-006.xht
</wpt>
<dt><dfn>pre-wrap</dfn></dt>
<dd>Like ''pre'', this value preserves <a>white space</a>;
but like ''white-space/normal'', it allows wrapping.
<wpt>
white-space/pre-wrap-001.html
white-space/pre-wrap-002.html
white-space/pre-wrap-003.html
white-space/pre-wrap-004.html
white-space/pre-wrap-005.html
white-space/pre-wrap-006.html
white-space/pre-wrap-007.html
white-space/pre-wrap-009.html
white-space/pre-wrap-010.html
white-space/pre-wrap-011.html
white-space/pre-wrap-012.html
white-space/pre-wrap-013.html
white-space/pre-wrap-014.html
white-space/pre-wrap-051.html
white-space/pre-wrap-052.html
white-space/textarea-pre-wrap-001.html
white-space/textarea-pre-wrap-002.html