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="generate.id.attributes">
\r
8 <refentrytitle>generate.id.attributes</refentrytitle>
\r
9 <refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>
\r
12 <refname>generate.id.attributes</refname>
\r
13 <refpurpose>Generate ID attributes on container elements?</refpurpose>
\r
17 <src:fragment xml:id="generate.id.attributes.frag">
\r
18 <xsl:param name="generate.id.attributes" select="0"/>
\r
22 <refsection><info><title>Description</title></info>
\r
24 <para>If non-zero, the HTML stylesheet will generate ID attributes on
\r
25 containers. For example, the markup:</para>
\r
27 <screen><section id="foo"><title>Some Title</title>
\r
28 <para>Some para.</para>
\r
29 </section></screen>
\r
31 <para>might produce:</para>
\r
33 <screen><div class="section" id="foo">
\r
34 <h2>Some Title</h2>
\r
35 <p>Some para.</p>
\r
36 </div></screen>
\r
38 <para>The alternative is to generate anchors:</para>
\r
40 <screen><div class="section">
\r
41 <h2><a name="foo"></a>Some Title</h2>
\r
42 <p>Some para.</p>
\r
43 </div></screen>
\r
45 <para>Because the <tag class="attribute">name</tag> attribute of
\r
46 the <tag>a</tag> element and the <tag class="attribute">id</tag>
\r
47 attribute of other tags are both of type <quote>ID</quote>, producing both
\r
48 generates invalid documents.</para>
\r
50 <para>As of version 1.50, you can use this switch to control which type of
\r
51 identifier is generated. For backwards-compatibility, generating
\r
52 <tag>a</tag> anchors is preferred.</para>
\r
54 <para>Note: at present, this switch is incompletely implemented.
\r
55 Disabling ID attributes will suppress them, but enabling ID attributes
\r
56 will not suppress the anchors.</para>
\r