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