blob: 1d5899a659f2172c52aa885113b1f13d0a92dba2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:exsl="http://exslt.org/common"
version="1.0"
exclude-result-prefixes="exsl">
<!-- ********************************************************************
$Id$
********************************************************************
This file is part of the XSL DocBook Stylesheet distribution.
See ../README or http://nwalsh.com/docbook/xsl/ for copyright
and other information.
******************************************************************** -->
<!-- ==================================================================== -->
<xsl:import href="docbook.xsl"/>
<xsl:import href="chunk-common.xsl"/>
<xsl:include href="manifest.xsl"/>
<!-- Why is chunk-code now xsl:included?
Suppose you want to customize *both* the chunking algorithm used *and* the
presentation of some elements that may be chunks. In order to do that, you
must get the order of imports "just right". The answer is to make your own
copy of this file, where you tqreplace the initial import of "docbook.xsl"
with an import of your own base.xsl (that does its own import of docbook.xsl).
Put the templates for changing the presentation of elements in your base.xsl.
Put the templates that control chunking after the include of chunk-code.xsl.
Voila! (Man I hope we can do this better in XSLT 2.0)
-->
<xsl:include href="profile-chunk-code.xsl"/>
</xsl:stylesheet>
|
