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="html.longdesc.link">
\r
8 <refentrytitle>html.longdesc.link</refentrytitle>
\r
9 <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
\r
12 <refname>html.longdesc.link</refname>
\r
13 <refpurpose>Should a link to the longdesc be included in the HTML?</refpurpose>
\r
17 <src:fragment xml:id="html.longdesc.link.frag">
\r
18 <xsl:param name="html.longdesc.link" select="$html.longdesc"/>
\r
22 <refsection><info><title>Description</title></info>
\r
24 <para>If non-zero, links will be created to the
\r
25 HTML files created for the
\r
26 <literal>longdesc</literal> attribute. It makes no
\r
27 sense to enable this option without also enabling the
\r
28 <parameter>html.longdesc</parameter> parameter.</para>
\r
31 <para>The <literal>longdesc.link</literal> named template is called
\r
32 to construct the link.</para>
\r
33 Assumption. That this documentation is for the user, do they need to know
\r