glossary.as.blocks.xml 1.3 KB

1234567891011121314151617181920212223242526272829303132333435363738
  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. <refsynopsisdiv>
  16. <src:fragment xml:id="glossary.as.blocks.frag">
  17. <xsl:param name="glossary.as.blocks" select="0"/>
  18. </src:fragment>
  19. </refsynopsisdiv>
  20. <refsection><info><title>Description</title></info>
  21. <para>If non-zero, <tag>glossary</tag>s will be formatted as
  22. blocks.</para>
  23. <para>If you have long <tag>glossterm</tag>s, proper list
  24. markup in the FO case may produce unattractive lists. By setting this
  25. parameter, you can force the stylesheets to produce block markup
  26. instead of proper lists.</para>
  27. <para>You can override this setting with a processing instruction as the
  28. child of <tag>glossary</tag>: <tag class="xmlpi">dbfo
  29. glossary-presentation="blocks"</tag> or <tag class="xmlpi">dbfo
  30. glossary-presentation="list"</tag></para>
  31. </refsection>
  32. </refentry>