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