doc/xslt/params/glossary.as.blocks.xml

   1 <refentry xmlns="http://docbook.org/ns/docbook"
   2           xmlns:xlink="http://www.w3.org/1999/xlink"
   3           xmlns:xi="http://www.w3.org/2001/XInclude"
   4           xmlns:src="http://nwalsh.com/xmlns/litprog/fragment"
   5           xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
   6           version="5.0" xml:id="glossary.as.blocks">
   7 <refmeta>
   8 <refentrytitle>glossary.as.blocks</refentrytitle>
   9 <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
  10 </refmeta>
  11 <refnamediv>
  12 <refname>glossary.as.blocks</refname>
  13 <refpurpose>Present glossarys using blocks instead of lists?</refpurpose>
  14 </refnamediv>
  15
  16 <refsynopsisdiv>
  17 <src:fragment xml:id="glossary.as.blocks.frag">
  18 <xsl:param name="glossary.as.blocks" select="0"/>
  19 </src:fragment>
  20 </refsynopsisdiv>
  21
  22 <refsection><info><title>Description</title></info>
  23
  24 <para>If non-zero, <tag>glossary</tag>s will be formatted as
  25 blocks.</para>
  26
  27 <para>If you have long <tag>glossterm</tag>s, proper list
  28 markup in the FO case may produce unattractive lists. By setting this
  29 parameter, you can force the stylesheets to produce block markup
  30 instead of proper lists.</para>
  31
  32 <para>You can override this setting with a processing instruction as the
  33 child of <tag>glossary</tag>: <tag class="xmlpi">dbfo
  34 glossary-presentation="blocks"</tag> or <tag class="xmlpi">dbfo
  35 glossary-presentation="list"</tag></para>
  36
  37 </refsection>
  38 </refentry>