aboutsummaryrefslogtreecommitdiffstats
path: root/doc/user/tbl_inde
blob: c8e02d4285204bc4ae79eefd7563f21da2afc890 (plain) (blame)
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
@Section
    @Title { Indenting and struts }
    @Tag { tbl_inde }
@Begin
@PP
By default, entries appear at the left within cells, not counting the
cell margin.  The @Code indent option causes entries to be indented
tables. @RawIndex { tables }
tables.indent @SubIndex { @Code "indent" option }
indent.tables @Index { @Code "indent" option (tables) }
horizontally.  For example,
@ID @OneRow @Code "@Cell indent { ctr }"
horizontally centres the entry within the cell.  Other possible values
centred.entries @Index { centred entries in tables }
right.justified.entries @Index { right justified entries in tables }
are {@Code "left"} (the default value), {@Code "right"},
{@Code "align"} (Section {@NumberOf tbl_alig}), or any length (for
example, {@Code 2f}) meaning that much indent.
@PP
There is a corresponding @Code "indentvertical" option for vertical indenting
tables. @RawIndex { tables }
tables.indentvertical @SubIndex { @Code "indentvertical" option }
indentvertical.tables @Index { @Code "indentvertical" option (tables) }
within the cell.  It takes the same values except that @Code "left" is
renamed {@Code "top"} (the default), and @Code "right" is renamed
{@Code foot}.  A common problem with vertical placement is that words that
lack ascenders (parts of letters that rise up) or descenders (parts that
sink down) can easily become misaligned.  Looking at
@CD @Tbl
    mv { 0i }
    aformat { @Cell A | @Cell B | @Cell C }
{
@Rowa
    A { resume }
    B { poppy }
    C { title }
}
which is the result of
@ID @OneRow @Code @Verbatim {
@Tbl
    aformat { @Cell A | @Cell B | @Cell C }
{
@Rowa
    A { resume }
    B { poppy }
    C { title }
}
}
we see that the words are aligned correctly despite these
worries.  This is because by default
@Code "@Tbl" adds a @I { vertical strut } to each entry:  an invisible
object of zero width and height {@Code "1f"}, which covers for any absent
tables. @RawIndex { tables }
tables.strut @SubIndex { @Code "strut" option }
strut.option. @RawIndex { @Code "strut" option }
strut.option.in.tables @SubIndex { in tables }
ascenders and descenders.  The option
@ID @OneRow @Code "@Cell strut { no }"
can be used to remove the strut; other acceptable values for this
option are {@Code yes} (the default value), and any length, which will
add a strut of that length.
@PP
For completeness there is a corresponding @Code "struthorizontal" option; it
tables. @RawIndex { tables }
tables.struthorizontal @SubIndex { @Code "struthorizontal" option }
struthorizontal.tables @Index { @Code "struthorizontal" option (tables) }
takes the same values, its default value is {@Code no}, and it unlikely
ever to be used.
@End @Section