xserver-nodm-init: reorder xserver-nodm to start position 90 for shr distribution
[openembedded.git] / docs / usermanual / chunk-utf8.xsl
blob5d979ac7117619672a39b32b5c4e9ac15f8104c6
1 <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
2 xmlns:exsl="http://exslt.org/common"
3 version="1.0"
4 exclude-result-prefixes="exsl">
6 <!-- ********************************************************************
7 $Id: chunk.xsl 6910 2007-06-28 23:23:30Z xmldoc $
8 ********************************************************************
10 This file is part of the XSL DocBook Stylesheet distribution.
11 See ../README or http://docbook.sf.net/release/xsl/current/ for
12 copyright and other information.
14 ******************************************************************** -->
16 <!-- ==================================================================== -->
18 <!-- First import the non-chunking templates that format elements
19 within each chunk file. In a customization, you should
20 create a separate non-chunking customization layer such
21 as mydocbook.xsl that imports the original docbook.xsl and
22 customizes any presentation templates. Then your chunking
23 customization should import mydocbook.xsl instead of
24 docbook.xsl. -->
25 <xsl:import href="docbook-utf8.xsl"/>
27 <!-- chunk-common.xsl contains all the named templates for chunking.
28 In a customization file, you import chunk-common.xsl, then
29 add any customized chunking templates of the same name.
30 They will have import precedence over the original
31 chunking templates in chunk-common.xsl. -->
32 <xsl:import href="chunk-common.xsl"/>
34 <!-- The manifest.xsl module is no longer imported because its
35 templates were moved into chunk-common and chunk-code -->
37 <!-- chunk-code.xsl contains all the chunking templates that use
38 a match attribute. In a customization it should be referenced
39 using <xsl:include> instead of <xsl:import>, and then add
40 any customized chunking templates with match attributes. But be sure
41 to add a priority="1" to such customized templates to resolve
42 its conflict with the original, since they have the
43 same import precedence.
45 Using xsl:include prevents adding another layer
46 of import precedence, which would cause any
47 customizations that use xsl:apply-imports to wrongly
48 apply the chunking version instead of the original
49 non-chunking version to format an element. -->
50 <xsl:include href="chunk-code.xsl"/>
52 </xsl:stylesheet>