| 123456789101112131415161718192021222324252627282930313233343536 | 
							- <refentry xmlns="http://docbook.org/ns/docbook"
 
-           xmlns:xlink="http://www.w3.org/1999/xlink"
 
-           xmlns:xi="http://www.w3.org/2001/XInclude"
 
-           xmlns:src="http://nwalsh.com/xmlns/litprog/fragment"
 
-           xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 
-           version="5.0" xml:id="olink.debug">
 
- <refmeta>
 
- <refentrytitle>olink.debug</refentrytitle>
 
- <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
 
- </refmeta>
 
- <refnamediv>
 
- <refname>olink.debug</refname>
 
- <refpurpose>Turn on debugging messages for olinks</refpurpose>
 
- </refnamediv>
 
- <refsynopsisdiv>
 
- <src:fragment xml:id="olink.debug.frag">
 
- <xsl:param name="olink.debug" select="0"/>
 
- </src:fragment>
 
- </refsynopsisdiv>
 
- <refsection><info><title>Description</title></info>
 
- <para>If non-zero, then each olink will generate several
 
- messages about how it is being resolved during processing.
 
- This is useful when an olink does not resolve properly
 
- and the standard error messages are not sufficient to
 
- find the problem. 
 
- </para>
 
- <para>You may need to read through the olink XSL templates
 
- to understand the context for some of the debug messages.
 
- </para>
 
- </refsection>
 
- </refentry>
 
 
  |