1<?xml version="1.0" encoding="ASCII"?> 2<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<!-- ******************************************************************** 5 $Id: profile-chunk.xsl,v 1.1 2011-09-16 21:44:00 bobs Exp $ 6 ******************************************************************** 7 8 This file is part of the XSL DocBook Stylesheet distribution. 9 See ../README or http://docbook.sf.net/release/xsl/current/ for 10 copyright and other information. 11 12 ******************************************************************** --> 13 14<!-- ==================================================================== --> 15 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 22 docbook.xsl. --> 23<xsl:import href="docbook.xsl"/> 24 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="../xhtml/chunk-common.xsl"/> 31 32<!-- The manifest.xsl module is no longer imported because its 33 templates were moved into chunk-common and chunk-code --> 34 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. 42 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="../xhtml/profile-chunk-code.xsl"/> 49 50<xsl:include href="html5-chunk-mods.xsl"/> 51 52</xsl:stylesheet> 53