2 <!DOCTYPE xsl:stylesheet [
<!ENTITY % xsldoc.ent SYSTEM
"./xsldoc.ent"> %xsldoc.ent; ]
>
3 <!--#############################################################################
4 | $Id: pi.mod.xsl,v 1.6 2004/01/01 11:37:00 j-devenish Exp $
5 |- #############################################################################
6 | $Author: j-devenish $
7 + ############################################################################## -->
10 xmlns:
xsl=
"http://www.w3.org/1999/XSL/Transform"
11 xmlns:
doc=
"http://nwalsh.com/xsl/documentation/1.0"
12 exclude-result-prefixes=
"doc" version='
1.0'
>
14 <doc:reference id=
"pi" xmlns=
"">
16 <releaseinfo role=
"meta">
17 $Id: pi.mod.xsl,v
1.6 2004/
01/
01 11:
37:
00 j-devenish Exp $
24 <year>2000</year><year>2001</year><year>2002</year><year>2003</year><year>2004</year>
25 <holder>Ramon Casellas
</holder>
28 <doc:revision rcasver=
"1.12">&rev_2003_05;</doc:revision>
31 <title>Processing Instructions
<filename>pi.mod.xsl
</filename></title>
35 Some processing instructions are handled by templates in this file
36 while other are present in
<xref linkend=
"figure"/>,
<xref
37 linkend=
"biblio"/> and
<xref linkend=
"index"/>.
43 <doc:template xmlns=
"">
44 <refpurpose> Process generic processing instructions
</refpurpose>
48 Processing instructions are allowed but are ignored unless they
49 have a
&DB2LaTeX;-specific name.
57 <para>This template suppresses processing instructions.
</para>
60 <xsl:template match=
"processing-instruction()"/>
62 <doc:template xmlns=
"">
63 <refpurpose> Output arbitrary
&LaTeX; text
</refpurpose>
67 The contents of this processing instruction will
68 output directly by
&DB2LaTeX;. This allows the
69 inclusion of
&latex;-specific instructions that
70 will be recognised only by
&latex; stylesheets.
71 For example,
<literal><![CDATA[
<?latex \sloppy
?>]]
></literal>
72 would insert
<literal>\sloppy
</literal> into the output
73 without any character escaping.
81 <xsl:template match=
"processing-instruction('latex')">
82 <xsl:value-of select=
"."/>
85 <doc:template xmlns=
"">
86 <refpurpose> Output arbitrary
&LaTeX; text
</refpurpose>
90 The contents of this processing instruction will
91 output directly by
&DB2LaTeX;. This allows the
92 inclusion of
&latex;-specific instructions that
93 will be recognised only by
&latex; stylesheets.
94 For example,
<literal><![CDATA[
<?latex \sloppy
?>]]
></literal>
95 would insert
<literal>\sloppy
</literal> into the output
96 without any character escaping.
104 <xsl:template match=
"processing-instruction('db2latex')">
105 <xsl:value-of select=
"."/>
108 <xsl:template match=
"processing-instruction('rcas')">
109 <xsl:processing-instruction name=
"dbhtml">
110 <xsl:value-of select=
"."/>
111 </xsl:processing-instruction>
114 <xsl:template name=
"process.cmdsynopsis.list">
115 <xsl:param name=
"cmdsynopses"/><!-- empty node list by default -->
116 <xsl:param name=
"count" select=
"1"/>
119 <xsl:when test=
"$count>count($cmdsynopses)"></xsl:when>
121 <xsl:variable name=
"cmdsyn" select=
"$cmdsynopses[$count]"/>
125 <xsl:attribute name=
"href">
126 <xsl:call-template name=
"label.id">
127 <xsl:with-param name=
"object" select=
"$cmdsyn"/>
132 <xsl:when test=
"$cmdsyn/@xreflabel">
133 <xsl:call-template name=
"xref.xreflabel">
134 <xsl:with-param name=
"target" select=
"$cmdsyn"/>
139 <xsl:call-template name="xref.cmdsynopsis">
140 <xsl:with-param name="target" select="$cmdsyn"/>
141 </xsl:call-template>-->
147 <xsl:call-template name=
"process.cmdsynopsis.list">
148 <xsl:with-param name=
"cmdsynopses" select=
"$cmdsynopses"/>
149 <xsl:with-param name=
"count" select=
"$count+1"/>
155 <xsl:template match=
"processing-instruction('dbcmdlist')">
156 <xsl:variable name=
"cmdsynopses" select=
"..//cmdsynopsis"/>
158 <xsl:if test=
"count($cmdsynopses)<1">
159 <xsl:message><xsl:text>No cmdsynopsis elements matched dbcmdlist PI, perhaps it's nested too deep?
</xsl:text>
164 <xsl:call-template name=
"process.cmdsynopsis.list">
165 <xsl:with-param name=
"cmdsynopses" select=
"$cmdsynopses"/>
170 <!-- ==================================================================== -->
172 <xsl:template name=
"process.funcsynopsis.list">
173 <xsl:param name=
"funcsynopses"/><!-- empty node list by default -->
174 <xsl:param name=
"count" select=
"1"/>
177 <xsl:when test=
"$count>count($funcsynopses)"></xsl:when>
179 <xsl:variable name=
"cmdsyn" select=
"$funcsynopses[$count]"/>
183 <xsl:attribute name=
"href">
184 <xsl:call-template name=
"label.id">
185 <xsl:with-param name=
"object" select=
"$cmdsyn"/>
190 <xsl:when test=
"$cmdsyn/@xreflabel">
191 <xsl:call-template name=
"xref.xreflabel">
192 <xsl:with-param name=
"target" select=
"$cmdsyn"/>
197 <xsl:call-template name="xref.funcsynopsis">
198 <xsl:with-param name="target" select="$cmdsyn"/>
206 <xsl:call-template name=
"process.funcsynopsis.list">
207 <xsl:with-param name=
"funcsynopses" select=
"$funcsynopses"/>
208 <xsl:with-param name=
"count" select=
"$count+1"/>
214 <xsl:template match=
"processing-instruction('dbfunclist')">
215 <xsl:variable name=
"funcsynopses" select=
"..//funcsynopsis"/>
217 <xsl:if test=
"count($funcsynopses)<1">
218 <xsl:message><xsl:text>No funcsynopsis elements matched dbfunclist PI, perhaps it's nested too deep?
</xsl:text>
223 <xsl:call-template name=
"process.funcsynopsis.list">
224 <xsl:with-param name=
"funcsynopses" select=
"$funcsynopses"/>
229 <!-- ==================================================================== -->