chunk.xsl 2.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
  1. <?xml version="1.0" encoding="ASCII"?>
  2. <!--This file was created automatically by html2xhtml-->
  3. <!--from the HTML stylesheets.-->
  4. <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">
  5. <!-- ********************************************************************
  6. $Id$
  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. <!-- First import the non-chunking templates that format elements
  14. within each chunk file. In a customization, you should
  15. create a separate non-chunking customization layer such
  16. as mydocbook.xsl that imports the original docbook.xsl and
  17. customizes any presentation templates. Then your chunking
  18. customization should import mydocbook.xsl instead of
  19. docbook.xsl. -->
  20. <xsl:import href="docbook.xsl"/>
  21. <!-- chunk-common.xsl contains all the named templates for chunking.
  22. In a customization file, you import chunk-common.xsl, then
  23. add any customized chunking templates of the same name.
  24. They will have import precedence over the original
  25. chunking templates in chunk-common.xsl. -->
  26. <xsl:import href="chunk-common.xsl"/>
  27. <!-- The manifest.xsl module is no longer imported because its
  28. templates were moved into chunk-common and chunk-code -->
  29. <!-- chunk-code.xsl contains all the chunking templates that use
  30. a match attribute. In a customization it should be referenced
  31. using <xsl:include> instead of <xsl:import>, and then add
  32. any customized chunking templates with match attributes. But be sure
  33. to add a priority="1" to such customized templates to resolve
  34. its conflict with the original, since they have the
  35. same import precedence.
  36. Using xsl:include prevents adding another layer
  37. of import precedence, which would cause any
  38. customizations that use xsl:apply-imports to wrongly
  39. apply the chunking version instead of the original
  40. non-chunking version to format an element. -->
  41. <xsl:include href="chunk-code.xsl"/>
  42. </xsl:stylesheet>