</para>
<para>
- An overview of the permissions field can be found in <link linkend="access1"/>.
+ An overview of the permissions field can be found in <link linkend="access1">the image below</link>.
</para>
<image id="access1" scale="40"><imagedescription>Overview of UNIX permissions field.</imagedescription><imagefile>access1</imagefile></image>
</para>
<para>
- <link linkend="ugbc"/> enumerates these controls.
+ <link linkend="ugbc">The table below</link> enumerates these controls.
</para>
<table frame='all' pgwide='0' id="ugbc"><title>User and Group Based Controls</title>
</para>
<para>
- Refer to <link linkend="fdpbc"/> for information regarding the parameters that may be used to affect file and
+ Refer to <link linkend="fdpbc">the table below</link> for information regarding the parameters that may be used to affect file and
directory permission-based access controls.
</para>
<para>
The following are documented because of the prevalence of administrators creating inadvertent barriers to file
- access by not understanding the full implications of &smb.conf; file settings. See <link linkend="mcoc"/>.
+ access by not understanding the full implications of &smb.conf; file settings. See <link linkend="mcoc">the table below</link>.
</para>
<table frame='all' id="mcoc"><title>Other Controls</title>
<title>Simple &smb.conf; Settings for CUPS</title>
<para>
- To summarize, <link linkend="cups-exam-simple"/> shows simplest printing-related setup for &smb.conf; to enable basic CUPS support:
+ To summarize, <link linkend="cups-exam-simple">the example below</link> shows simplest printing-related setup for &smb.conf; to enable basic CUPS support:
</para>
<para><smbconfexample id="cups-exam-simple">
<title>More Complex CUPS &smb.conf; Settings</title>
<para>
- <link linkend="overridesettings"/> is a slightly more complex printing-related setup
+ <link linkend="overridesettings">The example below</link> is a slightly more complex printing-related setup
for &smb.conf;. It enables general CUPS printing
support for all printers, but defines one printer share, which is set
up differently.
filter is used to convert directly from image to raster, without the
intermediate PostScript stage. It is used more often than the above
mentioned pre-filters. A summarizing flowchart of image file
-filtering is shown in <link linkend="small8"/>.
+filtering is shown in <link linkend="small8">the figure below</link>.
</para>
<para>
CUPS by default ships only a few generic PPDs, but they are good for
several hundred printer models. You may not be able to control
different paper trays, or you may get larger margins than your
-specific model supports. See <link linkend="cups-ppds"/> for summary information.
+specific model supports. See <link linkend="cups-ppds">the figure below</link> for summary information.
</para>
<table frame="all" id="cups-ppds">
(and also bypasses the CUPS-raster-drivers
<parameter>rastertosomething</parameter>). After Ghostscript finished its rasterization,
<parameter>cupsomatic</parameter> hands the rendered file directly to the CUPS backend. The
-flowchart in <link linkend="cupsomatic-dia"/> illustrates the difference between native CUPS
+flowchart in <link linkend="cupsomatic-dia">the image below</link> illustrates the difference between native CUPS
rendering and the <parameter>Foomatic/cupsomatic</parameter> method.
</para>
</sect2>
</itemizedlist>
<para>
- The resulting filter chain, therefore, is as drawn in <link linkend="pdftosocket"/>.
+ The resulting filter chain, therefore, is as drawn in <link linkend="pdftosocket">the figure below</link>.
</para>
<image id="pdftosocket"><imagefile>pdftosocket</imagefile><imagedescription>PDF to socket chain.</imagedescription></image>
</itemizedlist>
<para>
-The resulting filter chain therefore is as drawn in <link linkend="pdftoepsonusb"/>.
+ The resulting filter chain therefore is as drawn in <link linkend="pdftoepsonusb">the figure below</link>.
</para>
<image id="pdftoepsonusb"><imagefile>pdftoepsonusb</imagefile><imagedescription>PDF to USB chain.</imagedescription></image>
</itemizedlist>
<para>
-Both print paths are shown in the flowcharts in <link linkend="small11"/> and <link linkend="small12"/>.
+ Both print paths are shown in the flowcharts in the figures below.
</para>
</sect2>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+ <xsl:template match="ulink">
+ <xsl:element name="ulink">
+ <xsl:attribute name="url">
+ <xsl:value-of select="@url"/>
+ </xsl:attribute>
+ <xsl:choose>
+ <xsl:when test=". != ''">
+ <xsl:value-of select="."/>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:value-of select="@url"/>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:element>
+</xsl:template>
+
+
+
+<xsl:template match="link">
+ <xsl:element name="link">
+ <xsl:attribute name="linkend">
+ <xsl:value-of select="@linkend"/>
+ </xsl:attribute>
+ <xsl:choose>
+ <xsl:when test=". != ''">
+ <xsl:value-of select="."/>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:value-of select="@linkend"/>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:element>
+</xsl:template>
+
<xsl:param name="base.dir" select="'../htmldocs/'"/>
<xsl:param name="bridgehead.in.toc" select="1"/>
<xsl:param name="citerefentry.link" select="'1'"/>