stylesheets/evergreen_docbook_files/docbook-xsl-1.75.2/params/glossary.as.blocks.xml

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