Added programlisting example based on the one in variablelist.as.blocks with the...

diff --git a/xsl/params/variablelist.as.table.xml b/xsl/params/variablelist.as.table.xml
index d167de136f4e498accc571dac201da4d906115b6..f6ad97aed450caacf2ec47c88aa476889aa031f3 100644 (file)
--- a/xsl/params/variablelist.as.table.xml
+++ b/xsl/params/variablelist.as.table.xml
@@ -18,7 +18,7 @@
 
 <para>If non-zero, <sgmltag>variablelist</sgmltag>s will be formatted as
 tables. A processing instruction exists to specify a particualar width for the 
-column containing the <sgmltag>term</sgmltag>s  
+column containing the <sgmltag>term</sgmltag>s:   
 <sgmltab class="pi">dbhtml term-width=".25in"</sgmltab></para>
 
 <para>You can override this setting with a processing instruction as the
@@ -30,5 +30,20 @@ list-presentation="list"</sgmltag>.</para>
 FO case, proper list markup is robust enough to handle the formatting.
 But see also <parameter>variablelist.as.blocks</parameter>.</para>
 
+<programlisting><![CDATA[  <variablelist>
+        <?dbhtml list-presentation="table"?>
+        <?dbhtml term-width="1.5in"?>
+        <?dbfo list-presentation="list"?>
+        <?dbfo term-width="1in"?>
+        <varlistentry>
+          <term>list</term>
+          <listitem>
+                <para>
+                  Formatted as a table even if variablelist.as.table is set to 0.
+                </para>
+          </listitem>
+        </varlistentry>
+  </variablelist>]]></programlisting>
+
 </refsect1>
 </refentry>