1 <?xml version="1.0" encoding="ASCII"?><!--This file was created automatically by html2xhtml--><!--from the HTML stylesheets.--><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:exsl="http://exslt.org/common" xmlns="http://www.w3.org/1999/xhtml" version="1.0" exclude-result-prefixes="exsl">
3 <!-- ********************************************************************
4 $Id: chunk.xsl 9801 2013-09-06 19:23:43Z bobstayton $
5 ********************************************************************
7 This file is part of the XSL DocBook Stylesheet distribution.
8 See ../README or http://docbook.sf.net/release/xsl/current/ for
9 copyright and other information.
11 ******************************************************************** -->
13 <!-- ==================================================================== -->
16 <!-- First import the non-chunking templates that format elements
17 within each chunk file. In a customization, you should
18 create a separate non-chunking customization layer such
19 as mydocbook.xsl that imports the original docbook.xsl and
20 customizes any presentation templates. Then your chunking
21 customization should import mydocbook.xsl instead of
23 <xsl:import href="docbook-no-doctype.xsl"/>
25 <!-- chunk-common.xsl contains all the named templates for chunking.
26 In a customization file, you import chunk-common.xsl, then
27 add any customized chunking templates of the same name.
28 They will have import precedence over the original
29 chunking templates in chunk-common.xsl. -->
30 <xsl:import href="chunk-common.xsl"/>
32 <!-- The manifest.xsl module is no longer imported because its
33 templates were moved into chunk-common and chunk-code -->
35 <!-- chunk-code.xsl contains all the chunking templates that use
36 a match attribute. In a customization it should be referenced
37 using <xsl:include> instead of <xsl:import>, and then add
38 any customized chunking templates with match attributes. But be sure
39 to add a priority="1" to such customized templates to resolve
40 its conflict with the original, since they have the
41 same import precedence.
43 Using xsl:include prevents adding another layer
44 of import precedence, which would cause any
45 customizations that use xsl:apply-imports to wrongly
46 apply the chunking version instead of the original
47 non-chunking version to format an element. -->
48 <xsl:include href="chunk-code.xsl"/>