blob: 017e1665112723647c910376b82697c03bc855d4 (
plain)
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
|
<refentry id="variablelist.as.blocks">
<refmeta>
<refentrytitle>variablelist.as.blocks</refentrytitle>
<refmiscinfo role="type">boolean</refmiscinfo>
</refmeta>
<refnamediv>
<refname>variablelist.as.blocks</refname>
<refpurpose>Format <sgmltag>variablelist</sgmltag>s lists as blocks?</refpurpose>
</refnamediv>
<refsynopsisdiv>
<src:fragment id='variablelist.as.blocks.frag'>
<xsl:param name="variablelist.as.blocks" select="0"/>
</src:fragment>
</refsynopsisdiv>
<refsect1><title>Description</title>
<para>If non-zero, <sgmltag>variablelist</sgmltag>s will be formatted as
blocks.</para>
<para>If you have long terms, proper list markup in the FO case may produce
unattractive lists. By setting this parameter, you can force the stylesheets
to produce block markup instead of proper lists.</para>
<para>You can override this setting with a processing instruction as the
child of <sgmltag>variablelist</sgmltag>: <sgmltag class="pi">dbfo
list-presentation="blocks"</sgmltag> or <sgmltag class="pi">dbfo
list-presentation="list"</sgmltag></para>
<programlisting><![CDATA[ <variablelist>
<?dbfo list-presentation="list"?>
<varlistentry>
<term>list</term>
<listitem>
<para>
Formatted as a list even if variablelist.as.blocks is set to 1.
</para>
</listitem>
</varlistentry>
</variablelist>]]></programlisting>
</refsect1>
</refentry>
|
