<!-- I can't fathom xmlto's logic with image scaling, so I've turned it off -->
<xsl:param name="ignore.image.scaling" select="1"/>
+<!-- <note> in a div with no heading -->
+<xsl:template name="note.frobozz">
+ <xsl:param name="content">
+ <xsl:apply-templates/>
+ </xsl:param>
+ <xsl:text disable-output-escaping="yes"><div class="note"></xsl:text>
+ <xsl:copy-of select="$content"/>
+ <xsl:text disable-output-escaping="yes"></div></xsl:text>
+</xsl:template>
+
+<xsl:template match="note">
+ <xsl:call-template name="note.frobozz"/>
+</xsl:template>
+
</xsl:stylesheet>
<xsl:call-template name="inline.frobozz"/>
</xsl:template>
+<!-- <note> in a box with \dbend -->
+<xsl:template name="note.frobozz">
+ <xsl:param name="content">
+ <xsl:apply-templates/>
+ </xsl:param>
+ <xsl:text>\begin{center}\fbox{\begin{minipage}{0.8\textwidth}\raisebox{10pt}{\dbend}\quad</xsl:text>
+ <xsl:copy-of select="$content"/>
+ <xsl:text>\end{minipage}}\end{center}\par</xsl:text>
+</xsl:template>
+
+<xsl:template match="note">
+ <xsl:call-template name="note.frobozz"/>
+</xsl:template>
+
</xsl:stylesheet>
This manual uses icons from the <ulink url="http://tango.freedesktop.org/">Tango Desktop Project</ulink>, with thanks.
</para>
+</section>
+
+<!-- ============================================================== -->
+<section>
+<title>This manual</title>
+
+<para>
+This manual presents bits of DCP-o-matic's user interface (such as menu items or buttons) <guilabel>like this</guilabel>.
+</para>
+
+<note>
+Notes of an advanced nature are presented like this. Ignore them unless you want to know the gory details.
+</note>
+
</section>
</chapter>
doubt, use <guilabel>Modified Transitional 1</guilabel>.
</para>
+<note>
+The differences between the three KDM types are fairly subtle.
+<guilabel>DCI Specific</guilabel> and <guilabel>DCI Any</guilabel> add
+a <code><ContentAuthenticator></code> tag to the KDM which
+allows the exhibitor to check that the DCP and KDM have come from a
+bona-fide source. In addition, <guilabel>DCI Specific</guilabel> adds
+information on trusted devices to the KDM. This allows the KDM
+creator to specify devices (such as sound processors) that are allowed
+to use keys delivered by the KDM. At present it is not clear how
+widely the <guilabel>DCI Specific</guilabel> and <guilabel>DCI
+Any</guilabel> features are supported (or even tolerated) by servers
+so you are advised to use <guilabel>Modified Transitional
+1</guilabel>.
+</note>
+
<para>
Finally, choose what you want to do with the KDMs. They can be
written to disk, to a location that you can specify by clicking